Zoho CRM 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 applications used by businesses. Day to day, they write code, design data models, optimise queries, debug production issues, and collaborate with frontend and product teams to ship features. The focus is on reliability, scalability, and clean, maintainable code that serves many customers on shared infrastructure.

Role and Technical Knowledge

1. 1

   What is multi-tenancy in a SaaS product, and how would you design a database to support it?

   Explain the concept of serving multiple customers from one application instance. Discuss shared schema with tenant ID, separate schemas, or separate databases, and trade-offs in cost, isolation, and maintenance.

2. 2

   How would you design a REST API for a CRM module that manages customer leads?

   Cover resource naming, HTTP methods, status codes, pagination, filtering, and authentication. Mention versioning and idempotency for safe retries.

3. 3

   Explain the difference between SQL and NoSQL databases. When would you choose one over the other for a B2B product?

   Compare schema flexibility, consistency, scaling, and query patterns. Give examples like transactional data in SQL and high-volume logs or flexible documents in NoSQL.

4. 4

   What are database indexes, and how do they affect read and write performance?

   Describe how indexes speed up reads but slow down writes and take storage. Mention composite indexes, covering indexes, and avoiding over-indexing.

Practical Scenarios

1. 5

   A customer reports that a report in your SaaS application is timing out. How would you debug and fix it?

   Start by reproducing the issue, checking logs and query execution plans. Suggest optimising queries, adding indexes, caching, or paginating results. Mention communicating with the customer.

2. 6

   You need to add a new field to a table that already has millions of rows in production. How would you do it safely?

   Discuss adding the column as nullable or with a default, backfilling in batches, and avoiding long locks. Mention testing on a staging environment and monitoring.

3. 7

   How would you handle authentication and authorisation for an API used by multiple business customers?

   Cover token-based auth like JWT or OAuth, role-based access control, and tenant isolation. Mention secure storage of secrets and token expiry.

4. 8

   Your application needs to send email notifications to users. How would you design this so it does not slow down the main request?

   Suggest using a message queue or background job to process emails asynchronously. Mention retries, failure handling, and not blocking the user response.

Behavioural and Situational

1. 9

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

   Use the STAR method. Focus on how you approached learning, resources used, and the outcome. Show curiosity and ability to apply new knowledge.

2. 10

   Describe a situation where you disagreed with a teammate on a technical approach. How did you handle it?

   Show that you listen, present data or reasoning, and aim for the best solution. Avoid sounding stubborn or passive. Highlight teamwork and respect.

3. 11

   Give an example of a bug you fixed that had a significant impact. What was your process?

   Explain how you identified the root cause, the fix, and how you prevented recurrence. Mention testing and communication with stakeholders.

4. 12

   How do you prioritise tasks when you have multiple deadlines or bugs to fix?

   Talk about assessing impact and urgency, communicating with your manager, and using tools like issue trackers. Show that you stay calm and organised.

HR and Company Fit

1. 13

   Why do you want to work as a backend engineer in a SaaS product company rather than a services company?

   Show understanding of product work: building for many customers, iterating on features, and long-term ownership. Mention interest in scalable systems and continuous learning.

2. 14

   What do you know about our company and the products we build?

   Research the company's main products, target customers, and tech stack if public. Connect your skills and interests to their work without claiming inside knowledge.

3. 15

   Where do you see yourself in three years as a backend engineer?

   Show ambition to grow technically, take ownership of modules, and contribute to design. Avoid saying you want to move to management immediately unless that is genuine.

4. 16

   How do you keep your technical skills up to date?

   Mention reading blogs, documentation, online courses, side projects, or open source. Show that you enjoy learning and can do it independently.