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.
$164K
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.
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 Glassdoor process.
I went through what was supposed to be a four-round process—recruiter call, manager interview, technical screen, and leadership round—but it ballooned into nine rounds over two weeks. That initial mismatch between expectation and reality was frustrating, but I stuck with it.
The technical interviews were the main focus. I got asked about reversing a linked list, which was straightforward algorithmic work, but I also fielded questions on Kafka streams that felt disconnected from the actual job description. There were system design elements mixed in too, testing my broader problem-solving approach beyond just coding. The behavioral side covered standard territory: how I handle conflict, a time I overcame a challenge, that sort of thing.
What struck me most was the disconnect between what they said the process would be and what actually happened. Multiple technical screens piled up without clear signal about what each one was evaluating. The interviews themselves weren't hostile or disorganized—the team was collaborative and transparent when I asked questions—but the sheer volume felt like they were still figuring out what they needed. In the end, I didn't move forward, but the experience taught me to push back early on process expectations and ask for clarity on how many rounds are actually necessary.
Prep tip from this candidate
Be wary of scope creep in interview processes—ask upfront how many rounds are planned and what each evaluates. In this case, nine rounds with some questions unrelated to the role suggests unclear hiring criteria. Practice both standard algorithms (linked lists, reversals) and domain-specific questions (Kafka streams for platform roles) since technical breadth seems to matter more than depth here.
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
Write a query to get the percentage of users that have never liked or commented rounded to two decimal places
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Legacy System Heartbeat Monitor | |
| Binary Tree Validation | |
| Testing Constraints | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Monthly Customer Report | |
| Closest SAT Scores | |
| Top 3 Users | |
| Longest Streak Users | |
| Subscription Overlap | |
| Random SQL Sample | |
| Rolling Bank Transactions | |
| Weighted Keys | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Upsell Transactions | |
| Raining in Seattle | |
| Size of Joins | |
| User Experience Percentage | |
| String Shift | |
| Customer Orders | |
| Google Maps Improvement | |
| Find Bigrams | |
| Over-Budget Projects | |
| Last Transaction |
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.
