A podcast about what happens to business when software no longer scales with engineering headcount.
Supported by
AI agents are breaking that relationship. Software can now move from requirement to production without a human reading every line. What happens next?
An operating model where autonomous agents do most of the building, testing, reviewing, and deployment, while humans design the system, define the constraints, and stay accountable for the outcomes. The engineers don't disappear; the system moves them from writing the code to governing it.
When production stops scaling with headcount, companies rebuild their teams, their pricing, their procurement, and their idea of technical leadership. This show documents that transition.
Questions we investigate with builders, operators, and leaders
A venture designer who explores what happens to companies when software output stops tracking engineering headcount.
A senior engineer who builds autonomous delivery systems and tests where they survive contact with production.
Both work at Camplight, where they build and test agentic software-delivery systems on real projects. Dany argues from the business side, Vitaliy from the machine room.
Guests join a running argument: what does a company become when its software output no longer depends on its headcount?
For guests · every two weeks
Episode one is recorded and the first five clips are cut. Watch them:
Five clips from episode one · full episode coming soon
We'd love to talk. · dany@camplight.net
Book a recording →After the Last Engineer · Supported by