Founding Engineer

In your first 30 days, you’ll ship a real product surface or infrastructure improvement. Likely something around browser automation, MCP/tool reliability, or agent state visibility.

In your first 60–90 days, you should own a major part of the product: desktop runtime, tool execution, realtime sync, or team workflow sharing.

I started OpenWork while running my previous startup on AI workflows. The product came from wanting to share my own agent setup with coworkers — not as prompts in a doc, but as reusable skills, tools, MCPs, and workflows the whole team could actually use.

That’s still the core idea.

OpenWork is not single-player AI chat. The future is teams of humans + agents coordinating in the same workspace.

The kind of person who will do well here:

\- has built real things end-to-end

\- has strong taste and can explain why something is good or bad

\- can move fast without filling the codebase with slop

\- likes hard product/engineering problems

\- cares about reliability, permissions, and trust

\- wants ownership, not tickets

I’m especially interested in people who have built great realtime or multiplayer product experiences. Shared workspaces, presence, collaborative editors, event streams, permissions, live sync, CRDTs, Replicache, Yjs, multiplayer UX — anything where multiple people interact with the same state and it has to feel fast and reliable.

In-person in SF.

Not “maybe one day SF.”

Not remote.

Comp: $200k salary + 3–5% equity.

If this sounds obvious to you, reach out with what you’ve built. GitHub, demos, weird projects, products people actually used — much better than a polished resume.

A meeting lands on your calendar

If they’re a yes, I book the chat. You show up — that’s the whole job-hunt.