Glassdoor Software Engineer interview typically runs 4 rounds: engineer screen, take-home UI assignment, team interview, recruiter wrap-up. The process takes a little over two months and is notably frontend-focused.
$136K
Avg. Base Comp
$206K
Avg. Total Comp
3
Typical Rounds
2+ months
Process Length
We’ve seen Glassdoor lean much more practical than theoretical for software engineers. The candidate experience here points to a company that cares about whether you can turn product requirements into clean, working UI under real-world constraints. The take-home was described as straightforward in concept but easy to trip over if you missed the wording, and even the coding question hid edge cases that rewarded careful reading over cleverness. That’s a strong signal that precision with product specs matters as much as implementation quality.
A recurring theme is the balance between React fundamentals and product judgment. Multiple candidates report standard JavaScript and React questions, but they’re paired with conceptual UI design prompts rather than deep algorithm drills. That tells us Glassdoor is looking for engineers who can reason about component behavior, state, and user experience in the same conversation. We also see behavioral questions woven in naturally, which suggests they care about how you collaborate when things go wrong, not just how you code when things go right.
What makes or breaks candidates here is often less about raw technical depth and more about whether they can stay grounded in the prompt. Our candidates report that the process felt smooth and friendly, but the final decision still came down to execution details and how well the work matched the ask. In other words, reading the assignment exactly as written and showing sound frontend tradeoffs seem to be the real filters.
Synthetized from 1 candidates 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 Glassdoor process.
The part that stood out most to me was how much of the process was actually about practical frontend thinking rather than anything overly academic. It started with a 45-minute interview with an engineer where we mostly talked through my project experience, then moved into a 3-hour take-home UI assignment on CoderPad using React, TypeScript, and vanilla CSS. That take-home was straightforward in concept, but I had to be careful with the wording of the prompt and the inputs/outputs, especially because there was a JavaScript coding question about counting words that seemed easy until you paid attention to the edge cases.
After that, I had a very long 1 hour 45 minute team interview that was split into three parts. The first 45 minutes were technical with a senior engineer and included standard JavaScript and React trivia along with conceptual UI design questions. The next 45 minutes were behavioral, and they asked classic situational questions like a time I messed up and a time I had to resolve a conflict. The last 15 minutes were with the recruiter, mostly wrapping things up and giving me time for questions. Everyone was friendly and the process felt pretty smooth overall, even though there were a few delays and the whole thing took a little over two months from first contact to final update. In the end, they called to say they were moving forward with. My main takeaway was to be ready for careful reading on the coding task, and to expect a mix of React fundamentals, UI reasoning, and behavioral questions rather than deep algorithm work.
Prep tip from this candidate
Brush up on standard JavaScript/React fundamentals and be ready for conceptual UI design questions, since those came up alongside the take-home. Also practice reading coding prompts very carefully, because the CoderPad word-count task seemed simple but depended on getting the exact inputs and outputs right.
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 Glassdoor
Describing a data project and its challenges
| Question | |
|---|---|
| Liked and Commented | |
| Binary Tree Validation | |
| Legacy System Heartbeat Monitor | |
| Testing Constraints | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Weighted Keys | |
| Random SQL Sample | |
| Raining in Seattle | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Employee Salaries | |
| Delivery Estimate Model | |
| Over-Budget Projects | |
| Closest SAT Scores | |
| Download Facts | |
| Permutation Palindrome | |
| Job Recommendation | |
| Prime to N | |
| Upsell Transactions | |
| P-value to a Layman | |
| Monthly Customer Report | |
| First Touch Attribution |
Synthesized from candidate reports. Individual experiences may vary.
A first interview with an engineer focused mostly on discussing past project experience and general fit for the role. The conversation was practical and centered on frontend work rather than deep algorithmic problems.
A CoderPad take-home assignment using React, TypeScript, and vanilla CSS. The prompt was straightforward but required careful reading of the wording, inputs, and outputs, and included a JavaScript coding question with edge cases around counting words.
A longer panel-style interview split into three parts. The first 45 minutes covered technical questions with a senior engineer on JavaScript, React, and UI design concepts, the next 45 minutes were behavioral questions about conflict and mistakes, and the final 15 minutes were with the recruiter for wrap-up and candidate questions.