Founding Engineer

You'd be one of the first engineers here, and you'd own a vertical end to end. By "own a vertical" we mean something specific. Not a ticket queue. You take a real part of the business; sourcing, negotiation, logistics and customs, inventory, or the buyer-facing product, and you're the person responsible for it working.

You talk to the customers who use it. You decide what gets built. You write it, ship it, watch it break at 2am, and fix it. When it works well, that's your win. When it doesn't, nobody's going to hand you a spec explaining why.

Concretely, in your first few weeks you might: - Build a new agent in our procurement pipeline — something that reads a BOM and decomposes it into sourceable line items, or one that handles customs documentation.

- Take our negotiation agent from "usually gets a better price" to "reliably beats what a good human buyer would get," which means building the evaluation harness to even know if you did.

- Design the inventory system from scratch — what's on the shelf, what's in transit, what's committed, and what a hardware team actually needs to see. - Sit with a customer's procurement lead for a day, watch what they do, and come back and rebuild the part of our product that was quietly wrong.

What we work with TypeScript end to end. Agents and backend. LangGraph, Node, Express, Postgres, Langfuse - yes we take our evals seriously. Product. Next. js, React, Tailwind, shadcn/ui, TanStack Query Data and infra. Postgres, Drizzle, Vercel You don't need to have used all of this. Most people haven't.

What matters is that you can pick up an unfamiliar tool quickly and have opinions about it a week later. Who we're looking for We care much more about how you think than what you've already used. You should be someone who: - Ships.

You have things you've built that real people used — a startup, an open source project, something at a previous job you can point at and say "that was mine." - Is genuinely fast. Not sloppy-fast. Fast because you ha