Chargebee Software Engineer Interview Experience

I recently interviewed with Chargebee for a Software Engineer position and wanted to share my experience. Even though I was rejected in the final round, I found the process well-structured and learned quite a few things from it.

Recruiter Screening

A recruiter reached out to me around two days before the interview. I applied for the role, but I couldn't attend the initial call. The recruiter called again the night before the interview, explained the entire interview process, and asked me to be present at the office by 8:30 AM.

One thing I appreciated was the transparency throughout the process. The recruiter clearly explained the rounds, the interviewers involved, and what to expect.

The entire interview process was completed on the same day.

The interview took place at a WeWork coworking space.

Round 1: Written Assessment

The first round was a written test focused on backend and system design fundamentals.

The questions were roughly around:

1. Database schema design

2. REST API design

3. Designing a concurrent application

I don't remember the exact problem statements, but the emphasis was on understanding design concepts and being able to explain your approach.

Result: Cleared

Round 2: Coding Round

This was the only round where working code was expected.

Questions:

1. Longest non-repeating character sequence

2. Flatten an array

3. Find the 3rd highest salary of an employee (SQL)

The discussion included time complexity and optimization considerations.

Result: Cleared

Round 3: Hiring Manager Round

This round focused heavily on my professional experience and projects.

We discussed:

• Project architecture

• Design decisions

• Technical trade-offs

• Challenges faced during implementation

Towards the end, I was asked to design a rate limiter. Due to time constraints, I provided a high-level design rather than going into implementation details.

One interesting aspect of this round was that the interviewer was not looking for production-ready code. The focus was on understanding the concept, reasoning through the solution, and communicating the approach clearly.

Result: Cleared

Round 4: Vice President Round

The final round started with a DSA question:

• Design a queue using arrays

Unfortunately, I wasn't able to solve it. The interview was scheduled on short notice and I hadn't revised some of the fundamental concepts recently.

The discussion then shifted towards my college projects. The VP opened my GitHub profile and asked questions about various repositories, including why some projects were not deployed and decisions made during development.

Again, the focus was more on understanding and explanation rather than writing complete code.

Result: Rejected

Feedback

The feedback I received was that the questions I asked during the interview were thoughtful and showed curiosity. However, they did not feel I was the right fit for the role at that time.

Key Takeaways

1. Fundamentals matter. Even seemingly simple data structures can become stumbling blocks if not revised regularly.

2. Communication plays a huge role. Except for the coding round, most of the interview weightage was on understanding concepts, explaining trade-offs, and reasoning through solutions rather than writing working code.

3. Be prepared to discuss everything on your resume and GitHub. Interviewers may go deep into projects you built years ago.

4. Candidate experience was excellent. Every round included actionable feedback, and the recruiter was transparent throughout the process.

Overall, despite the rejection, it was a positive interview experience and gave me a clear picture of areas I need to improve before future interviews.