Hi there - thank you for being interested in learning more about our interview process!
Our process is made up of 4 steps:
The first two steps are shorter (30 mins and 1 hr, respectively). We've structured those conversations to enable you to learn more about us, and for us to make sure there's a high-level fit in terms of what you're looking for, what we can provide, and your skillset.
The final two steps take a little bit more time, but are at a stage where we're confident enough in a potential fit to devote that time across our team (and to ask that of you!). These last two steps could be thought of as one consolidated final round interview (with both technical and non-technical components), but we've broken them apart to bring down the 'stress' level of someone watching you code the whole time!
This conversation is a 30-minute casual chat over the phone.
We usually kick off the conversation with 15-20 minutes of conversation led by our team asking you about your background, what you're looking for in the role, and what matters to you in the place you work (to determine if we're the right fit for what you're looking for!).
We'll also ask for any salary expectations you might have - this isn't meant to be a 'trick' question, but to quickly understand whether we're close enough in expectations so that we don't waste your time!
We'll spend the remaining time sharing background on 4Degrees, what we’re looking for in the hire, and answering any questions you have about the product, business, and the role!
Assuming you're excited about working with us after the first conversation (and vice versa), we'll connect you to a senior engineer for a technically oriented conversation (and assessment).
The conversation and exercise usually takes 60 minutes in total, typically done via screen share. About 45 minutes of the interview are spent in an actual coding environment, with the rest set aside for introductions and questions from the candidate.
The coding is meant to be collaborative, somewhat like a paired programming exercise. The coding tasks are meant to be as reflective of the real on-the-job work as possible and often include writing from scratch as well as editing existing code.
While most organizations have final round interview days that include a number of live technical assessments, we've found the stress of direct oversight for such a long period of time to be painful for candidates. As a result, we've substituted that out in favor of doing a take-home assignment designed to mimic the on-the-job tasks they will be expected to do once hired.