ING interview process & guide 2026
Everything we know about interviewing at ING: the process stage by stage, what each round tests, compensation by level, and reports from candidates who interviewed.
- 1Recruiter Screen
- 2Technical Assessments and Technical Interviews
- 3Behavioral, Scenario, and Manager or Leadership Discussions
- 4Final Decision
Interviewing at ING
ING’s interview loop is a mix of HR screening, technical assessments, and conversations that emphasize fit and leadership. Across reported experiences, the technical parts are often panel-based and structured, with a noticeable emphasis on Java and databases, plus additional role relevant areas like Spring Boot and Terraform for the relevant tracks.
What gets tested, based on the extracted topic set, is technical depth and reasoning (Java, SQL, Spring Boot, quality assurance/testing for QA, and modeling or domain analysis like DCF, IRRBB, and market outlook analysis), plus problem solving and communication (case study evaluation and scenario-based problem solving). For finance and risk-adjacent roles, the topics directly include DCF modeling, IRRBB, and market outlook analysis, and for other tracks you should still expect structured evaluation of how you think through real tasks.
The process timing varies in the reports, with some candidates moving quickly and others experiencing long waits or unclear follow-up. Even when interviews go well, the candidate reports show that outcomes can end without an offer, and the overall offer rate from the reports provided is 0.0%.
From the question data, Java and SQL are absolute pillars (both at 100% prominence), and several of the reported loops include a live or interactive coding component, so your ability to reason through code and data together matters more than memorizing frameworks alone.
How hard is the ING interview?
Aggregated from 500 interview experiencesAbout 1 in 2 candidates with a known outcome convert.
The interview process, end to end
4 rounds · based on 500 candidate reports- 1Recruiter Screen
You start with an HR or recruiter-led screening to discuss your background and motivation, and to assess fit for the role. Some reported experiences include an additional HR-led screening step before technical work.
- 2Technical Assessments and Technical Interviews
You then move into technical evaluation that can include problem solving, live or interactive coding, and often panel discussions. Based on the topic data, expect Java and SQL as central themes, plus role-specific areas like Spring Boot, QA/testing, Terraform, and finance or risk modeling topics.
- 3Behavioral, Scenario, and Manager or Leadership Discussions
After technical work, you get assessed on cultural fit, leadership potential, and scenario-based problem solving. Some loops include discussions with managers or chapter leads, and others include leadership discussions focused on alignment with the bank’s values and strategic thinking.
- 4Final Decision
You reach a final decision stage involving stakeholders, which follows the last interview rounds. Candidate reports indicate that even after multiple interviews, outcomes can still end without an offer and follow-up can be slow or unclear.
What ING actually tests for
How prominent each skill is across reported loopsFind the guide for your role
This is your next step: open the guide for the role you are interviewing for. Each one carries the questions ING interviewers actually ask that position, the loop structure, and pay by level.
Real interview experiences
What candidates said about the loop, difficulty, and outcomes, straight from recent reports for these roles.
What ING pays, by level
Estimated total compensation: base salary plus stock and annual cash bonus.
What separates offers from rejections
Patterns from candidates who got offers, and the mistakes that most often sink a loop.
Do this
- Prepare to explain your Java fundamentals clearly under interactive conditions, including how you reason about code during live problem solving.
- Be ready to use SQL confidently, especially to discuss or apply database concepts as part of technical evaluation, not just as trivia.
- If you are interviewing for a role that touches modeling or risk, study how to structure your approach for DCF modeling, IRRBB, and market outlook analysis from the start, then communicate tradeoffs and assumptions.
- For behavioral and scenario questions, connect your experience to fit and leadership potential, because scenario-based problem solving and behavioral fit appear in the topic set.
Avoid this
- Do not assume the process will give you frequent closure once you pass early rounds, because multiple reports describe stalled or unclear communication after interviews.
- Avoid going into the coding or assessment stage without time management, because at least one report describes getting negatively impacted by time pressure during live coding.
- Do not treat the interview as purely casual, even when the tone feels friendly, because several reported technical sessions include deeper dives and interactive formats.
- Be careful with practicalities like screen sharing and privacy, because one report specifically mentions being asked to share a screen without warning.
ING interview FAQ
Answered from real candidate and workplace dataHow hard are ING interviews, based on candidate reports?
In the candidate reports you provided, difficulty is split into easy 22.2%, medium 61.2%, hard 14.4%, and very hard 2.2%. The topic set also shows a heavy presence of core technical areas like Java and SQL, plus additional specialized domains depending on the role.
What is the offer rate from these reports?
The offer rate from the supplied candidate reports is 0.0%. Positive sentiment is 66.0%, so interviews can feel positive even if the outcome is not an offer in the reported dataset.
How long is the process?
Timelines vary by candidate in the sample reports. One report mentions about four weeks overall, and another mentions stalling for about a month after being told an offer was coming. The extracted process steps do not provide a single consistent schedule.
What should I prioritize studying?
Prioritize Java and SQL since both are at 100% prominence in the topic data. Then align the rest to your target role: Spring Boot (97%), QA/testing (100% for QA roles), Terraform (100%), and finance and risk topics like DCF modeling and IRRBB (100% each) where relevant.
Is there case study or modeling work?
Yes. Case study assessment appears (percentile 62), and DCF modeling, IRRBB, and market outlook analysis each appear as prominent technical topics (all at percentile 100). Some reports also describe case study stages tied to research or modeling.
Do they re-contact you after interviews, and can you re-apply?
The reports you provided highlight communication problems, including silence after interviews and unclear updates, so you should be prepared for possible delays in follow-up. Your dataset does not include any explicit policy about re-application, so I cannot state how re-applying works.
What people say about ING
Verbatim snippets from employee and candidate reviews“Promotion opportunities are progressing slowly.”
“The pay is competitive for my level of experience.”
“Frequent restructuring creates uncertainty and a lack of clear career paths.”
“Focus on identifying and retaining high performers to strengthen the organization.”
“The work environment is average, heavily influenced by team dynamics and leadership.”
“Management should enhance communication with staff and be more receptive to employee feedback.”
Related company guides
Companies that hire for the same data roles
Ready for your ING interview?
Practice the exact questions from this guide with AI feedback, and walk into your loop knowing what to expect.