Candidates for the Ziprecruiter Software Engineer role describe a timed four-question coding assessment as the main hurdle, with quick rejections common and only one report of later rounds.
$158K
Avg. Base Comp
$201K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Reports from candidates who applied for the Software Engineer role at Ziprecruiter center on one gate: a timed online assessment with four coding questions. Candidates describe 70 to 90 minutes on the clock where a time limit was given, and two name CodeSignal. Difficulty is uneven, with easy openers and much harder later questions, so pacing across all four problems is the main skill being tested. One candidate suggests scanning the set first and starting with the two easiest.
Question topics in these reports include 1D and 2D arrays, string manipulation, and an array-of-arrays-of-strings problem about free and paid items and storage space. One candidate recalls implementing a banking or restaurant system, which leans on object-oriented design. Another describes a geometry problem about objects whose square collision boxes overlap, plus an event-processing problem with string parsing. Long problem statements with many edge cases made careful reading important.
Outcomes were mostly quick. Three of the four candidates were rejected or did not advance at the assessment stage. One got a rejection email within about three days that cited headcount rather than performance, and another received an automated rejection with no human feedback. That candidate suspects passing all four questions is required, but it is a guess.
Only one candidate describes later steps: a phone screen with behavioral questions and a process overview, then a technical interview with ML-workflow coding on data preparation and problem formulation, plus a system design question. That candidate also did not get an offer, so treat those rounds as a single data point.
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 Ziprecruiter process.
When I applied for the Software Engineer role, I started with an online assessment containing four coding questions that ranged from easy to medium difficulty. My advice: don't tackle them in order. Scan through first, pick the two easier ones to build momentum, then circle back to the harder problems—it's a better use of your 90 minutes than grinding on a wall right away. After passing the assessment, I had a technical phone screen where the recruiter asked behavioral questions and walked me through the rest of the process, though it felt more like a checkpoint than a deep technical probe.
What struck me most about Ziprecruiter was how much the recruiter's demeanor mattered. The recruiting team I dealt with were genuinely helpful, warm, and responsive—they even offered to walk me through prep topics after I asked what to focus on. The technical interview itself featured coding problems tied to ML workflows: data preparation, problem formulation, and a system design question. These weren't abstract LeetCode problems; they had context and asked you to think about real pipelines. That said, the outcome still wasn't always a function of interview performance; at least one candidate who passed all rounds had the role vanish after weeks of waiting. The process is solid when things move, but communication gaps can leave you hanging.
Prep tip from this candidate
The ML-focused coding problems emphasize data preparation and problem formulation rather than pure algorithms—practice designing small components of ML workflows and think through data validation and edge cases in that context. Also take the recruiter's attitude as a signal; a warm, engaged recruiter usually correlates with a smoother 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 Ziprecruiter
Write a function to return the names and resume IDs for resumes whose IDs have not already been scraped
| Question | |
|---|---|
| Moving Window | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Top 3 Users | |
| Random SQL Sample | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Find Bigrams | |
| Size of Joins | |
| Upsell Transactions | |
| Longest Streak Users | |
| Google Maps Improvement | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| String Shift | |
| Download Facts | |
| Customer Orders | |
| Find the Missing Number | |
| Find the First Non-Repeating Character in a String | |
| Scrambled Tickets | |
| Comments Histogram | |
| Type I and II Errors | |
| Minimum Change | |
| Last Transaction | |
| Get Top N Frequent Words |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports receiving an assessment link within a few days of applying, and two name CodeSignal. The assessment has four coding questions, with reported time limits of 70 and 90 minutes. Difficulty climbs from easy to hard. Reported topics include arrays, 2D arrays, strings, geometry-style counting, event processing and a banking or restaurant system.
Most candidates in this set stopped here. One received a rejection email within about three days that cited headcount, another got an automated rejection with no feedback, and a third simply did not advance. One candidate suspects a score threshold or a requirement to pass all four questions, but that is an inference, not something Ziprecruiter confirmed.
One candidate who passed the assessment describes a phone screen where the recruiter asked behavioral questions and explained the remaining steps. The technical interview that followed had coding problems tied to ML workflows, covering data preparation and problem formulation, along with a system design question. Other candidates did not reach these steps, so the format may vary.
