For a junior Grubhub Software Engineer role, one candidate described a two-round process: a behavioral discussion of current work and a C#/.NET code-review interview.
$132K
Avg. Base Comp
$147K
Avg. Total Comp
2
Typical Rounds
Not reported
Process Length
The available Grubhub Software Engineer report describes two rounds: one behavioral and one technical for a junior role. The behavioral conversation focused on the candidate’s current project, their role in it, and how they would approach a complicated feature request. Prepare a concise project walkthrough that makes your own decisions and responsibilities clear, then be ready to explain how you would break down an ambiguous feature request.
The technical round was a review of C#/.NET code rather than a programming exercise in the report. Questions covered the meaning of a [Key] tag, why an ORM/database model may be separate from a public API model, and .NET service lifetimes including AddScoped. Review those concepts in context: explain the responsibility of each model boundary and the trade-offs of service lifetime choices, rather than relying on definitions alone. The candidate found the discussion fairly simple and linked that impression to the junior level.
This is a single candidate account, so team and level may change the emphasis.
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 Grubhub 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 Grubhub
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Download Facts | |
| Bagging vs Boosting | |
| Order Addresses | |
| Coin Dispenser | |
| Your Strengths and Weaknesses | |
| Tic-Tac-Toe Outcome | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Comments Histogram | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Weighted Keys | |
| Top 3 Users | |
| Random SQL Sample | |
| Over-Budget Projects | |
| Daily Retention Summary | |
| Prime to N | |
| Permutation Palindrome | |
| Upsell Transactions | |
| Delivery Estimate Model | |
| Raining in Seattle | |
| First Touch Attribution | |
| Find the First Non-Repeating Character in a String | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported a behavioral round centered on their current project and the role they played in it. Prepare a clear account of the project, your responsibilities, and the decisions you personally made; other teams may vary.
The same behavioral round included a question about approaching a complicated feature request. Candidates may be asked to explain how they would clarify the request, organize the work, and communicate their approach.
The reported technical round reviewed C#/.NET code and asked about `[Key]`, separate ORM and public API models, plus service lifetimes and `AddScoped`. Candidates should be ready to explain these concepts against the code in front of them.
