Love the idea of giving the person an idea as to what to expect though this is a pretty general outline; I've gotten the same (although I'll admit far less pret

Love the idea of giving the person an idea as to what to expect though this is a pretty general outline; I've gotten the same (although I'll admit far less pretty) when I've interviewed at Amazon, Apple, etc. The idea of letting someone actually work on a problem is far better than generic algorithm or data structure questions. Two things though... > As soon as we schedule the interview, applicants receive a link taking them to this welcome page. Love the page but the content is all static. This should be in an email. If it's in an email, especially in invite form, I have access to the content at all times on my phone and can even accept an invite. Putting it in the browser means I have to find the email and open the browser (alternatively bookmark or keep the site open). But the content is static so it should be in an email. In my opinion anyway. > After that is the main part of the technical interview: we ask interviewees to work on their own project, using whatever resources they deem necessary (and yes, that includes Google). We want resourceful developers who can problem solve, not people with an encyclopedic memory. We use this as an opportunity to learn what our candidates are passionate about. This helps us understand whether ReadMe is a place where they can pursue their long-term goals. Hmm. So many projects I want to work on, especially for an hour or two session, may not necessarily reflect my long term goals but be more oriented towards completing something that either myself or I perceive my interviewers being interested in. Yeah I get the whole "work on what you want" thing but in such a short timeframe to show off what I can do is absolutely not indicative of my long term goals.