If your agents are doing the building, your job as technical founder just got clarified — and harder. Understanding what leverage actually means in that world starts here.
Greg Brockman's essay on figuring out the CTO role at Stripe is one of the more honest documents about technical leadership you'll find. He argues that the role has no fixed definition — you have to author it, continuously, based on what the organization actually needs. The real work is raising the floor: setting standards, choosing tools, shaping culture so that good decisions proliferate without you in the room. Individual technical brilliance is a trap if it becomes load-bearing.
When agents handle implementation, the Brockman insight sharpens considerably. You are no longer the best coder in the building — an agent probably is — so the old temptation to heroic contribution evaporates by necessity. What remains is exactly what he identified: judgment about what gets built, standards for how agents are prompted and constrained, and cultural norms around when humans override. The CTO of an AI-native studio is, structurally, already the role Brockman was arguing Stripe needed. The question is whether you're filling it deliberately.
- Define your technical leadership role explicitly or it will define you by default
- raising the floor through standards and tooling matters more than any individual output
- in an agent-first shop, the human judgment layer is the architecture — design it like one.
