ING Hubs Spain interview process & guide 2026
Everything we know about interviewing at ING Hubs Spain: the process stage by stage, what each round tests, compensation by level, and reports from candidates who interviewed.
- 1Initial Screening (HR and application review)
- 2Technical Assessments (screens, coding, take-home style work)
- 3Technical Evaluations and Competency/Case Rounds
- 4Final Assessment and Cultural/Leadership Fit
Interviewing at ING Hubs Spain
ING Hubs Spain runs a multi-step hiring loop that usually starts with an HR screening and then moves into technical evaluations, with later stages focusing on overall fit. Across candidate reports, the tone is often described as professional or positive, but multiple reports highlight poor communication afterward, including no follow-up or minimal feedback.
The topics show you what they test. They strongly emphasize Java, SQL, Kotlin, and structured engineering ecosystem knowledge like Spring Boot. For role competencies, they also include Business Analysis, Product Management principles, DevOps Engineering, Data analysis, Apache Spark, Financial Accounting, Task-based design exercises, and technical interviewing that can include machine learning and AI topics.
Expect a funnel, where early technical screens can reduce the candidate pool quickly, and later rounds may feel more selective or intense. Timelines reported by candidates vary, with some seeing a process finish in about four weeks and others describing waits around a month or unclear waiting with delayed or missing updates.
From candidate reports, the most recurring non-technical failure point is not the interview content but the post-interview communication, including silence after multiple rounds and lack of meaningful feedback when you do not progress.
How hard is the ING Hubs Spain 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- 1Initial Screening (HR and application review)
You start with an HR-style screening to assess your background and motivation, plus an initial review of your application and qualifications. Candidate reports often describe a recruiter call or HR conversation as a first step before technical work begins.
- 2Technical Assessments (screens, coding, take-home style work)
You undergo technical assessments that can include live coding or take-home assignments to evaluate relevant technical skills. The topics data strongly points to Java and SQL, and also includes role-specific areas like Spark, DevOps, and Financial Accounting, depending on the track.
- 3Technical Evaluations and Competency/Case Rounds
You may have deeper technical evaluations and practical case-style work that mirrors tasks performed by the team. Some reports describe pair-programming elements, and the topics data indicates they may test Business Analysis, Product Management principles, data analysis, and technical interviewing covering areas like machine learning and AI.
- 4Final Assessment and Cultural/Leadership Fit
The loop can end with final assessment steps that evaluate overall fit, sometimes including senior leadership discussions and cultural fit. Candidate reports also mention face-to-face style interviews with team or chapter leads focusing on technical discussions and behavioral alignment.
What ING Hubs Spain 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 Hubs Spain 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 Hubs Spain 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 for Java and SQL fundamentals and be ready to discuss practical relational database work, not just theory. Several reports describe Java-centric panels and relational database focus.
- Practice live coding or collaborative coding without relying on an IDE. Reports mention coding on a board, pair-style problem solving, and collaborative execution.
- Be ready for structured, role-aligned exercises like take-home assignments, case studies, and task-based design. Candidates reported backend take-home work, research-focused case studies, and exercises tied to how teams work.
- Align your answers to past experience and how you operate in Agile or team settings. Behavioral and competency-style conversations are repeatedly mentioned as part of the loop.
Avoid this
- Do not assume you will receive clear closure or detailed feedback if you do not get an offer. Multiple reports describe no follow-up or minimal clarification after interviews.
- Avoid memorizing a list of exact commands at the expense of explaining your approach. One report describes a grilling centered on specific commands, and candidates can get tripped up when recalling exact details.
- Do not treat timing and interaction as secondary in live coding. One report notes awkward flow, dead air, and issues with running past allotted time, which affected how the assessment was perceived.
- Do not share sensitive information if they ask to share your screen unexpectedly. At least one report mentions being asked to share screen without warning, causing privacy concerns.
ING Hubs Spain interview FAQ
Answered from real candidate and workplace dataWhat is the overall difficulty and how should I calibrate my prep?
Across candidate reports, 61.2% of experiences are medium difficulty, 22.2% easy, 14.4% hard, and 2.2% very hard. You should prepare for fundamentals and also expect that some rounds may be knowledge-check intensive, especially where Java, Spring Boot, and SQL come up.
Do candidates get offers from this process?
In the aggregated candidate data provided here, the offer rate is 0.0%. The sample reports also indicate that candidates did not receive offers in the reported experiences.
How long does the process take?
Candidate reports describe timelines of a few weeks to about a month. One report says roughly four weeks from start to finish, and another says about a month, but other reports focus on uncertainty due to missing follow-up.
What should I prioritize if I only have time for a top set of topics?
Prioritize Java, SQL, and Spring Boot, since these appear with very high prominence in the topics data. Then cover Kafka and performance tuning where relevant to technical rounds, and be prepared for role-specific areas like Business Analysis, Product Management, DevOps Engineering, Apache Spark, Financial Accounting, and data analysis.
Do they do coding interviews or take-homes?
Yes. The process includes technical assessments with take-home projects and live coding or similar practical coding sessions. Candidate reports mention online coding tests, live coding on a board, and take-home assignments related to backend functionality or structured research exercises.
Can I expect feedback after interviews?
Do not rely on detailed feedback. Multiple candidate reports describe abrupt negative responses with very little detail, and several describe waiting with no follow-up communication from recruiters after interviews.
Related company guides
Companies that hire for the same data roles
Ready for your ING Hubs Spain interview?
Practice the exact questions from this guide with AI feedback, and walk into your loop knowing what to expect.