Nasdaq Software Engineer interview typically runs 5 rounds: recruiter phone screen, online assessment, technical screen, technical interview, onsite. It usually takes a few weeks and is highly structured and technical.
$109K
Avg. Base Comp
$165K
Avg. Total Comp
5-6
Typical Rounds
3-6 weeks
Process Length
Our candidates consistently describe Nasdaq as a process that looks broad on paper but is really trying to answer one question: can you ship reliable software in a finance-adjacent environment? The strongest signal is the repeated mix of CS fundamentals plus applied coding. Multiple candidates reported being tested on operating systems, networks, DBMS, cloud concepts, and debugging alongside standard algorithm problems, which tells us Nasdaq is not satisfied by LeetCode fluency alone. They want engineers who can reason about how systems behave under load and explain tradeoffs clearly.
A recurring theme is that the interviews become more revealing once they move past the assessment. We’ve seen resume-driven technical conversations where interviewers kept digging into how candidates solved problems in past projects, and manager discussions that focused on performance improvements and issue handling. That pattern suggests Nasdaq values specific ownership stories over polished generalities. Candidates who could walk through what they changed, why it mattered, and how they measured impact seemed better aligned than those offering high-level summaries.
We also see a practical bent in the later technical work: one candidate faced Vue CRUD tasks, another had to implement backend code to satisfy tests, and others were asked about real-time processing and hash maps. That combination points to a team that cares about working code, not just correct answers. In our view, the non-obvious make-or-break factor here is whether you can stay calm when the prompt shifts from theory to implementation detail and still show disciplined engineering judgment.
Synthetized from 2 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 Nasdaq process.
The process felt pretty structured overall, and the hardest part for me was the online assessment. That was a 2-hour OA with a mix of CS fundamentals and coding. They covered computer networks, operating systems, and DBMS, and then there were four coding questions in total: one easy, two medium, and one hard. It was a lot to fit into one sitting, so time management mattered as much as knowing the material. After that, the rest of the process was more conversational and less intense. I had a phone screen, then an initial technical round that was mostly basic Java questions, and then another technical interview that leaned more toward LeetCode-style problems. The questions there were the usual kind of thing around real-time processing and hash maps, plus some motivational questions mixed in. I also had a hiring manager round where they went through my resume and asked me to explain how I handled an issue and what I did to improve performance. The interviewers were generally nice and the process was organized, but it still felt thorough and fairly technical throughout. In the end I didn’t get an offer, so I’d say the main thing to prepare for is a broad OA with both theory and coding, plus being ready to talk clearly about your past projects and performance improvements in the manager round.
Prep tip from this candidate
Be ready for a 2-hour OA that mixes CS fundamentals like networking, OS, and DBMS with four coding problems of increasing difficulty. Also prepare to explain resume projects in detail, especially performance improvements and issue resolution, since that came up in the hiring manager round.
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 Nasdaq
Design a database schema for a blogging platform.
| Question | |
|---|---|
| Subscription Overlap | |
| Prime to N | |
| Find the Missing Number | |
| Rectangle Overlap | |
| Hurdles In Data Projects | |
| String Subsequence | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Radix Addition | |
| Binary Tree Validation | |
| Find Duplicate Numbers in a List | |
| Most Repetition | |
| Target Indices | |
| Dijkstra implementation | |
| Filling Supermarket Bag | |
| Median O(1) | |
| Messenger Service Design | |
| Target Value Search | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Concurrent LLM Serving | |
| Finding the Maximum Number in a List | |
| Moving Window | |
| Check Matching Parentheses | |
| String Palindromes | |
| 5th Largest Number | |
| Confidence Interval Explanation | |
| NxN Grid Traversal |
Synthesized from candidate reports. Individual experiences may vary.
An initial call with the recruiter to review your background, experience, and basic fit for the role. This stage is mostly conversational and helps determine whether you move forward to technical rounds.
A timed coding and fundamentals test covering computer science topics such as operating systems, networks, DBMS, cloud computing, data structures, and debugging. Candidates reported 4 coding questions in one version of the OA, with a mix of easy, medium, and hard problems, so time management is important.
A technical interview that can include basic language questions, resume-driven discussion, and standard coding problems. Candidates described questions ranging from Java fundamentals to LeetCode-style problems and practical problem-solving around past projects.
A deeper technical round, sometimes with a specific team such as the European team, focused on data structures and algorithms plus discussion of how you solved problems in previous work. Reported questions included stock trading, playlist-style problems, real-time processing, and hash maps.
A manager round centered on your resume, project impact, and how you handled issues or improved performance. This stage is more behavioral and impact-oriented, but still technical enough to probe your decision-making and execution.
The final stage was described as an in-person, hands-on interview with multiple practical components. It included frontend work in Vue on a CRUD-style task, backend implementation from tests in a test-driven-development style, and a system design discussion.