As a Software Engineer at ING, you are at the heart of the bank’s digital transformation. You are not just writing code; you are building the robust, scalable, and secure infrastructure that powers financial services for millions of customers worldwide. Whether you are working on high-frequency transaction systems, customer-facing mobile applications, or backend loan processing engines, your work directly influences the reliability and innovation of a global financial leader. The role demands a balance of deep technical expertise and a pragmatic, solution-oriented mindset. You will often work within Agile squads, collaborating closely with product owners, architects, and other engineers to translate complex business requirements into elegant software solutions. Success at ING requires a passion for clean code, a commitment to system performance, and the ability to thrive in a fast-paced environment where security and quality are non-negotiable.
Initial Screening
reportedA preliminary assessment to gauge your background and motivation for the role.
What to demonstrate
- A preliminary assessment to gauge your background and motivation for the role
- Depth in Java
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Deep Dives
reportedIn-depth technical interviews that may include conceptual questions, live coding, or take-home assignments.
What to demonstrate
- In-depth technical interviews that may include conceptual questions, live coding, or take-home assignments
- Depth in Java
How to prepare
- Answer aloud and timed: Can you describe the lifecycle of a Spring Bean?
- Answer aloud and timed: What are the advantages of using Functional Programming features introduced in Java 8?
Live Coding
reportedPrepare for potential live coding or screen sharing during the technical interviews.
What to demonstrate
- Prepare for potential live coding or screen sharing during the technical interviews
- Depth in Java
How to prepare
- Answer aloud and timed: How do you handle transaction management in a distributed system?
- Answer aloud and timed: How would you design an API Gateway for a microservices architecture?
Review of Assignments
reportedDiscussion and evaluation of any take-home assignments submitted as part of the technical assessment.
What to demonstrate
- Discussion and evaluation of any take-home assignments submitted as part of the technical assessment
- Depth in Java
How to prepare
- Answer aloud and timed: What strategies do you use for performance tuning in high-load scenarios?
- Answer aloud and timed: How do you ensure consistency and availability when working with Kafka or other message brokers?
PracHub editorial advice for the preparation topics above.
Prioritize clarity
When answering behavioral questions, use the STAR method (Situation, Task, Action, Result) to keep your stories focused and impactful.
Ask questions
At the end of every interview, have 2–3 thoughtful questions prepared about the team's challenges or technical roadmap; it shows genuine interest.
Be honest about gaps
If you don't know an answer, explain how you would go about finding it rather than guessing.
Prepare your environment
Since virtual interviews are standard, ensure you have a stable internet connection and a quiet space to minimize distractions.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
How do you manage memory and performance in a high-traffic Spring Boot application?
How do you manage memory and performance in a high-traffic Spring Boot application?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
Merge partitioned event streams into one ordered feed with bounded lateness
The read-model service consumes 64 log partitions carrying about 4,000 events per second in total. Each partition is ordered within itself, but partitions drift by up to 30 seconds, and the activity feed must present a tenant's events in occurred_at order. Produce the merge. State its complexity, the buffer it requires in events and in bytes, what happens when one partition is idle, and what you do with an event that arrives after you have already emitted its position. Payloads average 1 KB.
Approach
- Merge with a min-heap over the 64 partition heads keyed on (occurred_at, event_id): O(log P) per event and O(n log P) overall. The tie-break on event_id is what makes the output deterministic when two partitions carry the same millisecond, which matters because the feed is paginated and a non-deterministic order reorders pages under the reader.
- Emitting the heap head is only correct once every partition has produced everything up to that timestamp, so the emit condition is a watermark: the minimum across partitions of the highest occurred_at seen, less the allowed lateness. Events are held until the watermark passes them, which is what turns individually ordered streams into a jointly ordered one.
- Size the buffer from the lateness rather than guessing: 4,000 events per second times 30 seconds is 120,000 buffered events, and at 1 KB each about 120 MB of heap. That number is the real price of the ordering guarantee and belongs in front of whoever asked for it.
- Handle the idle partition explicitly, because it fails the feed rather than corrupting it: a partition with no traffic never advances its own maximum, so the watermark freezes and output stops entirely. Either every partition emits a periodic idle marker carrying the broker's current time, or the watermark falls back to wall clock for a partition silent beyond a threshold.
Follow-up
- The lateness budget is raised to five minutes. What is the new buffer, and what besides memory changes?
- The consumer restarts. Where does it resume from, and what does the feed look like for the first 30 seconds?
Can you explain how you would structure a database schema for a loan processing application?
Can you explain how you would structure a database schema for a loan processing application?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
Explain the difference between JPA and Hibernate and when to use each.
Explain the difference between JPA and Hibernate and when to use each.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Can you describe the lifecycle of a Spring Bean?
Can you describe the lifecycle of a Spring Bean?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What are the advantages of using Functional Programming features introduced in Java 8?
What are the advantages of using Functional Programming features introduced in Java 8?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you design an API Gateway for a microservices architecture?
How would you design an API Gateway for a microservices architecture?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
What strategies do you use for performance tuning in high-load scenarios?
What strategies do you use for performance tuning in high-load scenarios?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you ensure consistency and availability when working with Kafka or other message brokers?
How do you ensure consistency and availability when working with Kafka or other message brokers?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you approach securing sensitive data in transit and at rest?
How do you approach securing sensitive data in transit and at rest?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Edge instances grow 400 MB per hour until the nightly restart
Edge API instances start at 700 MB resident and grow about 400 MB/hour; a nightly rolling restart has hidden it for weeks. Growth continues unchanged when request rate halves overnight, p99 degrades in the last hours before an instance is recycled, and heap used immediately after a forced full GC rises monotonically. The service holds no product state. Name the discriminating measurement that separates the plausible causes, give the most likely cause, and give the fix and how you would verify it.
Approach
- Separate resident memory from live heap first, because they fail differently. Resident size can grow from fragmentation, native buffers or thread stacks while the heap is flat; heap used after a full GC rising monotonically is the measurement that says objects are reachable and not being released. You already have it, so this is retention, not fragmentation, and that closes off half the candidate list.
- Use the rate's independence from traffic as the discriminator. Growth that continues at half the request rate rules out per-request objects that are merely slow to collect and points at a structure that grows with distinct values observed rather than with call volume. Write the candidates that have that property: a metrics registry keyed on a high-cardinality label, an unevicted cache, an interner, a per-key lock map.
- Take two heap snapshots an hour apart and diff by retained size, reading the dominator tree, not by allocation count or instance count. Expect one root holding a map with millions of entries, then follow the reference chain to the code that inserts and never removes. Allocation profilers point at churn, which is the wrong signal here.
- The candidate that fits this service is an observability label carrying an identifier, such as a request path recorded before templating so that /v1/resources/48213 becomes its own metric series. That grows with distinct ids seen, is independent of rate, and explains the late p99 degradation, since GC cost rises with the size of the live set.
Follow-up
- Post-GC heap is now flat but resident size still creeps. What are you looking at, and does it matter?
- How would you have detected this before an OOM, given the nightly restart masked the trend?
Built from the rounds and topics ING candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the ING loop
- Write out the reported sequence: Initial Screening, Technical Deep Dives, Live Coding, Review of Assignments.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.
02Work Java
- Spend the session on Java, which ING candidates report being tested on.
- Write one worked example in Java and time yourself on it.
Deliverable: One timed worked example in Java.
03Work Spring Boot
- Spend the session on Spring Boot, which ING candidates report being tested on.
- Write one worked example in Spring Boot and time yourself on it.
Deliverable: One timed worked example in Spring Boot.
04Work OOP (Object-Oriented Programming)
- Spend the session on OOP (Object-Oriented Programming), which ING candidates report being tested on.
- Write one worked example in OOP (Object-Oriented Programming) and time yourself on it.
Deliverable: One timed worked example in OOP (Object-Oriented Programming).
05Answer out loud: Java and Backend Development
- Answer aloud, timed: Explain the difference between JPA and Hibernate and when to use each.
- Answer aloud, timed: How do you manage memory and performance in a high-traffic Spring Boot application?
Deliverable: Spoken answers to 2 reported Java and Backend Development question(s), under time.
06Answer out loud: System Design and Architecture
- Answer aloud, timed: How would you design an API Gateway for a microservices architecture?
- Answer aloud, timed: What strategies do you use for performance tuning in high-load scenarios?
Deliverable: Spoken answers to 2 reported System Design and Architecture question(s), under time.
07Answer out loud: Behavioral and Cultural Fit
- Answer aloud, timed: Describe a time you had a conflict with a team member; how did you resolve it?
- Answer aloud, timed: What, in your opinion, makes a high-performing software engineering team?
Deliverable: Spoken answers to 2 reported Behavioral and Cultural Fit question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
How do you handle transaction management in a distributed system?
How do you handle transaction management in a distributed system?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a time you had a conflict with a team member; how did you resolve it?
Describe a time you had a conflict with a team member; how did you resolve it?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What, in your opinion, makes a high-performing software engineering team?
What, in your opinion, makes a high-performing software engineering team?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle situations where you have to make trade-offs between speed of delivery and code quality?
How do you handle situations where you have to make trade-offs between speed of delivery and code quality?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell us about a project where you had to learn a new technology on the fly to meet a deadline.
Tell us about a project where you had to learn a new technology on the fly to meet a deadline.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you approach providing and receiving constructive code review feedback?
How do you approach providing and receiving constructive code review feedback?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
How do you handle transaction management in a distributed system?
- 02
Describe a time you had a conflict with a team member; how did you resolve it?
- 03
What, in your opinion, makes a high-performing software engineering team?
- 04
How do you handle situations where you have to make trade-offs between speed of delivery and code quality?
How long does the interview process typically take?
The process can vary, but generally spans 3 to 6 weeks from the initial screen to the final decision.
ING Software Engineer candidate reports ↗Are there coding challenges?
Yes, many teams utilize either live coding sessions or take-home assignments to assess your practical implementation skills.
ING Software Engineer candidate reports ↗What is the most common reason candidates fail the technical round?
Often, it is not a lack of knowledge, but an inability to explain the "why" behind their decisions or a failure to communicate during the problem-solving process.
ING Software Engineer candidate reports ↗Is the interview conducted in English?
In most international hubs and for global roles, the primary language of the interview is English, regardless of the local language.
ING Software Engineer candidate reports ↗What topics does ING test in interviews?
ING interviews most often cover SQL, Python, Problem Solving, Java, and Spring Boot. The exact emphasis depends on the specific role you apply for.
ING Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01ING Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Zebra Technologies Software Engineer Interview Guide
What Zebra Technologies asks Software Engineer candidates, from reported rounds and questions.
Vodafone Software Engineer Interview Guide
What Vodafone asks Software Engineer candidates, from reported rounds and questions.
Verisk Analytics Software Engineer Interview Guide
What Verisk Analytics asks Software Engineer candidates, from reported rounds and questions.
Upgrade Software Engineer Interview Guide
What Upgrade asks Software Engineer candidates, from reported rounds and questions.