OneCard Backend Engineer Interview: Rounds, Questions and Preparation

What the job involves

Backend engineers in neobanking, lending, and insurtech build and maintain the core services that handle user accounts, credit underwriting, payment processing, and regulatory reporting. Day to day, they write APIs, design database schemas, integrate with third-party financial systems, and ensure low-latency, high-availability operations. They also work on fraud detection, loan management, and compliance features that are critical in Indian fintech.

Role and Technical Knowledge

1. 1

   How would you design a database schema for a credit card management system that handles transactions, repayments, and rewards points?

   A strong answer covers normalization, indexing, ACID transactions, and scalability. Mention tables for users, cards, transactions, repayments, and rewards, with appropriate relationships.

2. 2

   Explain how you would ensure idempotency in a payment processing API to prevent duplicate transactions.

   Discuss using unique idempotency keys, storing request IDs, and returning the same response for repeated requests. Highlight the importance of idempotency in financial transactions.

3. 3

   What are the key considerations for building a real-time fraud detection system in a neobanking app?

   Cover data streaming, rule engines, machine learning models, low-latency processing, and feedback loops. Mention false positives and regulatory reporting.

4. 4

   How would you handle data consistency across microservices in a lending platform?

   Discuss patterns like Saga, event sourcing, and two-phase commit. Emphasize eventual consistency and compensating transactions for failures.

Practical Scenarios

1. 5

   You notice a sudden spike in failed loan repayment transactions. How would you debug and resolve this?

   Outline steps: check logs, monitor system metrics, identify patterns (e.g., specific bank or time), test payment gateway integration, and roll back recent changes if needed.

2. 6

   A regulatory audit requires you to produce a report of all transactions above a certain amount for the last quarter. How would you design this?

   Mention efficient querying with proper indexing, data archiving strategies, and ensuring data integrity. Discuss batch processing and compliance with RBI guidelines.

3. 7

   How would you optimize a slow API endpoint that fetches user account details and recent transactions?

   Suggest caching, database indexing, pagination, query optimization, and possibly denormalization. Mention profiling to identify bottlenecks.

4. 8

   You need to integrate a new UPI payment method into your existing system. What steps would you take?

   Cover API integration, testing in sandbox, security checks, error handling, and gradual rollout. Mention NPCI guidelines and reconciliation.

Behavioural and HR

1. 9

   Why do you want to work in the fintech sector, specifically in neobanking or lending?

   Show passion for financial inclusion, technology-driven solutions, and awareness of Indian fintech landscape. Relate to personal experiences or projects.

2. 10

   Describe a time when you had to learn a new technology quickly for a project. How did you approach it?

   Use STAR method: situation, task, action, result. Highlight self-learning, resourcefulness, and application of the new skill.

3. 11

   Tell me about a time you worked in a team to solve a complex problem. What was your role?

   Focus on collaboration, communication, and your specific contribution. Mention challenges and how you overcame them.

4. 12

   How do you handle tight deadlines and pressure, especially in a fast-paced startup environment?

   Discuss prioritization, time management, and staying calm. Give an example of meeting a deadline under pressure.

System Design and Architecture

1. 13

   Design a scalable notification system for a neobanking app that sends transaction alerts via SMS, email, and push notifications.

   Cover message queues (e.g., Kafka), worker services, retry mechanisms, and user preferences. Discuss scalability and fault tolerance.

2. 14

   How would you architect a loan origination system that integrates with multiple credit bureaus and bank APIs?

   Mention API gateways, service orchestration, data transformation, security, and asynchronous processing. Highlight reliability and compliance.

3. 15

   What factors would you consider when choosing between SQL and NoSQL databases for storing user transaction data?

   Compare ACID compliance, scalability, query patterns, and consistency requirements. For financial data, SQL often preferred for transactions, NoSQL for logs or analytics.