Wigzo Software Engineer Interview: Rounds, Questions and Preparation

What the job involves

As a Software Engineer at an Indian SaaS or B2B product company, you will build and maintain web-based features that help businesses manage customers, sales, and operations. Day to day, you will write backend APIs, integrate with frontend components, debug production issues, and work with product managers to ship improvements quickly. You will also write tests, review code, and participate in agile ceremonies like daily standups and sprint planning.

Role and Technical Knowledge

1. 1

   What happens when a user logs into a B2B SaaS dashboard and requests their sales data? Explain the flow from browser to database.

   Cover HTTP request, authentication token, API gateway, backend controller, database query, and JSON response. Mention caching if relevant.

2. 2

   How would you design a database schema for a multi-tenant SaaS app where each company has its own users and leads?

   Discuss a tenant ID column in every table, foreign keys, indexing on tenant ID, and isolation strategies like row-level security or separate schemas.

3. 3

   Explain the difference between SQL and NoSQL databases. Which would you choose for storing user activity logs in a B2B product and why?

   Compare schema flexibility, scaling, and consistency. For logs, NoSQL or time-series databases often work well due to high write volume and flexible format.

4. 4

   What is an API rate limit and why would a SaaS product like a marketing automation tool need it?

   Explain preventing abuse, ensuring fair usage across tenants, and protecting backend resources. Mention common algorithms like token bucket.

Practical Scenarios and Problem Solving

1. 5

   A customer reports that their campaign emails are not being sent from your SaaS platform. How would you debug this?

   Start by checking logs, email service provider status, queue backlog, and customer configuration. Suggest reproducing the issue and isolating the failure point.

2. 6

   You need to add a feature that lets users export a list of contacts as CSV. Walk through your implementation steps.

   Cover API endpoint design, database query with pagination, generating CSV on the server or client, handling large files, and testing edge cases like empty lists.

3. 7

   Your code passes locally but fails in production. What could be different and how do you fix it?

   Mention environment variables, database versions, file paths, permissions, and dependencies. Suggest using staging environments and logging to compare.

4. 8

   How would you handle a situation where a feature you built is causing slow page loads for a few large customers?

   Profile the slow queries or API calls, add indexes or caching, consider pagination, and communicate with the customer success team about timelines.

Behavioural and Teamwork

1. 9

   Tell me about a time you worked in a team to complete a college project. What was your role and how did you handle disagreements?

   Use STAR format. Highlight listening, compromising, and focusing on the project goal over personal preferences.

2. 10

   Describe a situation where you had to learn a new technology quickly for a project or hackathon.

   Show curiosity, resourcefulness, and a structured learning approach. Mention specific resources and how you applied the learning.

3. 11

   Give an example of a time you received critical feedback on your code or work. How did you respond?

   Emphasize not taking it personally, asking clarifying questions, and making concrete improvements. Show growth mindset.

4. 12

   How do you prioritize when you have multiple tasks like a bug fix, a new feature, and a code review request?

   Discuss impact, urgency, and communication with your manager. Mention using tools like Jira or Trello and asking for guidance when unsure.

HR and Company Fit

1. 13

   Why do you want to work at a fast-growing Indian SaaS company like Wigzo instead of a large MNC?

   Show interest in ownership, rapid learning, direct impact, and exposure to multiple technologies. Avoid saying you just need a job.

2. 14

   Where do you see yourself in three years as a software engineer in a B2B product company?

   Focus on deepening technical skills, taking ownership of modules, and contributing to architecture. Align with the company's growth path.

3. 15

   What do you know about our product and how do you think engineering contributes to it?

   Research the company's product, customers, and tech stack. Explain how engineers build features that solve customer problems and drive retention.

4. 16

   Are you comfortable working in a fast-paced environment with changing requirements? Give an example.

   Share a college or internship experience where you adapted to changes. Show flexibility, communication, and a focus on delivering value.