Founding Engineer

The work

BotBot runs on structured company context in plain files and Git. That context steers agent work, and typed checks plus human review make the work inspectable before it is trusted.

The role

We're hiring a founding engineer to build the systems that make this workflow reliable. You will work close to the architecture and help decide what needs to exist next.

This is a generalist role with an immediate weight on the systems underneath: context, task execution, verification, history, and the interfaces those systems need. You will work alongside a founding design engineer who owns the depth of the experience.

You will receive missions and company context rather than a maintained backlog. The scope grows with the person. What does not change is the expectation that you determine what work moves the mission and carry it through to a reviewed result.

What you'll work on

• build the runtime that turns company context and goals into agent work, verification, and review
• work on structured schemas, parsing, checks, and Git-aware history that keep company context legible and auditable
• design the APIs, data models, and integrations needed to run, inspect, and review work
• build trust through clear state, audit history, verification, rollback, and honest handling of missing information
• implement product surfaces end to end when that is what the mission requires
• create fast feedback loops with agent workflows, browser automation, and comparative review

The work is complete when the parts have been integrated, tested, reviewed at the right level, and shipped as one coherent result.

How you operate

You can take a goal such as “make agent review understandable” and create the work from there. You are comfortable running research, architecture, implementation, and testing in parallel, then using judgment to bring the results together.

You keep useful work in motion. While one line is blocked or running, you can test an assumption, improve the context, or advance another part of the mission. Ordinary ambiguity does not stop you, but consequential decisions get surfaced early.

Technical foundations

Useful experience includes some combination of:

• Python and backend application development
• TypeScript and modern frontend application architecture
• structured schemas, parsers, validators, or Git-backed systems
• LLM application architecture and multi-agent workflows
• data models, event pipelines, and integrations
• production systems with clear verification, observability, and rollback
• browser automation and visual regression testing

You do not need all of these. We care about strong fundamentals, sound judgment, and evidence that you can cross boundaries without lowering the quality bar.

Strong evidence

Show us a product you took from a rough goal to a shipped result, a system whose verification you cared about, or an AI-native workflow where you can explain how work was created, checked, and integrated. We are interested in the system you built around yourself as much as the final artifact.

Working relationship

You will work alongside the founding design engineer and report to Michael. Both roles are expected to improve the system of work alongside the product work.

Location

San Francisco is strongly preferred. We want to work together in person and build shared context quickly during this stage of the company. We will consider an exceptional remote engineer with strong evidence of independent, high-throughput work and excellent written communication.

How we work

We build with shared structured context, spec-driven development, flights of agent work, automated verification, and human review at the decisions that matter.