Nasdaq Data Analyst interviews, as candidates describe them, mix SQL and resume deep-dives with take-home or exam-style work, plus behavioral and motivation questions. Formats varied across the three reports.
$95K
Avg. Base Comp
$110K
Avg. Total Comp
Not reported
Typical Rounds
1 month
Process Length
Three candidates describe Nasdaq analyst interviews that differed noticeably, so prepare for range rather than one fixed format. One candidate reports four rounds, three technical and one HR, preceded by an emailed exam. Another reports a phone screen, a Zoom technical interview, and an in-person stage, along with a homework task. A third describes only a roughly twenty-minute Zoom screen with the hiring manager and a team member.
SQL and resume depth came up most clearly in the technical reports. One candidate was asked about listed projects, then mostly SQL, medium-level problem solving, a few OOP concepts and puzzle-style questions. Another was asked the difference between left and inner joins and also about BI tools and analysis methodologies. Be ready to explain every project on your resume in detail and to write basic joins comfortably.
Exam and homework tasks appear in two of the reports. One candidate found the exam realistic for repetitive day-to-day work. Another said the homework ran well past the stated time and received no feedback. If you get one, confirm the time expectation upfront and ask for clarification if the scope seems off.
Fit questions can carry real weight. One candidate was asked about long-term plans and office attendance of three days a week. Another was asked what they knew about Nasdaq, why the analyst role, what challenge they overcame, and which securities or sectors interested them. Prepare a clear view of Nasdaq's business and a concise story about a challenge. Outcomes were mixed: two offers and one no offer.
Synthesized from 3 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 Nasdaq process.
I applied through Workday and heard back within a week for a phone screening. The initial conversation covered behavioral ground — they asked about my long-term plans in Vilnius and whether I could commit to three days a week in the office. This felt like a cultural fit check more than anything technical. I advanced the same day and moved into a Zoom interview a few days later. That's where the technical component showed up. They asked SQL questions, including one about the difference between left and inner joins, and probed my knowledge of BI tools, data analysis methodologies, and general familiarity with newer analytical frameworks. The questions felt broad rather than deeply specialized, touching on design thinking in analysis and tools across the modern data stack. After that, I was invited for an in-person interview at the Nasdaq office. I was told I'd advance to the next stage the same day if things went well. The whole process from application to decision moved pretty quickly — roughly a month from start to finish, which was faster than I expected. One thing that stood out as odd: after I submitted a homework task earlier in the process, there was no feedback or communication about it. The task itself was more involved than described and took considerably longer than the stated time estimate. It felt like different parts of the organization weren't fully aligned on what they were looking for, which made it hard to know if I was on the right track. By the end, despite making it through multiple rounds, I didn't receive an offer.
Prep tip from this candidate
Expect SQL fundamentals like join types and general BI tool knowledge rather than deep algorithmic problems. Be prepared to discuss your commitment to office presence and long-term location plans — those were weighted parts of the screening. Also, if you get a homework task, clarify the time expectation upfront and don't hesitate to ask for clarification if the scope feels misaligned with what you were told.
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 | |
|---|---|
| Fair Coin | |
| Find the Missing Number | |
| Subscription Overlap | |
| Prime to N | |
| Bank Fraud Model | |
| Hurdles In Data Projects | |
| Assumptions of Linear Regression | |
| Google Maps Improvement | |
| Triplet Counting | |
| Confidence Interval Explanation | |
| Decision Tree Evaluation | |
| Radix Addition | |
| Missing Housing Data | |
| Production Model Monitoring | |
| Find Duplicate Numbers in a List | |
| Dijkstra implementation | |
| Target Indices | |
| Car Recommendation Architecture | |
| Evaluate News | |
| 85% vs 82% | |
| Filling Supermarket Bag | |
| Median O(1) | |
| 5th Largest Number | |
| Client Solution Pushback | |
| RAG Strict Source Control | |
| Concurrent LLM Serving | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Data Preparation for Imbalanced Data | |
| Check Matching Parentheses |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a first conversation by phone or Zoom, sometimes about twenty minutes, covering motivation, knowledge of Nasdaq, background and practical items like salary expectations, shift availability or office commitment. Expect fit questions early, though details may differ by team.
Two candidates mention an exam or homework task. One describes an emailed exam that previewed repetitive day-to-day work; another says the homework took far longer than the stated time and drew no feedback. It may not apply to every team, so clarify scope and timing if you receive one.
Candidates report technical conversations centered on resume projects and SQL, including left versus inner joins, plus BI tools, analysis methodology, medium-level coding or problem solving, a few OOP concepts and some puzzle-style questions. Depth seems practical rather than highly specialized, but this varies by report.
One candidate reports an HR round focused on fit after three technical rounds, and another was invited to an in-person interview at the Nasdaq office. Outcomes differed, with two offers and one no offer, so treat the later stages as a final check on skills and fit rather than a fixed sequence.
