After a phone screen, I went through two more rounds with hiring managers, and the pace felt fast but still appropriately structured. The first two conversations were straightforward, then the third interview was where things really turned into a test of stamina.
That last stage was basically a full sheet of coding problems inspired by LeetCode. About fifteen questions fit into roughly forty-five minutes. Many of the tasks were on the easier side, but the constraint on time made it feel intense—especially because some problems required actually reading referenced documentation before you could even start coding. I left feeling like the overall difficulty wasn’t only about coding skill; it was about how quickly I could interpret the problem and move on under pressure.
7 months ago
Average Negative Paris
I went through a follow-up stage that was held in person with a SI developer and an analyst developer, and honestly the vibe was disappointing. The atmosphere felt off—there was pressure that didn’t feel necessary, and it came across as not very considerate. I ended the interview feeling like there wasn’t much real technical interest behind the process.
Even though the step was framed as a professional discussion, it didn’t end up giving me the chance to meaningfully demonstrate how I think technically. Instead, it felt more like a stressful interaction than a serious evaluation, and that left me underwhelmed overall.
10 months ago
Easy Positive Porto, Oporto
My process started like a lot of Natixis journeys I’d heard about: first a recruiter-style intro, then a technical step, and finally a conversation wi…
> 1 year
Average Positive Porto, Oporto
My interviews followed a simple, fairly approachable pattern. I started with an intro-style conversation focused on getting to know the team and expla…
> 1 year
Easy Positive Porto, Oporto
My first step was basically a conversation to get to know me as an internship candidate. There weren’t any technical questions at all—the goal was jus…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically consists of an initial HR conversation, followed by technical discussions and evaluations with team leads or managers. The overall timeline can vary, with some candidates experiencing delays of several weeks between stages.
HR interviewtechnical discussiontimeline
Technical Evaluation Focus
Candidates can expect a mix of coding challenges and technical questions that assess both software engineering fundamentals and domain-specific knowledge, particularly in finance-related concepts. The technical rounds often include practical tests and discussions about microservices architecture.
The coding rounds are often intense, featuring multiple problems under time constraints, similar to LeetCode-style questions. Candidates should be prepared for live coding sessions and practical exercises that evaluate their coding style and problem-solving approach.
live codingLeetCodeproblem-solving
Behavioral & Fit Assessment
Behavioral interviews focus on assessing cultural fit and communication skills, with interviewers looking for clear articulation of thoughts and teamwork capabilities. Candidates should be ready to discuss their experiences and how they align with the company's values.
Some candidates reported a mixed atmosphere during interviews, with feelings of pressure or lack of genuine technical interest from interviewers. It's important to remain adaptable and maintain a positive attitude throughout the process.
candidate experienceinterview atmospherepressure
Feedback & Communication
Communication from recruiters can vary, with some candidates experiencing delays or needing to follow up for updates. However, many appreciated structured feedback after technical evaluations, which helped clarify areas for improvement.