Krutrim Cuts 20-25 More Jobs, Nearly Halving Remaining Staff

In late July 2026 Krutrim, Bhavish Aggarwal’s AI company, cut another 20 to 25 people. Inc42 and The Economic Times reported the round. The people affected this time were in product and engineering. Sales and go-to-market had already been cut in an earlier round. Remaining headcount before this July cut was estimated at 40 to 50. This row stores 22, inside the 20-to-25 range, and stays reported because Krutrim did not publish the list. A stored point inside a range is a marker, not a pretence that the outlets counted 22 names.

The scale only makes sense against the shrinkage that came before it. Coverage said Krutrim had been above 550 people in 2025 and had since narrowed from a full-stack AI ecosystem toward enterprise AI, cloud and maps. A cut of about 20 people is small beside a global programme of thousands and large beside a company that may have had about 50 people left. Both comparisons are allowed. What is not allowed is pasting 22 onto a national AI chart as “Indian AI shed 22 jobs,” or treating the fall from 550 as this event. The 2025 figure is background. The July figure is this row. We do not have one sourced total for every Krutrim exit since 2025, so we do not publish one. Adding the rounds into a single people field would hide which team was cut when.

The July hit, as reported, is product and engineering, not the sales round repeated under a new date. Maps and cloud were described as businesses the company was turning toward, not as proof those teams were shut. A strategy sentence and a headcount sentence are doing different work. This page will not convert “moving toward cloud and maps” into “those teams were eliminated.”

The city is Bengaluru. No campus table was published. The percentage on the row is our reading of 20 to 25 exits against an estimated 40 to 50 people remaining, not a percentage Krutrim printed. If the true remainder was already lower than 40, that percentage is too high. That is another reason the row stays reported. About half of a company that small is a severe round for the people in it and a rounding error on an industry total. The page has to hold both readings without inflating the industry one.

Ola’s ride-hailing and operations workforce is a different employer story. Aggarwal’s name connects them in the press. The headcount does not. What we will not infer: that Ola drivers or Ola operations staff moved with this 22, that 22 is confirmed, or that a further round can be folded back into July. A further round needs its own date. The citable line is: Inc42 and The Economic Times reported that Krutrim cut another 20 to 25 product and engineering roles in late July 2026, with about 40 to 50 people thought to remain.

Sequence is the only way the small integer stays honest. First, a company reported above 550 people in 2025, built as a full-stack AI effort. Then a narrowing toward enterprise AI, cloud and maps, with earlier cuts in sales and go-to-market. Then this late-July round, product and engineering, another 20 to 25 people, against an estimated 40 to 50 left. The stored 22 is the midpoint of that last range, not the sum of the whole decline. If someone subtracts 50 from 550 and calls the result this row, they have invented a 500-person event the July stories did not report. If someone ignores 550 and calls 22 a trivial round, they have missed that it may have been about half of whoever was left. Both errors come from collapsing the sequence. The city is Bengaluru. There is no second campus in the July copy, and there is no Krutrim total on this ledger that already includes the sales round plus this one.

What this number is

Another 20–25 people, stored as 22, in product and engineering, against an estimated 40–50 people left. It is not the drop from 550-plus in 2025, and it is not an Ola figure.

What is not confirmed

• Krutrim did not publish the list. The 40–50 remainder is an estimate in the coverage.
• The percentage on the row is that estimate, not a figure the company printed.

Revision: 22 Sep 2026: July product-and-engineering round kept separate from the earlier sales cuts and from the 2025 shrinkage.

Continue reading

• How to read a number. An announced cut, a reported estimate, and a fiscal-year net change are three different facts. The ledger labels each one.
• Bengaluru file, 2026. Rows that name Bengaluru this year, and the city shares this ledger will not invent.
• Silent exits and announced cuts. A hiring freeze, an appraisal cycle, and a named layoff round do different kinds of damage. The words in the source decide the row.