Nucleus Software Backend Engineer Interview: Rounds, Questions and Preparation

What the job involves

Backend engineers in Indian SaaS and B2B product companies build and maintain the server-side logic, APIs, and databases that power multi-tenant business applications such as lending, HR, or ERP systems. Day to day, they write code in Java or Python, design REST APIs, optimise SQL queries, and work with cloud services to ensure reliability and scalability for enterprise clients.

Role and company knowledge

1. 1

   What does a backend engineer do in a SaaS company like Nucleus Software?

   Explain that you build server-side logic, APIs, and databases that serve multiple business clients. Mention multi-tenancy, data isolation, and scalability challenges specific to B2B SaaS.

2. 2

   Why do you want to work in the B2B SaaS sector rather than consumer tech?

   Show interest in solving complex business problems, working with enterprise clients, and building long-lasting products. Mention the learning opportunities in domains like lending or HR tech.

3. 3

   What do you know about Nucleus Software's products or domain?

   Research their flagship products like FinnOne for lending. Talk about how backend systems handle loan processing, risk assessment, and regulatory compliance.

4. 4

   How would you explain a REST API to a non-technical client?

   Use a simple analogy like a waiter taking your order to the kitchen and bringing back food. Emphasise that it is a standard way for software systems to talk to each other.

Technical fundamentals

1. 5

   What is the difference between SQL and NoSQL databases? When would you use each in a B2B product?

   SQL for structured, transactional data like financial records; NoSQL for flexible, high-volume data like logs or user activity. In B2B SaaS, SQL is common for core business data due to ACID compliance.

2. 6

   Explain how you would design a database schema for a multi-tenant application.

   Discuss options like shared database with tenant ID column, separate schemas, or separate databases. Mention trade-offs in cost, isolation, and maintenance.

3. 7

   What are ACID properties? Why are they important in a lending or banking application?

   Define Atomicity, Consistency, Isolation, Durability. Explain that financial transactions must be reliable and consistent to avoid errors like double debits or lost payments.

4. 8

   How does indexing improve database performance? What are the downsides?

   Indexes speed up read queries by creating a lookup structure. Downsides include extra storage and slower writes because indexes must be updated on insert/update.

Practical scenarios

1. 9

   You need to build an API endpoint that returns a list of loans for a customer. How would you approach it?

   Define the HTTP method (GET), URL structure (e.g., /customers/{id}/loans), authentication, pagination, and error handling. Mention returning JSON with appropriate status codes.

2. 10

   A client reports that a report is taking too long to load. How would you debug and fix it?

   Check database query performance, add indexes, optimise joins, consider caching, and review server logs. Suggest profiling tools and load testing.

3. 11

   How would you handle a situation where two users try to update the same record at the same time?

   Discuss optimistic locking (version numbers) or pessimistic locking (row locks). Explain how to prevent lost updates and ensure data integrity.

4. 12

   You are asked to integrate a third-party payment gateway. What steps would you take?

   Read API documentation, set up sandbox testing, handle authentication, implement retry logic, and ensure secure storage of keys. Mention error handling and logging.

Behavioural and HR

1. 13

   Tell me about a project where you faced a technical challenge and how you overcame it.

   Use the STAR method (Situation, Task, Action, Result). Focus on your problem-solving process, what you learned, and how you improved the outcome.

2. 14

   How do you handle feedback or criticism on your code during a review?

   Show that you are open to learning, ask questions to understand, and treat code reviews as a way to improve quality. Mention that you separate ego from the code.

3. 15

   Describe a time you had to work in a team to meet a deadline. What was your role?

   Highlight collaboration, communication, and reliability. Mention specific actions like breaking down tasks, helping teammates, and ensuring timely delivery.

4. 16

   Where do you see yourself in three years in a backend engineering role?

   Show ambition to grow technically, take ownership of modules, and contribute to architecture decisions. Align your goals with the company's growth in SaaS.