Updated by Jane Street candidates
Software Engineer Interview Experience
For a functional programming shop, nearly every question I got was best answered in an object-oriented way, and in the deep dive the interviewer literally said he’d much rather hear about a project I had not rehearsed.
Interview process
I ended up on the senior-and-up version of the loop because I had a project deep dive in addition to the coding rounds. The big surprise was that the SWE process was not mathy or brainteaser-heavy at all. It was mostly long, collaborative coding interviews where they start with one implementation problem and keep building on it, plus a pretty probing project discussion full of why questions. Almost every onsite round had two interviewers, but it felt more like a carefully run collaborative session than a pile-on. My overall impression was that the bar was high and the interview design was very intentional.
- Recruiter screen
- Phone interview
- Technical interview
- Final round
Interview tips
I would actually ignore rumors and prep for solid implementation-heavy DSA, not quant math. I would also spend more time practicing talking while coding, because the value is not just getting the answer, it is showing that you can build something cleanly, ask clarifying questions, and keep going when they add another layer. I would also prep one or two projects deeply enough that you can explain the why behind the design, but do not over-rehearse a polished speech because they may deliberately steer you to something less scripted. Also, be ready to admit what you do not know without getting flustered.
Company culture
You can tell they put a lot of money and thought into hiring. They train interviewers heavily, use two interviewers a lot, write personalized questions instead of obvious LeetCode clones, and even fly people out early so they are not rushed. The whole thing felt high-trust and collaborative, like they are trying to simulate what it is actually like to work with you rather than catch you with tricks. For SWE at least, the public reputation around math and brainteasers seemed outdated or just aimed at different roles. They also seemed unusually principled about offers and recruiting in general, like not using exploding offers and wanting candidates to make an informed decision.
Questions asked
Overview
The project deep dive was the part that made it clear I was in their senior-and-up path. I came in with a short menu of projects I could talk about, and the interviewer specifically picked one that felt less rehearsed because he said he would rather hear something I had not polished. The tone was casual and friendly, but the probing was real, especially around why decisions were made and how much I understood about systems next to mine. One interviewer in that round was especially nice and would sometimes step in if he felt I had already answered enough.
Question types asked
Specific questions asked
Why did you make that design decision?
Why did you not use a different approach?
What was happening in the adjacent system your work depended on?
I had prepared a menu of six projects, but they intentionally picked one I had not starred because they wanted something less rehearsed. Then it turned into a lot of why questions: why we built it that way, why we did not choose some other design, and what was going on in systems connected to mine. On the parts I owned, I explained the motivation and tradeoffs. On the adjacent pieces, I was honest about what I knew and what I did not know instead of bluffing.
Get full access with a membership, or share your experience to try it free.
