Discover Software Engineer interview typically runs 4-6 rounds: recruiter screen, online assessment, technical screen, onsite interviews, behavioral. Timeline is about 2-4 weeks and is often manager-heavy and conversational.
$118K
Avg. Base Comp
$187K
Avg. Total Comp
4-6
Typical Rounds
2-4 weeks
Process Length
We’ve seen Discover lean hard on fundamentals, but not in a flashy way. Multiple candidates reported questions around indexing, APIs, and system design basics rather than deep algorithmic puzzles, and even the more technical conversations often stayed close to practical engineering tradeoffs. One candidate was asked to design an ecommerce application and explain how they’d scale it; another was pushed to reflect on how they would improve a solution with more time. That tells us Discover is looking for engineers who can reason clearly about everyday product and platform problems, not just recite theory.
A recurring theme is how much the company seems to value manager judgment and resume-level consistency. Several experiences describe a process dominated by managers or interviewers working from a fixed script, with questions about tenure, commute, on-call incidents, and disagreements with managers. That mix suggests Discover is screening for stability, communication, and low-drama collaboration as much as technical ability. We’ve also seen some candidates encounter a checklist-style interview that felt impersonal, which means polished, concise answers matter because there may be less room for a natural back-and-forth than at other companies.
The non-obvious signal here is that Discover appears to calibrate candidates against role level very explicitly. One rejected candidate was told their background fit better for a more senior application engineer role, which implies they’re paying attention to scope, ownership, and depth of experience. In practice, our candidates report that the strongest responses are the ones that connect past work to concrete engineering decisions — especially around APIs, scaling, and operational issues — while showing they can handle a structured, sometimes rigid interview style without getting thrown off.
Synthesized from 3 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 Discover process.
I was initially excited about the role, even though the recruiter told me upfront that the process would have four rounds, which already felt like a lot for a software engineer position. I still moved forward because the job seemed promising, but the first interview set a pretty rough tone right away. It was with a Quality Engineer on the team, and the conversation felt more like they were reading through my resume than actually trying to get to know how I work. There was also a noticeable language barrier, so a lot of the questions were hard to follow, and when I asked for clarification, the response was basically, “I don’t know, I’m just reading your CV.” That made it feel pretty impersonal and rushed.
The technical part of that round was mostly API-focused, so I spent most of the time talking through my experience with APIs rather than doing any coding or system design. It didn’t feel especially deep, but the way it was delivered made it harder than it should have been. The next morning, the recruiter emailed me saying they wouldn’t be moving forward, so I never got to the later rounds. I was disappointed because I had expected at least a more conversational screen before meeting the hiring manager. My main takeaway is to be ready to discuss API work clearly and concisely, but also to be prepared for an interview style that may feel more like a checklist than a discussion.
Prep tip from this candidate
Be ready to talk through your API experience in detail, since that was the main technical focus of the first round. Also prepare for a very resume-driven screen where you may need to clarify questions that are asked in a loose or rushed way.
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 Discover
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| P-value to a Layman | |
| Type I and II Errors | |
| International e-Commerce Warehouse | |
| Image Classification Pipeline | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Prime to N | |
| Cumulative Distribution | |
| Hurdles In Data Projects | |
| Over-Budget Projects | |
| Top 3 Users | |
| Google Maps Improvement | |
| Total Spent on Products | |
| Find the Missing Number | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates start with an online assessment that includes both coding questions and multiple-choice questions. It appears to be used as an initial filter before speaking with a recruiter.
A recruiter call follows, focused on your background, resume, internship or work experience, and general fit for the role. Candidates also get time to ask questions, and the recruiter may outline the rest of the process, including the number of rounds.
The technical interview can be conversational rather than coding-heavy, often with an engineer or infra engineer. Topics mentioned include APIs, basic system design, indexing, algorithms and data structures, and discussing how you would improve a solution if given more time.
Candidates reported being told to expect four additional rounds after the technical screen, and in one case this was exactly what happened. These rounds were mostly with managers and covered system design, technical fundamentals, and behavioral questions such as handling on-call issues, disagreements with a manager, and prior job tenure.
After the final interviews, candidates received a rejection or no-offer decision. Feedback in one case suggested the candidate’s experience and technical depth aligned more with a senior application engineer role.