Kapture CRM Software Engineer Interview: Rounds, Questions and Preparation

What the job involves

A Software Engineer at an Indian SaaS or B2B product company builds and maintains multi-tenant web applications that businesses use for sales, support, or operations. Day to day you write backend APIs, fix bugs, optimise database queries, and ship features with a small team. You also handle customer-specific configurations and work with support teams to resolve production issues quickly.

Role and SaaS fundamentals

1. 1

   What does a Software Engineer in a B2B SaaS company do differently from a developer in a services company?

   Mention building reusable product features for many customers, handling multi-tenancy, and owning long-term code quality instead of one-off client projects.

2. 2

   Explain what multi-tenancy means in a CRM product and how it affects database design.

   Cover shared database with tenant ID, row-level isolation, and the need to always filter queries by tenant to avoid data leaks.

3. 3

   How would you handle a feature request that only one large customer needs?

   Discuss configurable flags, tenant-specific settings, and balancing product roadmap with customer value without hardcoding for one client.

4. 4

   What is the difference between a product update and a hotfix in a live SaaS environment?

   Explain planned release cycles with testing versus emergency patches for production bugs, and mention rollback plans and communication.

Technical knowledge for the role

1. 5

   Write a SQL query to find the top 5 customers by number of support tickets raised in the last month.

   Use JOIN between customers and tickets, WHERE on date, GROUP BY customer, ORDER BY count DESC, and LIMIT 5.

2. 6

   How would you design a REST API to fetch a list of leads for a sales user?

   Cover GET endpoint, pagination, filtering by status or owner, authentication, and returning JSON with proper status codes.

3. 7

   Explain the difference between a stack and a queue. Give a use case in a CRM workflow.

   Define LIFO vs FIFO, then mention stack for undo operations or browser history, and queue for background job processing like email sending.

4. 8

   What happens when you type a URL in the browser and hit enter? Include where caching can happen.

   Walk through DNS, TCP, HTTP request, server processing, and response. Mention browser cache, CDN, and server-side cache.

Practical scenarios and problem solving

1. 9

   A customer reports that their dashboard is loading slowly. How do you debug this?

   Start with checking logs, database query times, API response times, and recent changes. Suggest adding indexes or caching if needed.

2. 10

   You deploy a new feature and it breaks the login for some users. What do you do first?

   Prioritise rollback or feature flag off, then check error logs, reproduce the issue, and communicate with the team and affected customers.

3. 11

   How would you find duplicate records in a leads table using SQL?

   Use GROUP BY on email or phone with HAVING COUNT(*) > 1, then join back to get full rows for review.

4. 12

   Your code works on your machine but fails on the staging server. What steps do you take?

   Compare environment variables, dependency versions, database state, and file paths. Check logs on staging and reproduce with the same config.

Behavioural and HR questions

1. 13

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

   Use STAR format: situation, task, action (how you learned), and result (working feature or deadline met).

2. 14

   How do you handle a situation where your teammate is not completing their part of the work?

   Show empathy, ask if they need help, escalate politely if needed, and focus on team goals rather than blame.

3. 15

   Why do you want to work in a SaaS product company instead of a services company?

   Talk about building products that scale, learning from many customer use cases, and long-term ownership of features.

4. 16

   Are you comfortable working in shifts or being on call for production support?

   Be honest. If yes, mention willingness to learn and that you understand SaaS products need uptime. If no, discuss flexibility.