Discover Software Engineer candidates report a manager-heavy interview block centered on behavioral judgment, followed by Java and React questions, including application-performance troubleshooting.
$132K
Avg. Base Comp
$167K
Avg. Total Comp
4 rounds
Typical Rounds
2-4 weeks
Process Length
For a Discover Software Engineer interview, prepare for behavioral and situational conversations alongside practical web-engineering discussion. One candidate described a four-hour block involving three managers who asked similar behavioral and situational questions. That repetition makes it worthwhile to build several distinct examples that show how you handle ambiguity, collaboration, tradeoffs, and difficult situations, rather than relying on one story for every prompt.
The same candidate also had a one-hour technical conversation focused heavily on Java and React. Be ready to connect those technologies to work you have actually done: explain how you would investigate application slowness, identify likely bottlenecks, and improve page-load speed. A clear answer can move from observing the symptom, to isolating whether the issue is in the client, service, or data path, and then describing an appropriate improvement and how you would validate it.
This guide reflects one direct Software Engineer account, so the exact order and emphasis may vary. Still, the reported combination suggests practicing concise manager-facing stories and technical explanations aloud, with enough detail to show the reasoning behind your performance decisions.
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 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 | |
|---|---|
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Type I and II Errors | |
| Diagnosing Query Speed Degradation | |
| International e-Commerce Warehouse | |
| Image Classification Pipeline | |
| Testing Constraints | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Cumulative Distribution |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported a four-hour block with three managers. All three asked very similar behavioral and situational questions, so candidates may encounter repeated prompts that test whether examples stay specific and consistent across conversations.
The same candidate described an hour of rapid Java and React questions. Candidates should be prepared to discuss hands-on experience in both technologies and explain their reasoning, rather than assuming a coding exercise will be the sole technical format.
Reported prompts included troubleshooting application slowness and improving page-load speeds. Practice explaining how you would investigate a performance problem, select an improvement, and evaluate whether the change resolved the issue.
