Hikes are extremely poor. Your responsibilities and title can grow significantly while your compensation barely keeps up.
There is little to no meaningful mentorship. Do not join expecting someone to actively mentor you or build your technical career. Most of your growth will depend on what you learn yourself.
There seems to be a lack of clear product vision. It often feels like the company itself does not know what it wants the product to become.
The company calls itself “AI-first,” but from my experience, it feels more like “AI-third.” There is a lot of talk about AI, but much less clarity about how AI is actually going to transform the product.
Chargebee once felt like a leader in subscription billing, but competitors such as Stripe have expanded aggressively. From my perspective, Chargebee increasingly feels like it is following the market instead of leading it.
Engineering quality can be very inconsistent. Strong technical work is not always recognized, and the overall quality bar varies considerably between teams.
Be very careful about putting significant value on stock options. Understand the actual terms, strike price, valuation, liquidity possibilities, and dilution rather than assuming they will eventually be worth a lot.
There is very little incentive to stay for the long term. You might receive a competitive package when joining, but internal hikes may leave your compensation significantly behind the market over time.
If you are joining, I would personally treat it as a place to gain experience for 1–2 years rather than assuming it will be a great place to build a long-term career.
The biggest contradiction is simple: they can value you well when hiring you, but that does not necessarily mean they will continue valuing you financially once you are already there.
Invest in the people who are already delivering for the company, not just in hiring new people at competitive market salaries.
Create a real mentorship culture. Employees should not have to figure out their entire career progression and technical development on their own.
Make compensation growth meaningful. If someone’s responsibilities, performance, and title increase substantially, their compensation should reflect that. Competitive joining packages combined with poor internal hikes give employees very little reason to stay.
Have a clearer product vision. Instead of constantly reacting to competitors and industry trends, communicate what Chargebee wants to lead in and why.
If the company wants to call itself “AI-first,” make it meaningful. AI should be reflected in the product strategy, engineering culture, internal capabilities, and customer value—not primarily in messaging.
Raise and maintain the engineering quality bar. Recognize strong technical contributions, invest in good engineering practices, and reward people who improve systems for the long term rather than only those who handle the most visible short-term work.
Most importantly, give your best employees reasons to stay. Hiring good people is expensive, but losing experienced employees because their compensation, mentorship, recognition, and opportunities have not kept pace is even more costly.
System design technical interview Technical interview 2 Cultural fitment round with hiring manager System design technical interview Technical interview 2 Cultural fitment round with hiring manager System design technical interview Technical interv
I applied via LinkedIn job section and got the OA link. The OA had 2 coding questions ranging in LeetCode hard level. 6 SQL questions and 5 aptitude questions. Got through that. Then came the first online technical interview. The interviewer had 2 ye
A good technical interview touches on every aspect of coding, automation, framework, different tools, testing concepts, cloud, different test approaches, concepts of OOPs, collection framework, performance testing, Gherkin, BDD, Cucumber, TestNG, and
System design technical interview Technical interview 2 Cultural fitment round with hiring manager System design technical interview Technical interview 2 Cultural fitment round with hiring manager System design technical interview Technical interv
I applied via LinkedIn job section and got the OA link. The OA had 2 coding questions ranging in LeetCode hard level. 6 SQL questions and 5 aptitude questions. Got through that. Then came the first online technical interview. The interviewer had 2 ye
A good technical interview touches on every aspect of coding, automation, framework, different tools, testing concepts, cloud, different test approaches, concepts of OOPs, collection framework, performance testing, Gherkin, BDD, Cucumber, TestNG, and