Ing-Diba Quantitative Analyst interview typically runs 3 rounds: phone screen, two Microsoft Teams interviews. It usually takes a few weeks and is fairly structured, with a mix of HR and technical discussion.
$154K
Avg. Base Comp
$215K
Avg. Total Comp
3
Typical Rounds
1-3 weeks
Process Length
Our candidates report that ING-Diba is less interested in seeing someone “perform” quant work than in checking whether they can explain their background cleanly and connect it to the role. Across both experiences, the strongest signal was not a deep technical grilling, but a steady focus on how the candidate presents their CV, why they applied, and how they would add value to the team. That tells us the bar here is partly about judgment: can you communicate a quantitative profile in a way that feels structured, credible, and relevant to finance?
A recurring theme is that the interviewers also look for motivation and fit with the project, not just technical fluency. One candidate was asked about five-year plans and even whether they were “dynamic or static,” which suggests ING-Diba is paying attention to work style and attitude in a fairly direct way. For quant and risk profiles, our candidates also mention basic financial risk concepts and model explanations, but these seem to function more as a check on practical understanding than as a stress test. In other words, the company appears to reward candidates who can keep their answers simple, coherent, and business-aware.
We’ve also seen that the process can feel polished when the conversation stays conversational, but it becomes fragile when execution slips. One candidate noted that technical issues in the final conversation made it hard to show their strengths, and that mattered. The takeaway is that ING-Diba seems to form a strong impression from how well you stay clear under pressure and how naturally you tie your experience to the team’s needs. That final impression carries real weight here.
Synthesized from 2 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 Ing-Diba process.
The process started with a phone screen and then moved into two Microsoft Teams interviews, which was a pretty standard setup on paper but a bit rough in practice. The first Teams round went well enough and felt more like a mix of technical discussion and general work behavior. They asked me to explain how my background would help me succeed and bring value to the team, and there were also questions around technical documents and how I approach work. That part felt conversational and professional, and I got the sense they were trying to understand both my experience and how I’d fit with the team.
The final interview was where things got frustrating. Microsoft Teams had technical issues during the round, and even though we kept going, it was hard to really show what I could do. That definitely affected the flow, especially because the interview was already the most important stage. I wasn’t given a detailed reason afterward, just an email asking for feedback, and I ultimately wasn’t offered the job. From what I experienced, the process was smooth at the beginning and the team seemed polite, but the last round was undermined by the platform problems. My main takeaway is to be ready for a mix of behavioral and technical questions, and to make sure you can clearly explain your background and value quickly, since the process moved fast and the final impression mattered a lot.
Prep tip from this candidate
Be ready to explain exactly how your background translates into value for the team, and practice discussing technical documents and general work behavior clearly and concisely. Since the final round was affected by Teams issues, it also helps to have a crisp, structured answer ready in case the conversation gets interrupted or rushed.
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 Ing-Diba
How do we deal with the missing square footage data to construct our model
| Question | |
|---|---|
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Bagging vs Boosting | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top 5 Turnover Risk | |
| Top Three Salaries | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Monthly Customer Report | |
| Cumulative Distribution | |
| Slacking Employees Salaries | |
| Sum to N | |
| Variable Error | |
| Jars and Coins | |
| New Partner Card | |
| Compute Deviation | |
| Find the Missing Number | |
| String Shift | |
| Prime to N | |
| Compute Variance | |
| 500 Cards | |
| Session Difference |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with a phone screen from HR/recruiting. In this stage, they introduce the company and the project, explain the interview flow, and ask you to walk through your CV and prior experience. They also probe motivation for the role and basic fit questions such as where you see yourself in five years.
The first Microsoft Teams interview is a mix of technical discussion and behavioral/work-style questions. Interviewers ask how your background would help you add value to the team, how you approach work and technical documents, and may include questions around financial risk or model explanations for quantitative profiles.
The last round is another Microsoft Teams interview and appears to be the most important stage in the process. It continues the mix of technical and behavioral evaluation, with a strong focus on how clearly you can explain your experience and fit for the team; one candidate noted that technical issues on Teams affected the flow of this round.
