Discover software engineer candidates describe a manager-heavy loop that combines technical depth (Java, React, APIs, system design) with repeated behavioral rounds. Several reports involve adjacent engineering titles.
$110K
Avg. Base Comp
$125K
Avg. Total Comp
4-6 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Discover engineering roles describe a loop where behavioral conversations carry as much weight as the technical ones. The one full-time Software Engineer report mentions a 4-hour block with three managers asking very similar behavioral and situational questions, plus an hour-long technical interview of Java and React questions. It also included troubleshooting application slowness and improving page load speed.
Reports from adjacent engineering titles add context, though they are not the same role. A quantitative developer describes a technical screen, three behavioral rounds with senior managers, and a whiteboard system design session with a staff engineer. A principal engineer who received an offer describes five rounds covering Spring Boot, REST API design, Java, three medium coding problems and a hiring manager conversation. An applications engineer was asked to explain indexing and design a scalable ecommerce application. Others describe API-focused or resume-driven screens and an internship process with an online assessment.
Outcomes were mostly rejections. Several candidates describe long, manager-heavy loops, so prepare to sustain energy across many conversations. Have short, repeatable stories about past projects, tradeoffs, on-call incidents and disagreements with a manager. Be able to explain your stack hands-on, and rehearse performance troubleshooting aloud. Thin evidence means the exact loop may differ by team and level.
Synthesized from 6 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.
Had a 4-hour interview block with 3 managers, all asking very similar behavioral and situational questions. I also had a technical interview where the interviewer fired Java and React questions at me nonstop for an hour. Fortunately, I had plenty of hands-on experience in both areas to draw from.
Questions asked: How would you troubleshoot slowness in an application?
How would you improve page load speeds?
Prep tip from this candidate
Prepare concise behavioral and situational examples for manager conversations, plus hands-on explanations of Java, React, application slowness, and page-load improvements.
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 | |
|---|---|
| Type I and II Errors | |
| P-value to a Layman | |
| International e-Commerce Warehouse | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Client Solution Pushback | |
| Diagnosing Query Speed Degradation | |
| Image Classification Pipeline | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Payments Received | |
| Monthly Customer Report | |
| Top 5 Turnover Risk | |
| Total Spent on Products | |
| Merge Sorted Lists | |
| Top 3 Users | |
| Google Maps Improvement | |
| Find the First Non-Repeating Character in a String | |
| String Shift | |
| Find the Missing Number |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an early recruiter call that is largely conversational, covering the role, the resume and the number of rounds to expect. One candidate was told upfront to expect four rounds. Prepare a clear summary of your background and tech stack.
Reports differ by role. An internship candidate describes an online assessment with coding and multiple-choice questions, while others describe a technical screen centered on their resume or API experience. Candidates may be asked how they would improve a solution given more time, so be ready to discuss tradeoffs.
The Software Engineer report describes an hour of back-to-back Java and React questions. Other titles report Spring Boot, REST API design, indexing and ecommerce or system design whiteboarding. Prepare hands-on explanations of your own work and how you would troubleshoot slow applications and page loads.
Multiple candidates describe several rounds with managers, some asking similar questions. Topics reported include goals, past projects, job tenure, on-call incidents and disagreements with a manager. Prepare concise examples with the decisions you made, since the same story may be probed repeatedly.
Five of the six reports ended without an offer, including one rejection the morning after a first-round screen, while one principal engineer candidate received an offer. Feedback in one case pointed to a more senior fit. The total timeline is not clearly reported, so treat length as variable.
