- Application review. Every application gets at least one human review.
- CodeSignal (45 minutes, in two sections). A security-specific assessment, not LeetCode and not a general coding test: it involves very little writing code by hand, and leans instead on code review and written responses to scenarios like diagnosing failures in an IAM configuration. We want the content of our assessments to have at least some overlap with the things we expect you to do in real life.
- Screening call (15 minutes). An informal chat, where we briefly cover background, fit, and motivation.
- Technical and experience interviews (about 2-3 hours in total, across two or three sessions). We're still settling the exact shape of these for this role, and we'll tell you the format before each session. Expect some combination of: a technical interview on reading and diagnosing unfamiliar infrastructure, without AI assistance; a technical interview in two parts, an AI-unassisted design and specification problem followed by an AI-assisted implementation of it; and an experience interview walking through one or more past projects in detail, with time to discuss the role and answer your questions.
- 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. Where we can, we'll bundle the sessions in (4) so they occur back to back, though with different interviewers, so you get a chance to talk to more of our team. We'll also run (5) and (6) 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, how well you interact with the AIs throughout implementation, and how well you navigate the resulting outputs. The exact details of the tests are still being settled for this role, 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.