Two Sigma · Software engineer / quant researcher · Quant Researcher (esp. PhD/experienced)
You present a past research project, thesis, or modeling problem; interviewers interrogate methodology, assumptions, validation, and alternatives
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
Two Sigma’s published process. Lime marks the stage this round runs.
Built from what Two Sigma publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.
Company description, mission ("rigorous scientific inquiry," "signals across markets to deliver alpha"), and culture language ("think like scientists," "kindness, collaboration, and continuous learning").
Hiring philosophy and candidate qualities ("problem solvers, academics, and inventors"; "hypothesize, collaborate with their peers, and develop their intellectual curiosity") and role families (Engineering; Quantitative Research).
SWE leveling ladder L1-L6, used to scale round difficulty by level. Page confirms levels; it does not describe the interview process.
General algorithm topic taxonomy backing the coding-round pattern list (arrays/hashing, graphs/trees, intervals, heaps, DP, data-structure design).
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
Conversational logistics and motivation call with a recruiter
Timed, autograded, no interviewer
Live coding on a shared editor over video
Onsite/superday live-coding round, harder than the phone screen
Verbal/whiteboard, no coding
Fast, escalating verbal round with scratch math
Conversational behavioral round, not a named-rubric interrogation like Amazon