cswork / libraryOpen practice workspace

Interview guides · Zenith Bank (Uk) Limited.

Zenith Bank (Uk) Limited. Software Engineer Interview Guide

Zenith Bank (Uk) Limited. Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Zenith Bank (Uk) Limited., you will play a pivotal role in bridging traditional corporate banking with modern financial technology. Operating within a highly regulated and competitive international financial landscape, the engineering team is responsible for building, optimizing, and securing the critical systems that process high-value transactions, manage risk, and support global operations. You will work on a mix of robust legacy systems and cutting-edge cloud-native architectures designed to maintain the bank's reputation for exceptional service and security. The impact of this role is extensive, directly influencing the reliability of banking services, the speed of cross-border financial transactions, and the seamless integration of internal tools. Because Zenith Bank (Uk) Limited.

This guide is scoped to a Software Engineer candidate at Zenith Bank (Uk) Limited..

Focus areas

  • Java
  • SOLID Principles
  • Object-Oriented Programming (OOP)

The Zenith Bank (Uk) Limited. interview process

Zenith Bank (Uk) Limited. candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Introductory Call

An initial call with HR or a hiring manager to discuss your background, career aspirations, and general fitness for the role.

What to demonstrate

  • An initial call with HR or a hiring manager to discuss your background, career aspirations, and general fitness for the role
  • Depth in Java

How to prepare

  • Answer aloud and timed: Explain the lifecycle of a Spring Bean within the ApplicationContext.
  • Answer aloud and timed: What is Inversion of Control (IoC), and how does it differ from Dependency Injection (DI)?

Technical Drill

A rigorous technical interview that evaluates your coding abilities, database knowledge, and system design experience.

What to demonstrate

  • A rigorous technical interview that evaluates your coding abilities, database knowledge, and system design experience
  • Depth in Java

How to prepare

  • Answer aloud and timed: How do you apply SOLID principles to ensure code maintainability in a large-scale banking application?
  • Answer aloud and timed: Explain the internal workings of a Java Virtual Machine (JVM) and how garbage collection impacts application latency.

Executive Management Review

A deep-dive conversation with the executive management team to assess your strategic thinking, leadership potential, and alignment with the bank's core values.

What to demonstrate

  • A deep-dive conversation with the executive management team to assess your strategic thinking, leadership potential, and alignment with the bank's core values
  • Depth in Java

How to prepare

  • Answer aloud and timed: What is the difference between a bean configured with singleton scope versus prototype scope in Spring?
  • Answer aloud and timed: How do you approach optimizing a slow-running SQL query that processes millions of transaction records?

Medical Screening

Candidates typically undergo a standard medical screening before a formal offer is extended.

What to demonstrate

  • Candidates typically undergo a standard medical screening before a formal offer is extended
  • Depth in Java

How to prepare

  • Answer aloud and timed: Describe a time when you had to resolve a database deadlock in a production environment.
  • Answer aloud and timed: What database indexing strategies do you use when designing schemas for high-write financial ledgers?

Where candidates lose points

Master the STAR Method

When describing your past projects and technical achievements, use the Situation, Task, Action, and Result framework. Focus heavily on the Action you took and the quantifiable Result of your engineering work.

Be Prepared to Diagram

During your system design and project walkthrough discussions, be ready to clearly map out your architectures. Practice drawing clean, logical diagrams that show the flow of data between clients, servers, caches, databases, and message queues.

Emphasize Security and Compliance

Remember that you are interviewing with a financial institution. Whenever you design a system or write code, explicitly mention how you handle data validation, encryption, access controls, and auditing. Showing a security-first mindset is highly valued.

Be Honest About Your Limits

If you encounter a technical question you do not know the answer to, do not try to guess or fake it. Instead, explain your thought process, how you would systematically go about researching the solution, and reference related concepts you do understand.

Questions & practice

Explain the internal workings of a Java Virtual Machine (JVM) and how garbage collection impacts application l

Medium · Java & Core Object-Oriented Programming

Explain the internal workings of a Java Virtual Machine (JVM) and how garbage collection impacts application latency.

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. 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?

What database indexing strategies do you use when designing schemas for high-write financial ledgers?

Medium · Database Design & Performance

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. 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?

Collapse a redelivered event batch into per-aggregate high-water marks

Easy · hashing · at-least-once · aggregation

You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.

Approach

  1. One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
  2. Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
  3. Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
  4. If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.

Follow-up

  • The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
  • How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?

How do you approach optimizing a slow-running SQL query that processes millions of transaction records?

Medium · Database Design & Performance

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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

Hard · denormalisation · online migration · backfill

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

  1. 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.
  2. 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.
  3. 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.
  4. 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 lifecycle of a Spring Bean within the ApplicationContext.

Medium · Java & Core Object-Oriented Programming

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 is Inversion of Control (IoC), and how does it differ from Dependency Injection (DI)?

Medium · Java & Core Object-Oriented Programming

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 do you apply SOLID principles to ensure code maintainability in a large-scale banking application?

Medium · Java & Core Object-Oriented Programming

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 is the difference between a bean configured with singleton scope versus prototype scope in Spring?

Medium · Java & Core Object-Oriented Programming

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Explain the trade-offs between ACID compliance and eventual consistency in distributed systems.

Medium · Database Design & Performance

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 would you design a highly available, fault-tolerant microservice architecture for a transaction processing

Medium · Cloud Architecture & System Design

