NoBroker Backend Engineer Interview: Rounds, Questions and Preparation

What the job involves

Backend engineers at Indian unicorns and high-growth startups build and maintain the server-side systems that power consumer apps, marketplaces, and internal tools. Day to day, they write APIs, design database schemas, debug production issues, and optimise for scale and latency under heavy traffic. They work closely with product, frontend, and DevOps teams to ship features quickly in fast-changing environments.

Role and Technical Knowledge

1. 1

   What happens behind the scenes when a user searches for a property on a platform like NoBroker?

   A strong answer covers request flow from client to load balancer, API server, database query, caching, and response formatting, showing awareness of latency and scale.

2. 2

   How would you design a REST API for posting a new property listing?

   Mention HTTP methods, status codes, request/response JSON structure, validation, authentication, and idempotency for retries.

3. 3

   Explain the difference between SQL and NoSQL databases. Which would you choose for a user profile service and why?

   Discuss schema flexibility, consistency, scaling, and access patterns. For user profiles, SQL is often fine due to relational data and transactions.

4. 4

   What is the role of an index in a database? How does it speed up queries?

   Explain that indexes create a data structure (like B-tree) for faster lookups, but add overhead on writes and storage. Mention composite indexes and query planning.

Practical Scenarios

1. 5

   Your API is suddenly slow during peak hours. How would you debug and fix it?

   Suggest checking logs, monitoring tools, database slow queries, cache hit ratio, and scaling horizontally. Mention profiling and load testing.

2. 6

   You need to add a new feature that sends notifications to users when a property matches their saved search. How would you approach this?

   Talk about background jobs, message queues (like RabbitMQ or Kafka), and ensuring notifications are sent asynchronously without blocking the main request.

3. 7

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

   Discuss transactions, row-level locking, optimistic vs pessimistic locking, and idempotency to prevent double booking.

4. 8

   You have to deploy a new version of your backend service with zero downtime. What steps would you take?

   Mention blue-green deployment, canary releases, database migrations that are backward compatible, and health checks.

Behavioural and HR

1. 9

   Why do you want to work at a high-growth startup like NoBroker instead of a large MNC?

   Show enthusiasm for ownership, fast-paced learning, and direct impact. Avoid saying you just need a job.

2. 10

   Tell me about a time you faced a technical challenge in a project. How did you overcome it?

   Use the STAR method: describe the situation, task, action, and result. Highlight debugging, research, and teamwork.

3. 11

   How do you prioritise tasks when you have multiple deadlines?

   Mention assessing impact and urgency, communicating with stakeholders, and using tools like Jira or Trello. Show flexibility.

4. 12

   Where do you see yourself in three years?

   Align your growth with the company's needs, such as becoming a strong backend engineer or tech lead, and express a desire to learn and contribute.

Core Computer Science Fundamentals

1. 13

   What is the difference between a process and a thread? How does multithreading help in backend services?

   Explain that processes have separate memory, threads share memory. Multithreading improves concurrency but requires synchronisation to avoid race conditions.

2. 14

   Explain TCP vs UDP. Which one would you use for a real-time chat feature and why?

   TCP is reliable, ordered; UDP is faster but unreliable. For chat, TCP is common, but UDP can be used with additional reliability layers for low latency.

3. 15

   What is a deadlock? How can you prevent it in a backend system?

   Describe four conditions for deadlock and prevention techniques like resource ordering, timeouts, and deadlock detection.

4. 16

   How does a hash map work? What is its time complexity for get and put operations?

   Explain hashing, collision resolution (chaining or open addressing), and average O(1) time, worst-case O(n). Mention load factor and resizing.