Three candidates who received offers describe Dremio's software engineer interviews: practical coding, a code-review screen, system design that varied by report, and behavioral conversations. One process took about three weeks.
$154K
Avg. Base Comp
$188K
Avg. Total Comp
Not reported
Typical Rounds
3 weeks
Process Length
Across the three reports we have, Dremio's software engineer interviews favor practical engineering over puzzle-solving. One senior candidate described a tech screen built around reviewing code like a pull request, commenting on design, readability and structure instead of only hunting for bugs. That same candidate's coding round was a standard LeetCode medium, and they felt interviewers cared about how they solved problems and communicated. A software engineer candidate described two coding rounds leaning on graphs, trees and binary search, one with a domain-specific problem, and rated the difficulty as average.
System design differed between reports. The software engineer candidate got a design question built around a Snowflake-like system, and the interviewer pushed well past the high-level picture into distributed-systems detail. A senior candidate instead got a more localized, open-ended problem that rewarded creativity over a single right answer. Prepare for both a data-platform design and a looser problem.
Another senior candidate described hands-on network analysis and JVM troubleshooting, so practice explaining how you diagnose production issues and which tradeoffs you weigh. The same candidate had a more behavioral VP round and a conversational round with an engineering leader, across a remote loop of six one-hour interviews. Another senior candidate reported about three weeks from application to offer, with feedback within a working day. Keep concrete project stories ready. All three candidates received offers, but three reports is a small sample.
Synthesized from 4 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 Dremio 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 Dremio
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Largest Salary by Department | |
| Top 5 Turnover Risk | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N | |
| Minimum Change | |
| Upsell Transactions | |
| Top 3 Users | |
| Find the Missing Number | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Rectangle Overlap | |
| Scrambled Tickets | |
| Bagging vs Boosting | |
| Flight Records | |
| The Brackets Problem | |
| Project Pairs | |
| Maximum Profit | |
| Download Facts | |
| Level Of Rain Water In 2D Terrain |
Synthesized from candidate reports. Individual experiences may vary.
The software engineer candidate began with a recruiter reaching out, then a one-hour chat with the engineering manager about past experience, then a one-hour phone interview. A senior candidate described their hiring manager interview as warm, mixing behavioral questions with past projects. Prepare a clear account of your recent work.
One senior candidate was given code tied to a real-world scenario and asked to review it as a pull request, generating comments and improvements. They had to think about design, readability and how the code would live in a codebase, not just spot tactical bugs. Practice reviewing unfamiliar code and explaining your suggestions aloud.
The software engineer candidate had two coding rounds: the first on algorithms plus a walkthrough of past work, the second on algorithms with a domain-specific problem. They saw graphs, trees and binary search and called the difficulty average. A senior candidate described their coding round as a standard LeetCode medium.
Reports differ. The software engineer candidate faced a Snowflake-like design and was pushed into distributed-systems specifics such as work distribution, storage, metadata and failures. A senior candidate got a more localized, creative problem with no single right answer. Be ready to go deep and to explain your reasoning.
One senior candidate worked through network analysis and JVM troubleshooting, then had a behavioral VP round and a conversational engineering leader round, across six one-hour remote interviews. The software engineer candidate's final session covered past projects, a client-reported issue and their most complex project. Bring concrete stories.
