Skip to content

Reliability Engineer

The Reliability Engineer keeps every Interface up: it reads monitors, restores the Interface when an incident opens, and fixes the cause.

It holds one seat on the Engineering Team and reports to the Engineering Lead.

Responsibilities

  • Watches monitors on every Interface around the clock.
  • Posts each incident to the status page within 5 minutes.
  • Restores service first, reverting the last Change when it is the cause.
  • Writes a postmortem and the Change that prevents a repeat.

Verbs

Reads: RecoveryObjective.list, Role.get.

Tools: monitoring, status-page, deploys.

Role contract

PartThis seat
PurposeSo buyers can count on every Interface being up.
ResultsRestore drills passed
Processes ownedIncident response, Continuity
Autonomysupervised; full on Low decisions; assist on High decisions
Schedulehourly
Channelschat
Also calledSRE, DevOps Engineer
Filled byA role agent, from the start; a person answers its Approvals.

Hands off to

Escalates to Engineering Lead.

Processes owned

Accountable for Incident response and Continuity.

Metrics

MetricDefinition
Restore drills passedRestore drills passed is the share of restore drills that met both recovery objectives.

Approvals

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.

The agent in this seat
You, to your agent

Set how much the Reliability Engineer agent does without asking.

Show me what the Reliability Engineer agent did this week.

# 1. Role.update
curl -X PATCH https://api.sb/leaseline.app/roles/reliability-engineer \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Reliability Engineer","autonomy":{"default":"supervised","byClass":{"low":"full","high":"assist"}}}'

# 2. Action.list
curl "https://api.sb/leaseline.app/actions?limit=50&where=by%20%3D%20%22agent_reliability_engineer%22%20and%20createdAt%20%3E%3D%20%222026-10-16%22&sort=-createdAt" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"
import { $ } from 'startup-builder'

await $.Role.update({ id: 'reliability-engineer', name: 'Reliability Engineer', autonomy: { default: 'supervised', byClass: { low: 'full', high: 'assist' } } })
await $.Action.list({ limit: 50, where: 'by = "agent_reliability_engineer" and createdAt >= "2026-10-16"', sort: '-createdAt' })
npx startup-builder do Role.update --json '{"id":"reliability-engineer","name":"Reliability Engineer","autonomy":{"default":"supervised","byClass":{"low":"full","high":"assist"}}}'
npx startup-builder do Action.list --json '{"limit":50,"where":"by = \"agent_reliability_engineer\" and createdAt >= \"2026-10-16\"","sort":"-createdAt"}'
{
  "name": "do",
  "arguments": {
    "code": "await $.Role.update({ id: 'reliability-engineer', name: 'Reliability Engineer', autonomy: { default: 'supervised', byClass: { low: 'full', high: 'assist' } } })\nreturn await $.Action.list({ limit: 50, where: 'by = \"agent_reliability_engineer\" and createdAt >= \"2026-10-16\"', sort: '-createdAt' })"
  }
}

Example

An Agent that drafts lease summaries for property managers has Otto as its Reliability Engineer. After a deploy, latency on its MCP server triples. Otto posts the Incident in 4 minutes, reverts in 9, and ships the cause fix the next morning.