Nielsen Software Engineer candidates report three interview rounds centered on coding, core CS, project discussion, and, in one account, low-level and system design.
$120K
Avg. Base Comp
$140K
Avg. Total Comp
3 rounds
Typical Rounds
2-4 weeks
Process Length
Nielsen’s Software Engineer interview reports point to a coding-first process with role-specific variation. Two candidates described an online assessment before interviews: one had two coding questions plus 24 DBMS, OOP, and OS multiple-choice questions, while another report described DSA questions and MCQs. Prepare to solve easy-to-medium problems clearly, since reported examples included two pointers, hashmaps, strings, greedy techniques, dynamic programming, graphs, and a Four Sum-style problem.
The live technical stages also tested how candidates explain their work. One candidate completed two DSA rounds followed by a managerial round with project discussion and questions on database internals, OS, DBMS, and computer networks. A separate account described a screening, low-level design exercise, and system-design discussion: the design prompts involved a parking lot and a scalable URL shortener, with follow-ups on APIs, schemas, caching, load balancing, sharding, reliability, edge cases, and trade-offs. Treat those design prompts as one candidate’s experience, rather than a fixed template.
For preparation, practice reaching a well-reasoned solution—not merely a working one—then narrate complexity, assumptions, and alternatives. Refresh SQL and core CS concepts, and prepare a concise walkthrough of projects, tech choices, and outcomes. The available Software Engineer reports do not state a shared end-to-end timeline.
Synthesized from 5 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 Nielsen process.
The language requirement threw me. Nielsen required me to code in a specific language — for me it was Go — and even though I'm comfortable with it, there's something about live-coding on a compiler in a language you don't use every day that adds real pressure. That was definitely one of the biggest hurdles across the whole experience.
Nielsen's interview process had four rounds total. The first two were DSA rounds with easy-to-medium problems. One was a No. of Islands variation testing graph traversal logic, the other a string and stack problem. The format was consistent for both: explain your approach first, then code it live on their compiler. No surprises in the format itself, but the language constraint made it more challenging than a standard coding round.
The third round was Low Level Design where I had to design a Rate Limiter. That was quite different from pure algorithmic problems — less about optimizing for time and space, more about thinking through system architecture, edge cases, and trade-offs. The final round mixed HLD with managerial conversation about bigger architectural decisions and how I work in teams.
One thing that stood out: throughout all four rounds, they asked about my projects. What tech stack I chose, why I made those decisions, what I'd do differently. It wasn't a gotcha-filled interrogation. It felt like genuine conversation about how I approach problems. I got the offer.
Prep tip from this candidate
Practice medium-level DSA on strings and graph problems alongside system design—they asked about designing a Rate Limiter. Clarify your language requirement upfront and ensure fluency, since you'll be coding live in whatever they assign.
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 Nielsen
Implement a simple regex parser with operator support for '.' and '*'.
| Question | |
|---|---|
| Radix Addition | |
| Valid Anagram | |
| Production Model Monitoring | |
| Hurdles In Data Projects | |
| SageMaker Deployment Architecture | |
| Minimum Days for Scheduling All Meetings | |
| Scalable Data Pipelines | |
| Cross-Culture Reports | |
| Your Strengths and Weaknesses | |
| Parking Application System Design | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| String Shift | |
| Top 3 Users | |
| Raining in Seattle | |
| P-value to a Layman | |
| Comments Histogram | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records | |
| Largest Salary by Department | |
| Find the First Non-Repeating Character in a String | |
| First Touch Attribution | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report that an assessment may come first. One Software Engineer account had two coding questions and 24 MCQs covering DBMS, OOP, and OS; another described DSA questions plus MCQs. Expect the exact format and difficulty to vary by hiring path.
Candidates report two DSA-focused rounds in one path and a screening round in another. Reported problems included two pointers, hashmaps, strings, greedy methods, dynamic programming, graphs, and Four Sum. Be ready to justify the chosen approach and discuss edge cases.
One candidate reported a managerial round covering projects, database internals, OS, DBMS, and computer networks. Another reported low-level design of a parking lot and system design of a URL shortener, so design depth may depend on the interview path.
