Product Engineer

Product.ai has more consumer surfaces than owners. We're hiring product thinkers through several doors, and this is the engineer's door: someone who came up writing code, has shipped things people use, and now wants to own the product outcome instead of the ticket.

Compensation $325k - $425k

You own one Product.ai consumer surface end to end: the product call, the spec, the build and the ship. Agents write most of the code. You own the verdict on whether it's right.

Product.ai (product.ai) is the verified truth layer for shopping: when a person or an AI agent needs to know what's actually true about a purchase, we answer with proof. Simply Codes () is the first proof at scale, the code verification service, at about $22M a year in revenue. Profitable. Founder-owned since 2009, bootstrapped, no outside investors, no board. Fewer than twenty operators.

Product.ai has more consumer surfaces than owners. We're hiring product thinkers through several doors, and this is the engineer's door: someone who came up writing code, has shipped things people use, and now wants to own the product outcome instead of the ticket.

A product engineer here decides what to build and how they'll know it worked. You weigh the data, the user and your own taste, make the calls in the gray area, write the spec, and direct the agents that write most of the code. Then you verify what came back, because an agent's output is something you check, never something you accept.

Your surface is one no one here holds yet, and two are waiting for an owner. The first is the consumer experience inside the AI platforms that now show our answers: what a person sees and does when ChatGPT, Siri, Gemini or Claude hands them a Product.ai verdict. The second is personalization: a shopper's own constraints and preferences, remembered and applied to every verdict they get.

Which one is yours is the first conversation with the founder, and we write the answer down. The interface contract those platforms call belongs to our technical product seat; what a person sees and does once the answer arrives belongs to you.

• Decision-shaped consumer interfaces. The unit of our product is a verdict, not a chat transcript: what's true, the evidence behind it, how sure we are, and when the honest answer is "don't buy." The user changes a constraint and watches the verdict move. Streaming, citation-bearing, trust-critical: one wrong claim rendered confidently costs more than a month of speed.
• Preference-aware answers. A verdict that remembers what this shopper cares about is a different product from one that doesn't. It's a data model, a consent and trust problem, and an interface problem at once, and the three have to be designed together.
• A spec-driven agentic build pipeline. Intent becomes a visual mockup, then a locked spec, then agents build against it in unattended runs of one to four hours, then separate verifier agents grade the build against the spec. The building agent never grades its own work. Your spec is the interface the whole loop builds and grades against, so your judgment is the gate, not your keystrokes.
• Cortex, the shared AI brain the company runs on. You'll work inside it daily, directing coding agents the way our founder does, and since August any operator here can change the rules the company runs on, live, without waiting on him.

If reading that energizes you, keep going. If it feels overwhelming or under specified, this isn't the right fit.

• One consumer surface, end to end. The experience, the metrics, the roadmap and the build, owned the way a founder owns a product. Your surface carries falsifiable outcomes, each with an evidence test a stranger could run.
• The product calls in the gray area. Most decisions on a consumer surface have no clean data answer. When does a confidence indicator build trust, and when does it plant doubt? When is "don't buy this" the right thing to render boldly? You weigh the data, the user and your taste, and you decide. What's visible here is decisions registered and outcomes moved.
• The spec and the gate. With our Founding Designer, who owns the design system and the mockup-before-code gate, you run the discipline that everything on your surface gets seen before it gets built. You write the spec agents build from and the acceptance tests that decide whether a long unattended run shipped the right thing.
• Verification for agent-written product code. You define what…