(Cross posted on my personal blog.)

Think of a function as a black box. It takes an input, and spits back out an
output.



For getPromotedPosts, you can feed it a list of blog posts and it will spit back
out the ones that have been promoted.

But I probably didn't need to explain that to you, did I? Why not? Well, because
getPromotedPosts is self-explanatory. Because getPromotedPosts is named well.

Now what if instead of getPromotedPosts, it was named something like getThePosts
? Well, that name isn't self-explanatory. You know it's getting some posts, but
it's not clear which ones. The most recent posts? Posts from a certain author?
Posts from this week?



As a programmer, what do you do in this situation? You scroll to the function
definition and start reading the code.

function getThePosts(posts) {
 ...
}


In other words, you open the box.



What does that look like? Something like this:

* You're reading through the code in some file. Line one, line two, line three.
* You reach line 30 and see…

As a Back-end Engineering Intern, you will get to learn from and work with our world-class Back-end Engineers. Most of our back-end systems are written in Ruby on Rails, so that’s a
Fantastic opportunity to gain some experience with one of the best web frameworks.

During the internship you’ll learn about the best practices of modern web development and get to work on various real-world tasks together with your mentor, and occasionally independently.

This is a 6 months paid internship program that may conclude with a permanent position within one of our great core engineering teams.

This is a full time, flexible hours, remote position that can be done from anywhere. Due to the remote nature of this role, we are unable to provide visa sponsorship.
Resumes and communication must be submitted in English.