Talroo software engineer candidates report a math-first screen, often with a founder or CEO, before any coding. Here is what was asked, how the later rounds went, and how to prepare.
$188K
Avg. Base Comp
$200K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The defining feature of the Talroo software engineer interview is that it opens with math, not code. Across six candidate reports, most describe an online assessment of math questions, and several then describe a math interview with the CEO or founder. Candidates describe geometry (squares, areas, grid and cube problems), combinatorics, and probability, with a few mentioning number theory or college-level topics.
The founder round looks like the main filter. Several candidates say one missed problem ended the interview, and three of the five no-offer reports ended at this stage. One candidate said they were told solving the first question was the bare minimum. Another reported being asked to explain every step, so practice showing your reasoning, not just final answers.
Candidates who got past the math describe a more conventional loop. One intern reported a coding round with LeetCode-medium problems, then a relaxed final round mixing behavioral and scenario questions. An associate-level candidate described same-day interviews with HR, the CTO, and an engineer, with medium-hard coding questions. A full stack candidate reported easy DSA, React theory, and SQL.
For preparation, spend real time on competition-style geometry, spatial reasoning, and counting problems, then keep your standard algorithm practice sharp. Talk through your thinking aloud, since one intern said the engineers cared more about reasoning than exact answers. Reports are limited and vary by role, so expect some differences.
Synthesized from 8 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 Talroo process.
I cleared the initial OA, which felt like a good sign, but then things took an unexpected turn. The next round was a math interview conducted by the CEO himself, and honestly, it threw me off. He set the bar pretty straightforwardly—solve the first question and you're meeting the bare minimum. I didn't manage it. The questions were geometry-focused: one involved figuring out the side length of a large square supported by three smaller squares, another was about calculating areas. There were also some probability and combinatorics problems mixed in, like permutation questions with constraints. The whole thing lasted about an hour, and the CEO went through my resume briefly before diving into the math. What caught me off guard wasn't just the difficulty, but the nature of the questions themselves. I came in expecting algorithmic challenges or system design—typical software engineering interview material—but instead I got high school geometry and number theory. The CEO's framing suggested these were screening questions, and if you pass, you'd move on to actual technical rounds with LeetCode-style mediums and hards. But the math interview felt disconnected from the role. The approach required a lot of intuition and clever geometric insight rather than a structured problem-solving method you could methodically work through. I walked away frustrated, not because the questions were hard, but because I couldn't see how they predicted coding ability. No offer came through.
Prep tip from this candidate
If interviewing at Talroo, expect the CEO to conduct a math screening round before technical interviews—brush up on geometry, combinatorics, and number theory problems with constraints, as they weigh intuition heavily and feel deliberately disconnected from standard SWE prep.
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 Talroo
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Employee Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Comments Histogram | |
| Top 3 Users | |
| String Shift | |
| Flight Records | |
| Rolling Bank Transactions | |
| Find the First Non-Repeating Character in a String | |
| Customer Orders | |
| Minimum Change | |
| Raining in Seattle | |
| Like Tracker | |
| Weighted Keys | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| First Touch Attribution | |
| Prime to N | |
| Job Recommendation | |
| Find Bigrams | |
| P-value to a Layman | |
| Largest Salary by Department | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment of about four questions, with two describing it as 35 minutes. Topics reported include combinatorics, exponents, geometry, integrals, and probability. One candidate also described an egg-drop style algorithm question answered in prose. Difficulty is described as anywhere from straightforward to competition-level.
Several candidates describe a video or live session with the CEO or founder, typically three math or geometry problems. Reports say a single miss can end the interview, and some got little feedback or friendliness. One candidate reported it lasted about an hour and included a brief resume review. Three of the no-offer reports ended at this stage.
Candidates who advanced describe coding questions at LeetCode medium or medium-hard level with an engineer or the CTO. A full stack candidate reported easy DSA problems, React theory, and SQL. One intern also reported a conceptual discussion on neural networks that tested reasoning rather than expertise.
Some candidates report an HR or behavioral conversation, and one intern described a final round mixing behavioral questions with describe-your-approach scenarios without writing code. Outcomes after this stage varied. One reported an offer, while others reported rejections within about a day.
