Five candidates describe NineTwoThree software engineer interviews with 3-5 rounds. Reports cover medium-level coding, QA and systems questions, resume deep dives, and SQL. Experiences differ by candidate and level.
$108K
Avg. Base Comp
$130K
Avg. Total Comp
3-5 rounds
Typical Rounds
4-8 weeks
Process Length
NineTwoThree software engineer interviews, as five candidates describe them, are built around coding problems at a medium level, with the later rounds sometimes going deeper. The reports differ a lot, so prepare for a range rather than one fixed format.
One candidate reported three elimination-style technical rounds. They started with array rotation and finding the middle of a linked list, moved to QA topics such as smoke testing, regression testing and test case design, and ended with a roughly hour-long hybrid round. That round included building a multi-node tree and running DFS on it, plus object-oriented design. Another candidate reported four rounds of about 30 minutes, all coding, with no behavioral or resume questions. Their later rounds moved to a 2D prefix sum with multithreading considerations. A third candidate also got a 2D prefix sum problem, along with hash map trade-offs, operating systems and compiler basics. That candidate described the process as taking one to two months.
Two candidates who interviewed as Associate Software Engineers described a more resume-heavy shape. One reported an online test, a pen-and-paper aptitude test, four technical rounds and an HR round, with questions on SQL, linked lists, OOP, networking and internship projects. The other described four rounds covering DSA, recursion, basic dynamic programming, joins and a second-highest-salary-per-department query. That candidate's last round combined technical and managerial topics. Both reported offers.
In practice, drill linked lists, arrays, trees and graph traversal, and be ready to explain your own projects in detail. Two candidates reported later rounds on multithreading or hash map internals, so it is worth reviewing concurrency basics too. Ask clarifying questions when a prompt feels vague, since one candidate said they sometimes had to work out what the interviewer was actually asking.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the NineTwoThree process.
There were four rounds total, and the entire process took about a month to two months from start to finish. Each round lasted roughly an hour and followed a similar structure: half resume and conceptual knowledge questions, half coding problems. The coding side mixed data structures and algorithms with questions about ML, operating systems, and compiler basics—which felt a bit scattered. One interview dove into hash map implementations, asking detailed questions about why std::unordered_map often isn't optimal and how alternatives from libraries like TBB or ABSL perform better under different circumstances. Another round included a 2D prefix sum problem, along with some more abstract data structure discussions where I had to figure out what the interviewer was actually asking. The interviewers were generally supportive and gave hints when I was stuck, but the bar for the "right" amount of assistance seemed inconsistent—needing too much help was apparently a signal against you. I felt confident after the final round; the interviews had ended on an upbeat note. Unfortunately, after that, the recruiter went silent and didn't respond to any follow-ups despite my reaching out multiple times.
Prep tip from this candidate
Be ready for oddball questions outside the typical DSA wheelhouse—deep dives into hash map trade-offs, compiler concepts, and OS internals are real possibilities. Also prepare mentally for vague prompts; if the question doesn't make sense, ask clarifying questions early rather than guessing.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at NineTwoThree
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Minimum Change | |
| Raining in Seattle | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 3 Users | |
| Find the First Non-Repeating Character in a String | |
| Flight Records | |
| Daily Retention Summary | |
| Prime to N | |
| The Brackets Problem | |
| Upsell Transactions | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Rectangle Overlap | |
| Download Facts | |
| P-value to a Layman | |
| First Touch Attribution | |
| Job Recommendation | |
| Bagging vs Boosting | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with medium-level data structure problems, such as rotating an array, finding a linked list's middle node, array manipulation or graph traversal. Some rounds also mixed in resume or project discussion, while one candidate reported coding only. Expect to explain your reasoning clearly as you work.
One candidate reported a round on smoke testing, regression testing and test case design, including walking through edge cases for a feature. Other candidates reported conceptual questions on operating systems, hash maps, compilers, SQL, OOP or networking. The topics may vary by team and level.
Later rounds are reported to get harder. Candidates mention a 2D prefix sum with multithreading, hash map implementation trade-offs, building a tree and running DFS, and detailed questions about internship projects. One candidate described having to reason about performance trade-offs on the spot.
Two candidates who interviewed as Associate Software Engineers describe a final HR or managerial conversation after the technical rounds. Another candidate reported a hybrid final round mixing behavioral and technical topics. Outcomes differed: some candidates reported offers, while others were rejected or got no reply from the recruiter.
