What everyone agreed on
Everyone is asking whether AI makes engineers faster. It is the wrong question, and it tells you nothing useful. I asked four senior engineers a narrower one: if writing code is no longer the slow part, what is? They agreed completely on one thing, coding stopped being the bottleneck, and then pointed in four different directions about what replaced it. That disagreement turned out to be the most interesting thing they said.
The numbers they reached for, unprompted, landed close: roughly 90% AI and 10% manual, almost zero manual for another, 70% coding down to 40%, and work that used to take a week now done in two days. The thing that used to eat the day, writing code by hand, mostly does not anymore.
Four people, four answers
I asked each the same follow-up: if coding is fast now, what is the slow step? Here is where they walked in different directions.
What this means for product
Two of the four bottlenecks sit inside the product function: Pabitra’s creating the task and Abhiraj’s alignment on what to build. That is not a mandate, two of four is not everything. But the direction is consistent with what the whole conversation kept gesturing at: as AI compresses the act of building, the expensive part drifts upstream, toward deciding what is worth building and exercising the judgment to know when the output is actually right.
A note on method
Four conversations are not a study. This is a set of careful anecdotes, recorded with permission, each engineer asked the same core questions in the same order. And since the irony is the point: I did not synthesize these transcripts by hand. I built a tool to do it, one that keeps every claim tied to the exact quote that supports it. That tool is Receipts, and it is its own case study.