Dezerv Software Engineer interview typically runs 7 rounds: coding, testing and technical, three technical rounds, director, and HR. It usually takes several weeks and is notably office-heavy, with later rounds called onsite.
$65K
Avg. Base Comp
$69K
Avg. Total Comp
7
Typical Rounds
3-5 weeks
Process Length
We've seen Dezerv lean heavily toward day-to-day engineering judgment rather than puzzle-solving. In the candidate experience we reviewed, the conversation centered on test design for a stateful product, framework choices, authentication versus authorization, and REST API fundamentals. That mix tells us they want engineers who can reason through how software behaves in production, not just describe patterns in the abstract. The chess-game example is especially revealing: they seem to care about whether you can think through edge cases, coverage, and failure modes in a real system.
A recurring theme is that the interviewers kept returning to the company’s work-from-office expectation, even while the candidate was moving through technical conversations. That suggests culture fit and logistics are not treated as an afterthought here; they are part of the evaluation. We also noticed the feedback felt positive right up until a rejection before the final HR step, which points to a process where strong technical impressions may still be outweighed by alignment concerns or internal calibration.
For us, the non-obvious signal is that Dezerv seems to value engineers who can explain why a testing strategy makes sense, not just name tools like Pytest. Candidates who can connect framework decisions, API behavior, and test coverage to a real product workflow appear to match what the team is screening for.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Dezerv process.
The part I still think about is the call I got roughly thirty minutes after my hiring manager round. That round went really well, so hearing that my profile did not match their requirements caught me completely off guard, and I still don't have a clear explanation for it.
The process itself was very organized. Before anything started, the recruiter shared a PDF laying out every round and what they expected from each one, which made preparation much easier than most loops I've been through.
The first round was an online HackerRank assessment. It had a medium array problem and a hard one asking for substring search using a trie, and the trie question was the part I found toughest. I'd describe my performance there as average.
Next was a low-level design round, where I was asked to design an order management system for mutual funds that included a ledger. I didn't feel as strong here as I wanted to be, so that was also average. The high-level design round went much better. The prompt was to design the system I was currently working on at my job, so most of the time went into walking through my own architecture, the tradeoffs I'd made, and how it scaled. That felt good.
The last round was a hiring manager conversation focused on my past projects and experience. I thought it went great, which is why the rejection call came as such a surprise.
Prep tip: Be ready for a hard trie-based substring problem on the online assessment and a low-level design of a ledger-backed order system, since both came up. Be prepared to explain your past projects thoroughly.
Prep tip from this candidate
Be ready for a hard trie-based substring problem on the online assessment and a low-level design of a ledger-backed order system, since both came up. Another candidate for this role reported an LFU cache coding problem and a project discussion that went into every detail, so be prepared to explain your past projects thoroughly.
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 Dezerv
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| String Shift | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Bagging vs Boosting | |
| Top 3 Users | |
| Total Spent on Products | |
| Cumulative Distribution | |
| Size of Joins | |
| Minimum Change | |
| Google Maps Improvement | |
| Prime to N | |
| Maximum Profit | |
| P-value to a Layman | |
| Largest Salary by Department | |
| Over-Budget Projects | |
| Sum to N | |
| Over 100 Dollars | |
| Hurdles In Data Projects | |
| Find the Missing Number | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with a hands-on coding interview focused on practical implementation skills. Candidates should be ready to solve programming problems and demonstrate clear thinking under time pressure.
This round emphasizes testing strategy and core engineering fundamentals rather than hard algorithmic problems. Expect questions on designing test cases for real products, Pytest, REST APIs, and concepts like authentication versus authorization.
There are three separate technical interviews with different hiring managers. These discussions go deeper into framework design, practical engineering decisions, and how you would approach building and testing product features.
After the hiring manager interviews, candidates meet with the director for a final technical or leadership-level discussion. This stage appears to assess overall fit, engineering judgment, and alignment with the team’s expectations, including the work-from-office requirement.
The final stage is an HR conversation, which in this experience was scheduled after the director round. In the reported case, the candidate was rejected before reaching this step, but it is part of the stated process.
