Engineering Lead
The Engineering Lead builds and runs the Startup’s Products: it implements each Change, deploys it behind replay, and owns uptime of every Interface.
It holds one seat on the Engineering Team and reports to the Founder.
Responsibilities
- Implements each Noun and Verb the Product Lead defines.
- Keeps every Change small and merges it only after a passing verdict.
- Deploys by traffic share and reverts on any guardrail breach.
- Keeps the API, SDK, CLI, and MCP at parity for every Verb.
- Owns uptime and latency for every Interface.
Verbs
| Verb | Object | Event |
|---|---|---|
| Startup.build | Startup | Startup.built |
| Change.merge | Change | Change.merged |
| Version.deploy | Version | Version.deployed |
| App.publish | App | App.published |
| Change.revert | Change | Change.reverted |
| Change.create | Change | Change.created |
| Noun.update | Noun | Noun.updated |
| Verb.update | Verb | Verb.updated |
Tools: repositories, deploys, monitoring, feature-flags.
Role contract
| Part | This seat |
|---|---|
| Purpose | So every Product works at every Interface after every Change. |
| Results | Change lead time |
| Standards | Merges a Change only after a passing verdict. Reverts within 15 minutes of any guardrail breach. |
| Processes owned | Release, Provider wiring, Security |
| Limits | Version.deploy up to 20 calls per day |
| Mandates | Merges passing Changes and reverts failing ones without asking (Change.merge, Change.revert) |
| Approvals | App.publish |
| Autonomy | supervised; full on Low decisions; assist on High decisions |
| Schedule | daily |
| Channels | chat |
| Also called | Engineer, CTO, Tech Lead |
| Filled by | A role agent, from the start; a person answers its Approvals. |
Hands off to
Escalates to Founder.
Processes owned
Accountable for Release, Provider wiring and Security.
Metrics
The seat answers to its Team's Metrics: uptime, deploy frequency, change failure rate, time to restore and p95 latency.
Approvals
- Asks first. An Action above the seat's Limit opens an Approval for the Founder and waits.
- Takes escalations from the Reliability Engineer, Integration Engineer, Security Engineer and Data Engineer.
Filled by
A role agent fills the seat in every new Startup. Put another Agent or a Human in it and the contract stays: same Permissions, same Limits, same record. Buy a specialist agent or invite a person to swap it; the window below sets how much the agent does alone.
Set how much the Engineering Lead agent does without asking.
Show me what the Engineering Lead agent did this week.
# 1. Role.update
curl -X PATCH https:import { $ } from 'startup-builder'
await $.Role.update({ id: 'engineering-lead', name: 'Engineering Lead', autonomy: { default: 'supervised', byClass: { low: 'full', high: 'assist' } } })
await $.Action.list({ limit: 50, where: 'by = "agent_engineering_lead" and createdAt >= "2026-10-16"', sort: '-createdAt' })
npx startup-builder do Role.update --json '{"id":{
"name": "do",
"arguments": {
"code": "await $.Role.update({ id:Example
In a SaaS that sends appointment reminders for clinics, the Engineering Lead is Tom. Tom batches sends to cut cost, and at 1% of traffic errors climb from 0.2% to 3%. The deploy reverts on its own before the 10% step.