How would you design a highly available, fault-tolerant microservice architecture for a transaction processing system?

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 cloud-native security measures do you implement to protect sensitive financial data in transit and at res

Medium · Cloud Architecture & System Design

What cloud-native security measures do you implement to protect sensitive financial data in transit and at rest?

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. 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?

How do you handle distributed transactions across multiple microservices without compromising data integrity?

Medium · Cloud Architecture & System Design

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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?

One customer endpoint stalls deliveries to every other destination

Medium · bulkhead · timeouts · saturation

The egress service delivers about 1.5k webhooks/second across 40,000 destinations, with a per-destination concurrency cap of 4 and a 10-second connect-plus-read timeout. Throughput falls to 300/second, queue depth climbs, and p99 delivery latency for unaffected destinations goes from 200 ms to minutes, while the error rate barely moves. One tenant holds 900 destination rows whose URLs share a hostname that now answers in 9.5 seconds. Explain the mechanism with the arithmetic, then give the containment in the order you would apply it.

Approach

  1. Look at saturation before errors. A flat error rate with collapsing throughput says nothing is failing, things are waiting, so the first signal to pull is in-flight request count or pool wait time rather than the error counter. This is the distinction that decides the whole investigation.
  2. Group in-flight work by resolved host, not by destination id. The cap is keyed per destination row, so 900 rows sharing one hostname buy 3,600 concurrent slots against a single host, each held for 9.5 seconds. The bulkhead was never a bulkhead for that host, and grouping by the wrong dimension is why the dashboard looked healthy.
  3. Do the arithmetic in both directions. Required concurrency is arrival rate times latency, so 1.5k/second at 200 ms needs about 300 in flight, which is entirely consumed by 3,600 slow slots; conversely whatever concurrency is left sustains rate equals concurrency divided by 9.5 seconds, which is the 300/second you are seeing. Matching both numbers is what promotes this from a plausible story to the mechanism.
  4. Explain why the circuit breaker never helped. It opens on consecutive failures, and a 9.5-second response inside a 10-second timeout is a success. Slow is not failing, so an error-rate breaker cannot see this; you need a slow-call ratio, a deadline propagated from the caller's remaining budget, or a concurrency limiter.

Follow-up

  • The host recovers to 80 ms. How long does the queue take to drain, and what does the drain do to the recovered host?
  • Where should the 10-second timeout number actually come from?

Suggested practice checklist

Built from the rounds and topics Zenith Bank (Uk) Limited. candidates report.

Day 1 — Map the Zenith Bank (Uk) Limited. loop

  • Write out the reported sequence: Introductory Call, Technical Drill, Executive Management Review, Medical Screening.
  • 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.

Day 2 — Work Java

  • Spend the session on Java, which Zenith Bank (Uk) Limited. candidates report being tested on.
  • Write one worked example in Java and time yourself on it.

Deliverable: One timed worked example in Java.

Day 3 — Work SOLID Principles

  • Spend the session on SOLID Principles, which Zenith Bank (Uk) Limited. candidates report being tested on.
  • Write one worked example in SOLID Principles and time yourself on it.

Deliverable: One timed worked example in SOLID Principles.

Day 4 — Work Object-Oriented Programming (OOP)

  • Spend the session on Object-Oriented Programming (OOP), which Zenith Bank (Uk) Limited. candidates report being tested on.
  • Write one worked example in Object-Oriented Programming (OOP) and time yourself on it.

Deliverable: One timed worked example in Object-Oriented Programming (OOP).

Day 5 — Answer out loud: Java & Core Object-Oriented Programming

  • Answer aloud, timed: Explain the lifecycle of a Spring Bean within the ApplicationContext.
  • Answer aloud, timed: What is Inversion of Control (IoC), and how does it differ from Dependency Injection (DI)?

Deliverable: Spoken answers to 2 reported Java & Core Object-Oriented Programming question(s), under time.

Day 6 — Answer out loud: Database Design & Performance

  • Answer aloud, timed: How do you approach optimizing a slow-running SQL query that processes millions of transaction records?
  • Answer aloud, timed: Describe a time when you had to resolve a database deadlock in a production environment.

Deliverable: Spoken answers to 2 reported Database Design & Performance question(s), under time.

Day 7 — Answer out loud: Cloud Architecture & System Design

  • Answer aloud, timed: How would you design a highly available, fault-tolerant microservice architecture for a transaction processing system?
  • Answer aloud, timed: What cloud-native security measures do you implement to protect sensitive financial data in transit and at rest?

Deliverable: Spoken answers to 2 reported Cloud Architecture & System Design question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe a time when you had to resolve a database deadlock in a production environment.

Medium · Database Design & Performance

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 your experience with containerization and orchestration using Docker and Kubernetes.

Medium · Cloud Architecture & System Design

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 me about yourself and walk me through the architecture of a complex software project you recently deliver

Medium · Behavioral & Project Deep-Dives

Tell me about yourself and walk me through the architecture of a complex software project you recently delivered.

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 situation where you had a technical disagreement with a senior teammate or architect. How did you r

Medium · Behavioral & Project Deep-Dives

Describe a situation where you had a technical disagreement with a senior teammate or architect. How did you resolve it?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 balance the pressure of tight business deadlines with the need to write clean, well-tested code?

Medium · Behavioral & Project Deep-Dives

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?

Can you demonstrate a hosted personal or professional project and explain the technical trade-offs you made du

Medium · Behavioral & Project Deep-Dives

Can you demonstrate a hosted personal or professional project and explain the technical trade-offs you made during its development?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?