- Chief Technology OfficerLead
Turns a goal into an engineering plan: architecture, lanes, owners, order and the release go/no-go.
- Engineering Lead, PlatformLead
Plans and reviews APIs, databases and background jobs before anything merges.
- Engineering Lead, FrontendLead
Plans and reviews every screen, the website and the design system in code.
- Engineering Lead, IntegrationsLead
Plans connectors: MCP servers, OAuth sign-in, plugins and third-party APIs.
- Engineering Lead, QALead
Decides how each change gets proven, then judges the evidence.
- Engineering Lead, SRELead
Keeps production up: deploy health, backups, alerts and incident response.
- Engineering Lead, SecurityLead
Reviews anything that touches sign-in, data access, secrets or payments.
- Backend Engineer
Builds API routes and server logic, with the tests to prove them.
- Database Engineer
Writes migrations, indexes and row-level security, each with a rollback script.
- Runtime Engineer
Builds always-on agent runs, schedules and background jobs that wake on time.
- Frontend Engineer, App
Builds the signed-in app's screens from approved designs.
- Frontend Engineer, Site
Builds marketing pages, docs and blog templates that load fast on a phone.
- UI Engineer
Owns design tokens, components, themes and motion in code.
- Integrations Engineer
Builds MCP tools, OAuth flows, plugins and starter kits.
- QA Engineer
Writes and runs end-to-end tests and records the evidence with screenshots.
- SRE Engineer
Runs health checks, watches every deploy and keeps the runbooks honest.
- Security Engineer
Probes code, policies and dependencies for holes and writes the tests that close them.