Numerator Software Engineer interview typically runs 1 round: a proctored online coding assessment. It usually takes about 1 hour and is broad across Python, SQL, and basic algorithms.
$118K
Avg. Base Comp
$187K
Avg. Total Comp
3-4
Typical Rounds
1-2 weeks
Process Length
Our candidates report that Numerator cares less about polished theory and more about whether you can move comfortably across the everyday stack a software engineer actually touches. The assessment wasn’t narrow: it mixed Python, MySQL, sorting logic, and a few algorithmic checks, which tells us they’re looking for breadth with enough depth to stay practical. Even the prompts felt grounded in real work — creating a SQL view, handling a file path in boto3/S3, or sorting structured data while preserving order — rather than abstract whiteboard puzzles.
A recurring theme is that the bar is not just correctness, but whether you can reason cleanly under a proctored, time-boxed setup. One candidate described the experience as “fairly robust and a bit heavy for the stage,” which is a useful signal: they seem comfortable using the screen to filter for candidates who can switch between data manipulation and basic DSA without losing precision. We’ve also seen that the questions can feel a little scattered, so the people who do best are usually the ones who can quickly identify the underlying pattern in each prompt instead of waiting for a familiar template.
What stands out most is that Numerator appears to value practical fluency over specialization. If you’re strong in one area but shaky in another, that imbalance is likely to show up here. The candidate feedback suggests they want engineers who can handle a broad, applied test without getting rattled by the mix of SQL, Python, and algorithmic reasoning.
Synthetized from 1 candidates 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 Numerator process.
The short version: I was approached by a recruiter who told me about this wonderful opportunity, and after a bit of back and forth I was sent a coding assessment link. The first step was a proctored online test on DoSelect, and it was pretty broad for a software engineer role. It ran about an hour and mixed Python programming, MySQL, and sorting/DSA questions, so it felt less like one focused coding challenge and more like a screen across a few different skills. The proctoring meant I had to make sure my internet was solid and that I was set up before starting.
The questions themselves were very practical but a little all over the place. I had to sort a 2D array of book title, author, and genre by genre while keeping the original order when genres tied, write SQL to create a view from an existing table, and solve a query about top-earning employees whose salary was above the overall average. There was also a question about how many iterations selection sort would take on an array, a pseudocode question where I had to identify what it was doing, and a grid-style algorithm question where movement was limited to right or down. In the earlier recruiter-led process, I also got asked things like adding a list of integers and returning the difference to the next closest Fibonacci number, plus a boto3/S3 question about listing the full name of a file. Overall, the assessment felt fairly robust and a bit heavy for the stage, especially if you were expecting a more standard backend screen. I didn’t move forward after that, so my main takeaway is to be ready for a proctored test that spans Python, SQL, and basic algorithms rather than just one area.
Prep tip from this candidate
Practice proctored-style timed questions that combine Python, SQL, and basic sorting/array logic in one sitting. Also review stable sorting behavior, selection sort iteration counts, and simple boto3/S3 file-listing tasks, since those showed up directly.
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 Numerator
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Random SQL Sample | |
| Prime to N | |
| Upsell Transactions | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Top 3 Users | |
| Closest SAT Scores | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Raining in Seattle | |
| Rectangle Overlap | |
| Hurdles In Data Projects | |
| Job Recommendation | |
| Minimum Change | |
| Google Maps Improvement | |
| Size of Joins | |
| Basic Regex | |
| Address Schema | |
| Nearest Common Ancestor | |
| Download Facts | |
| P-value to a Layman |
Synthesized from candidate reports. Individual experiences may vary.
A recruiter reaches out about the Software Engineer opening and shares details about the role. The candidate goes through some early back-and-forth before being sent forward to an assessment.
Before the formal test, the recruiter asked a few light technical questions to gauge baseline fit. Topics included adding a list of integers and returning the difference to the next closest Fibonacci number, plus a boto3/S3 question about listing the full name of a file.
Candidates complete a proctored DoSelect assessment that is broad for a software engineering role. It mixes Python programming, MySQL, sorting/DSA, and pseudocode questions, so candidates should expect coverage across multiple skill areas rather than one focused coding problem.
After the online test, the team reviews the submission and decides whether to continue. In this experience, the candidate did not move forward after the assessment, suggesting this stage serves as the main screen before later interviews.