Babylist engineering candidates describe brisk recruiter and phone screens, plus one senior candidate's longer process with algorithms, coding and system design evaluations. Here is what they report and how to prepare.
$153K
Avg. Base Comp
$190K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Reports on Babylist's engineering interviews are thin, and only one of the three is for the Software Engineer title; the other two come from Senior Software Engineer candidates. Treat what follows as signals rather than a fixed loop.
The clearest pattern is that the opening conversation is brisk. The Software Engineer candidate had a recruiter call that ended well before its scheduled time. They were asked to walk through their current role, got short acknowledgments, and were moved to the next standard question. A senior candidate describes a phone screen of about thirty minutes that began the same way, with frequent interruptions. Neither advanced. The Software Engineer candidate received a standard rejection email later that same week. Prepare a tight two-minute account of your current role built around one concrete project and your own contribution, so your key points land even if you are cut short.
A third candidate, also senior, described a much longer process. It included a recruiter screen, a technical assessment, a hiring manager conversation, separate algorithms, coding and system architecture evaluations, and a cultural fit interview. The design prompt was a nationwide pickleball court management system. That candidate found the technical evaluation thorough and fair, but the verbal offer was later rescinded without feedback, so get terms in writing before resigning from your current job.
Synthesized from 3 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 Babylist process.
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 Babylist
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Subscription Overlap | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Customer Orders | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Prime to N | |
| Random SQL Sample | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Scrambled Tickets | |
| Bagging vs Boosting | |
| Flight Records | |
| Over 100 Dollars | |
| Upsell Transactions | |
| Retailer Data Warehouse | |
| P-value to a Layman | |
| Recurring Character | |
| Completed Shipments | |
| Size of Joins | |
| Project Pairs | |
| Address Schema | |
| Permutation Palindrome | |
| Download Facts | |
| Hurdles In Data Projects | |
| Nearest Common Ancestor | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Both the Software Engineer candidate and a senior candidate describe a first call that opened with a walkthrough of your current role, followed by short acknowledgments, interruptions and quick standard questions. One call ended well before its scheduled time, and the other lasted about thirty minutes.
One senior candidate describes an initial technical assessment and three separate evaluations covering algorithms, coding and system architecture. The design question asked for a nationwide pickleball court management system, framed as a broad, open-ended discussion of how the pieces fit together at scale. They found the evaluation thorough and fair, and said the difficulty came mostly from the number of rounds and the time commitment.
The same senior candidate also met the hiring manager and had a cultural fit interview. A verbal offer was then rescinded on the day of signing, with no explanation or feedback. Team reassignments during that process meant some reinterviewing as the role shifted. The other two candidates did not advance past their first screen; the Software Engineer candidate's rejection email came later the same week and did not mention the call.
