Real, anonymous reports from people who interviewed for Software Engineer at Two Sigma, newest first and distilled into what to expect across the loop.
My process started with an online assessment that took about an hour and had two coding questions. The first one was the easier LeetCode-style problem, and the second was a more involved pathfinding task. It took longer than I expected because the second question required careful graph-style thinking, even though nothing felt conceptually alien.
My process started with a timed coding OA on HackerRank, and after I finished it, I had a phone interview. From there, I went into the final rounds in an in-person format with multiple interviews grouped back-to-back. What surprised me most was how flexible the recruiter was—deadlines got adjusted and the OA timeline ended up extending when needed.
Candidates begin with a HackerRank online assessment that typically includes 2-3 coding questions, often in the medium to hard range, focusing on data structures and algorithms. The assessment is seen as a significant gate, with varying difficulty levels reported across experiences.
The technical interview rounds are intensive, often consisting of multiple back-to-back sessions that progressively increase in difficulty, focusing heavily on graph traversal, dynamic programming, and data structure implementation. Candidates are expected to articulate their thought process clearly while solving problems.
Behavioral interviews follow the technical rounds and are structured to probe deeply into candidates' past experiences and decision-making processes. Candidates report that these sessions can feel rigorous, with a focus on specific examples from their resumes.
The overall interview process is described as tightly structured, with candidates experiencing a high level of pressure due to the pacing and the number of rounds. Many report that the process feels like a gauntlet, where performance in earlier rounds directly impacts progression.
Candidates consistently note that the difficulty of the questions is high, particularly in the technical rounds, with many struggling with dynamic programming and complex algorithmic challenges. The expectation is to solve problems correctly and efficiently under time constraints.
While the interview process is generally described as professional and responsive, candidates express a desire for more feedback after the interviews, particularly when they do not receive offers, as many feel the lack of closure after investing significant time.