Zopper Backend Engineer Interview: Rounds, Questions and Preparation

What the job involves

As a backend engineer in neobanking, lending, or insurtech, you will build and maintain the server-side systems that power loan origination, EMI schedules, payment processing, and risk checks. Day to day you will write APIs, integrate with banking and credit partners, ensure transaction accuracy and data security, and debug production issues in a regulated, high-volume environment.

Role and sector knowledge

1. 1

   Walk me through what happens technically from the moment a user applies for a loan on a neobanking app until the money is disbursed.

   Cover API calls for KYC, credit bureau check, underwriting rules, loan account creation, payment gateway or bank transfer, and webhook confirmation. Mention idempotency and status tracking.

2. 2

   What is the difference between a payment gateway, a payment aggregator, and a neobanking platform in terms of backend responsibilities?

   Explain that gateways handle card/UPI processing, aggregators pool merchants, and neobanking platforms orchestrate accounts and lending. Focus on where your code sits and what it must not do.

3. 3

   How would you design a database schema to store loan accounts, EMIs, and repayment transactions?

   Show tables for customers, loans, EMI schedules, and payments with foreign keys. Mention indexes on loan_id and due_date, and a ledger-style table for double-entry accuracy.

4. 4

   Why is idempotency important in lending and payments, and how would you implement it in an API?

   Explain that retries can duplicate a disbursement or repayment. Use an idempotency key stored in a unique table, return the same response for repeated requests, and combine with DB transactions.

Technical concepts for backend

1. 5

   Explain ACID properties with an example from a loan repayment system.

   Use a transfer of EMI from wallet to loan account. Show atomicity (both debit and credit happen), consistency (balance rules), isolation (concurrent repayments), and durability (committed data survives crash).

2. 6

   How would you prevent double spending or race conditions when two repayment requests hit the same loan account at the same time?

   Mention database row-level locks, SELECT FOR UPDATE, optimistic locking with version columns, or serializable isolation. Also mention idempotency keys and queue-based serialization.

3. 7

   What is the difference between authentication and authorization, and how would you secure a customer-facing loan API?

   Authentication verifies identity (JWT or OAuth token), authorization checks permissions (can this user view this loan). Add HTTPS, rate limiting, input validation, and never log sensitive PII.

4. 8

   How do you handle a slow third-party credit bureau API in your backend without blocking the user request?

   Use async processing with a message queue, return a pending status, and update via webhook or polling. Mention timeouts, retries with backoff, circuit breakers, and caching where allowed.

Practical scenarios and problem solving

1. 9

   A customer reports that their EMI was debited twice but the loan balance shows only one payment. How do you debug and fix this?

   Start with logs and transaction IDs, check idempotency keys, verify DB transaction boundaries, and reconcile with the payment gateway. Then fix the data and add a reconciliation job.

2. 10

   You need to add a new repayment option (UPI autopay) to an existing loan API. How do you approach the change without breaking current clients?

   Design a new API version or additive fields, use feature flags, write tests for old and new flows, and roll out gradually with monitoring. Mention backward compatibility and deprecation policy.

3. 11

   How would you ensure that a daily interest accrual job runs correctly even if the server restarts midway?

   Make the job idempotent by tracking last processed date per loan, use a database transaction per batch, and store job state. Mention retries and alerting on failures.

4. 12

   Your API response time suddenly increases from 200ms to 2 seconds in production. What steps do you take?

   Check database slow queries and missing indexes, review recent deployments, inspect external API latency, and look at CPU/memory. Use APM tools and add caching or query optimization.

Behavioural and HR questions

1. 13

   Why do you want to work in neobanking, lending, or insurtech rather than a general product company?

   Show interest in financial inclusion, regulated systems, and real impact on credit access. Mention willingness to learn compliance and accuracy, not just code.

2. 14

   Tell me about a time you had to learn a new technology or domain quickly for a project or hackathon.

   Use STAR format. Highlight how you broke down the problem, used documentation, asked for help, and delivered something working under a deadline.

3. 15

   Describe a situation where you made a mistake in code that caused an issue. How did you handle it?

   Be honest, own the mistake, explain how you fixed it, and what process you added (tests, code review, monitoring) to prevent recurrence.

4. 16

   How would you handle working under pressure when a production issue affects loan disbursements for many customers?

   Show calm prioritization: assess impact, communicate with stakeholders, roll back or hotfix, and write a post-mortem. Emphasize teamwork and clear updates.