Nomura Interview Questions (2026)
2 questions · GeeksforGeeks (2)
Top topics
Nomura Holdings Interview Experience (On-Campus)
Question Details
Nomura Holdings visited our Campus in
2021. Aptitude Round: Three Sections of questions: Verbal Quantitative Technical (Refer to Indiabix)
Technical Round 1: After entering the meet interviewer greeted me and started my interview with a simple question Tell me about yourself and what are your hobbies? He went through my resume and told me to explain all the projects in the resume. He asked to show any project present with me right now. All the Questions were Followed up related to Projects, how the project was made, team size, Everything in-depth, and most importantly about the database. ER diagram flow of my project. (covering all entity, relationship) How did I design my database? Difference between SQL and NoSQL. MySQL vs. Firebase. How Firebase works(I have used it in another project) What is primary key, foreign key what are the difference between them Unique key and primary key differences how I implemented these things in my project. My Login Page forgot password implementation and in detail about all the features in Database. API used in the project. Based on my project he asked what is the most important thing as per client which makes my project or any website user friendly (A UI and Designing of Database is expected) How will you design a project and what steps will you follow? (My answer was related to SDLC life cycle indirectly) Questions related to my social activities were asked in detail. Questions about my head of responsibilities were followed up and how I did it virtually in Lockdown. If a task is given and if I can not complete my task under the deadline, what will you do in that case? Then He Displayed a Database of Employee tables which consist of two tables. He asked me to write queries about: Joins(left) and asked why left join not inner join and the difference between them. And what other joins how they work. Maximum Salary from the table, since I gave him two methods he asked what limit does and max() function working. Select Distinct related query Count duplicate fields in a table. Questions I asked him: How a typical day at work looks in Nomura. Tech Stack Used.
Technical Round 2: Introduce yourself. Difference between pass by reference and pass by value, how it works, and example. Difference between Java and Javascript. Difference between Structure and Class. Swap two numbers without a third variable. What is Cloud Computing? How does it work? Puzzle of 7L,5L,4L water empty bucket. How to measure 6L. (similar to https://www.geeksforgeeks.org/aptitude/puzzle-measure-4l-using-given-3-buckets/) If I am a manager and I have a team of 5, one is on leave and one is sick and I have a deadline in the next 5 days and I am falling short of time, how will you deal with this situation? Questions I asked him: Internal Mobility in tech stack.
HR Round: Introduce yourself. What I do in my free time (one was reading and he asked me which book and name). Do I have any internship offers? Do I want to go for higher studies? Background about my family. TIP: You should know all projects and technologies In and Out. If you don’t understand any questions, ask the interviewer. Be confident about what you say (it is the most important thing). Go through Interviewbit questions according to the skills in your resume. Always smile even if you feel things are not going right. Look presentable, fresh and show interest by your body language. Do ask a question at the end. It shows your interest in the company.
Topics
More from Nomura
Related companies
Nomura Interview Process Overview
The Nomura interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show Nomura runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Nomura coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use Nomura Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Nomura updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in Nomura reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Nomura's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common Nomura Interview Mistakes
Reports tagged "no hire" at Nomura consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.