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.
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 Dezerv process.
The interview process had 7 rounds in total: a coding round, a testing and technical round, three technical rounds with different hiring managers, then a round with the director and finally HR. The first two rounds were the most hands-on, and after that the last four rounds were all called to the office, which made the process feel pretty long. Overall it wasn’t very difficult, but it was definitely more focused on how I think about testing, frameworks, and practical engineering decisions than on hard algorithm problems.
In the technical discussions, I was asked to design test cases for an online chess game, talk through framework design, and explain authentication versus authorization. There were also questions around Pytest and REST APIs, so they wanted to see whether I had real experience working with testing tools and service-level concepts. The interviewers also kept bringing up the 5-day work-from-office expectation, and I got the sense they were checking whether I would be comfortable with that in every round. What was frustrating was that they kept saying the feedback was positive, but I still received a rejection letter just before the HR round. That was disappointing after going through so many stages. My takeaway is to be ready to speak clearly about testing strategy, API basics, and how you would structure test coverage for a real product, especially something stateful like a game.
Prep tip from this candidate
Be ready to design test cases for a stateful product like an online chess game, and review Pytest plus REST API fundamentals. Also prepare to answer directly about your comfort with a 5-day work-from-office setup, since that came up repeatedly.
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 | |
|---|---|
| Top Three Salaries | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top 3 Users | |
| Prime to N | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Find the Missing Number | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Minimum Change | |
| Maximum Profit | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Last Transaction | |
| Sum to N | |
| Delivery Estimate Model | |
| Payments Received | |
| The Brackets Problem | |
| Third Purchase | |
| Like Tracker |
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.