01
Product surfaces
Own the React UI end to end. Hierarchy, spacing, copy, motion, density. Make admin and operator screens feel like one product.
Careers / Engineering
Build the control plane for useful agents.
This is the first developer role on the z0.ai codebase. We need someone who can own the full stack end to end: product surfaces people enjoy using, services that stay correct, and the taste to make both feel like one product.
Stage
Pre-seed
Location
NYC
Level
Senior
Comp
$140–180K + 1.0–2.5%
Codebase
Go 1.26PostgreSQLNext.js 15React 19VitePulumi
Platform surface
Infrastructure with a product face.
z0.ai sits between people asking for work in Slack, agents doing the work, and operators who need scope, cost, approval, and evidence to stay clear. The product has to feel as good as the plumbing behind it.
02
Onboarding and setup
Design the first-run experience for new tenants: Slack install, workspace scope, agent configuration, budget admission, approval routing.
03
Approvals, budgets, audit
Turn policy checks, human review, spend limits, and evidence records into clear flows the people running agents actually trust.
04
Control-plane services
Refine the Go services behind the product: API, scheduler, projectors, workers, and the migration paths that keep agent work recoverable.
05
PostgreSQL event flows
Evolve the event store, outbox claiming, read models, usage ledger, and tenant-scoped records without losing auditability.
06
Runtime and integrations
Improve Codex and Claude Code adapters, Slack routes, Composio-backed tools, sandbox snapshots, and retry behavior.
Open role
Founding Full Stack Engineer
Responsibilities
- Design and ship React product surfaces: onboarding, workspaces, agent setup, approvals, usage, and failure inspection.
- Make UI and UX decisions without waiting on a designer. Own hierarchy, copy, spacing, motion, and the details that make screens feel intentional.
- Ship production changes across the stack: React, Go services, database migrations, and OpenAPI contracts.
- Design event-driven backend workflows where retries, interruptions, approvals, and settlements are explicit records.
- Turn operational questions into clear, inspectable product flows for admins, approvers, auditors, and support staff.
- Write tests at the level of risk: UI coverage for customer flows, integration coverage for orchestration paths, and unit coverage for policy and accounting.
You might be a fit if
- You have taste. It shows up in the interfaces you build, the copy you write, and the code you delete.
- You make confident UI and UX decisions on your own. You can ship a screen that feels right without a figma handoff.
- You move between React details and backend invariants without treating either side as someone else's problem.
- You have shipped Go or TypeScript systems that keep working when jobs retry, processes crash, or webhooks arrive twice.
- You are comfortable with PostgreSQL schema design, transactions, idempotency, and read-model projection.
- You prefer direct, testable code over fashionable abstractions.
Bring judgment,
not ceremony.
Send a short note with the systems you have shipped, the failures you have debugged, and the parts of this codebase you would want to own first.
join@z0.ai · replies within a few days