Carvana Software Engineer interview typically runs 6 rounds: hiring manager, coding, data science, leadership, system design, and product. The process can take months and is notably broad for the role.
$92K
Avg. Base Comp
$178K
Avg. Total Comp
6
Typical Rounds
2-4 months
Process Length
Our candidates report that Carvana is looking for engineers who can move comfortably across the stack of problems the business actually faces, not just someone who can clear a single technical hurdle. The strongest signal in the experience we saw is breadth: one candidate described a mix of LeetCode-style medium coding, system design, product discussion, and leadership-oriented conversation. That combination suggests Carvana is screening for people who can reason about tradeoffs in a consumer marketplace, not just write correct code in isolation.
A recurring theme is that the interviews can feel a little uneven, which makes clarity in your answers especially important. The candidate noted that some interviewers seemed less prepared and that the conversation sometimes became repetitive, so the people who stand out here are the ones who can keep their thinking structured and bring the discussion back to concrete decisions. We’ve also seen that the company seems to care about how you handled a tough call in a previous role and what you valued in your last team, which points to a preference for engineers who can explain judgment, not just execution.
The other non-obvious factor is patience. This process can stretch out, and the long silence afterward was a major source of frustration in the experience we reviewed. That means candidates who stay consistent across a broad loop — especially when the questions span coding, design, and product thinking — are likely to make the strongest impression. At Carvana, the bar appears to be less about any single brilliant answer and more about whether you can operate as a practical, cross-functional engineer in a business that runs on speed, efficiency, and customer experience.
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 Carvana process.
Carvana reached out to me on LinkedIn, and after that the process moved into a fairly long interview loop. The first round was a 30-minute hiring manager conversation, which was mostly an overview of my background and fit for the role. The questions were pretty standard at that stage, like telling them about myself and talking through how I’d handled a tough call in a previous job and what I liked about my last position. After that, I had a 1-hour coding round, and then the onsite was broken into several separate interviews: a data science round, a leadership round, a system design round, and a product round. Overall it felt like a lot of rounds for a software engineer role, especially since there was also one behavioral interview and four technical ones in the broader process.
The technical portion was a mix of system design, multiple LeetCode-style medium problems, and general technical discussion. Nothing felt wildly exotic, but there was enough volume that it started to feel repetitive, and I got the impression some interviewers were not especially prepared for the conversations. The process also dragged on longer than I expected; after completing everything, I waited months to hear back. The interviews themselves were mostly straightforward, but the combination of many rounds, a long delay, and limited feedback made the experience frustrating. I didn’t get an offer, so my main takeaway is to be ready for a broad loop that covers coding, design, product thinking, and leadership, and to expect the process to take a while.
Prep tip from this candidate
Be ready for a long loop that includes a 1-hour coding round plus separate system design, product, leadership, and even data science conversations. I’d also practice explaining your background and past tough decisions clearly, since the early rounds were very conversational before getting into technical depth.
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 Carvana
Precisely ascertain whether the outcomes of an A/B test, executed to assess the impact of a landing page redesign, exhibit statistical significance.
| Question | |
|---|---|
| Choosing Between Python and SQL | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Customer Orders | |
| Merge Sorted Lists | |
| Prime to N | |
| Random SQL Sample | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Scrambled Tickets | |
| Bagging vs Boosting | |
| Upsell Transactions | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Over 100 Dollars | |
| P-value to a Layman | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Recurring Character | |
| Address Schema | |
| Download Facts | |
| Permutation Palindrome | |
| Last Transaction | |
| Find the First Non-Repeating Character in a String | |
| Average Quantity |
Synthesized from candidate reports. Individual experiences may vary.
Carvana initially reached out on LinkedIn to start the process. From there, the candidate was moved into a longer interview loop.
The first formal interview was a 30-minute conversation with the hiring manager. It focused on background, fit for the role, and standard behavioral questions such as telling them about yourself, describing a tough decision, and discussing what you liked about your previous job.
This round was a technical coding interview with LeetCode-style medium problems. It was described as straightforward but part of a broader technical loop.
The onsite was split into several separate interviews, including a data science round, a leadership round, a system design round, and a product round. The overall technical portion covered coding, system design, and general technical discussion, with some behavioral and product-thinking elements mixed in.
After completing all interviews, the candidate waited months to hear back. The process ended with no offer, and feedback was limited.