- Application review. Every application gets at least one human review.
- CodeSignal (90 minutes). The Industry Coding Assessment, not LeetCode: we want the content of our assessments to have at least some overlap with the things we expect you to do in real life, even if asking you to write code is a bit dated.
- Screening call (15 minutes). An informal chat, where we briefly cover background, fit, and motivation.
- Technical interview #1 (45 minutes). This will likely be a performance-optimization-style problem. We'll give you some demo code and ask you to spot issues and propose solutions, without AI assistance.
- Experience interview (60 minutes). We'll walk through your background in much more detail, asking you to go through one or more past projects you've worked on. We'll also take more time to discuss the role and answer your questions, and we'll share more information before you get to this stage.
- Technical interview #2 (75 minutes). This has two parts: (a) an AI-unassisted systems design and specification problem, followed by (b) an AI-assisted implementation of (a).
- 1-on-1s. A chat with our chief scientist, Geoffrey, as well as any relevant people from the team you would like to talk to and ask questions.
- References. We'll reach out to a few references as we make our final decision.
On scheduling. In some cases, we'll bundle (3) and (4) so they occur back to back. In almost all cases, we'll bundle (5) and (6), though with different interviewers, so you get a chance to talk to more of our team. We'll also run (7) and (8) in parallel. Our aim is to get you an update within 2-3 days of each stage, which means a process of about three weeks. For some candidates, especially if you have competing deadlines, we'll aim to push faster.
On the technical interviews. We dropped work tests because there's so little signal left in them. What we're looking for is how well you figure out what to tell the AIs (6a), how well you interact with the AIs throughout implementation (6b), and how well you navigate the resulting outputs (4). The exact details of the tests are liable to change a little, but what we're testing for will remain the same.
On interviewers. Most of our interviewers are on our engineering team, and we'll try to set things up so that you get to talk to different people at each interview. Each interview will have time for you to ask questions.