Real, anonymous reports from people who interviewed for Software Engineer at Nomura, newest first and distilled into what to expect across the loop.
I started with a team-formation step, where the process kicked off by creating a small team of two. The expectation was that I’d pair up with someone whose strengths complemented mine, since picking a good teammate was treated like a critical part of the process.
The process for me stretched across five rounds: an online assessment first, then technical interviews, and finally interviews with managers. Each round ran for about an hour, and the format stayed fairly consistent in how it tested fundamentals and how I handled structured questioning.
The interview process typically consists of multiple rounds, including an initial recruiter call, followed by technical interviews focused on Java, system design, and behavioral assessments. Candidates should expect a mix of technical depth and organizational fit discussions throughout the process.
Candidates will face questions primarily centered on Java fundamentals, system design, algorithms, and database management, including SQL and concurrency topics. It's crucial to be well-prepared on these subjects, as they form the core of the technical evaluations.
Behavioral interviews are integrated into the process, often focusing on past experiences and how candidates align with the company's values and team dynamics. Candidates should prepare to discuss their motivations and how their experiences relate to the role.
The interview environment can vary, with some candidates reporting a collaborative atmosphere while others experienced interruptions or a lack of warmth. Being prepared for different interviewer styles and maintaining composure under pressure is important.
Many candidates noted a lack of feedback following their interviews, which can be frustrating. It's advisable to seek clarification on performance and outcomes, as the communication around decisions may not always be clear.
Candidates should be aware that some interviews may focus heavily on theoretical knowledge rather than practical application, which can lead to unexpected challenges. Practicing clear communication and grounding answers in real-world experience can help mitigate this.