Design Engineer, SimplyCodes

You can draw the screen and ship it the same day. You own the design and the code of the Simply Codes screens, the interface that earns the large majority of the company's revenue, beside the designer who owns the bar.

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.

Design here is held to a founder-level bar by one Founding Designer, whose focus is now the design strategy of our chat agent. That leaves the Simply Codes screens, the code-verification pages real shoppers use every day, without a dedicated owner who can draw a screen and ship it the same day. This seat is that owner, starting on Simply Codes specifically.

It is one of the most urgent seats in the company right now: a surface that earns the large majority of our revenue, that people find and trust through search before they ever use it, and that has no full-time design owner today.

You're earlier in your career than most people we hire, maybe two to five years in, and that's on purpose. What we need isn't seniority. It's someone who already thinks in both design and code, has a real human-computer interaction background, is fluent with the AI tools that now do the mechanical part of both, and wants to run a consumer surface end to end while learning the taste side beside someone who has it.

You work beside our Founding Designer, and you have a direct line to the founder.

The part that makes this different from a frontend job with a nicer title: our design system is law, not a guideline. Its tokens and components are read directly by the agents that generate our interfaces, so an ambiguity in the system becomes a defect in the product. Owning that layer for Simply Codes, the machine-readable design layer, is the AI half of the job.

• Simply Codes as the cash engine. The code-verification and merchant pages earn the large majority of the company's revenue, so a design defect there is a revenue defect, not a polish issue.
• Pages built for two readers at once. A shopper who has to trust that a code works, and the search engine that finds and ranks the page before any person sees it.
• A design system agents build inside. Tokens, a component catalog and usage rules precise enough that an AI generating a Simply Codes screen stays within them without a person checking every line. Ambiguity in the system becomes a defect in the product, so precision is the craft, not decoration.
• Decision-shaped interfaces. The unit of a Simply Codes screen is a verified code and how sure we are that it works. Confidence has to read honestly, never oversold and never buried, and that's motion, state and typography doing trust work.
• 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.

• The Simply Codes screens. The code-verification and merchant pages, design and code, end to end. The product manager who owns the Simply Codes website decides what a page does; you decide how it looks, behaves and is built.
• The design system in code, for Simply Codes. The tokens, components and rules the agents generate inside, kept precise, documented and current. When a generated screen breaks the system, you find out why the system let it, and you fix the system. The engineer who owns the frontend codebase's infrastructure and performance keeps that fortress; you own the design-system layer and the interface craft inside it.
• Working prototypes and shipped components. Directions taken from a sketch to a running prototype and, when they clear the bar, to production. You build in design tools and in code, and you don't wait for a handoff in either direction.
• The polish layer. Motion, state, spacing, type: the thousand small decisions that make a trust interface feel trustworthy. You notice a misaligned pixel and you can say what it costs.
• Your seat charter. Within your first quarter you co-sign a charter for this seat. It names one…