Work With Us

We're Pagemind. We're building the catalog operating system for AI commerce — a closed multi-agent loop that takes a merchant's catalog and continuously enriches it, publishes AI-ready content under the merchant's editorial approval, surfaces an on-site chat + voice grounded in that same catalog, monitors how AI assistants are citing the brand, and feeds the observed demand gaps back into the next generation cycle.

Every node in that loop is its own product. Most "AEO platforms" ship one. We ship the loop.

Customers like TradeInn run ~14k products live across 7 brands and 18 languages on this stack today.

We're small. We're going to stay small for longer than is comfortable. There's no team to hide behind, no specialization to point at, no roadmap committee. The people we want here treat that as the point, not the problem.

You're a builder. You happen to have design skills — taste, sense of pace, a feel for how an interface lets a real human do their job — and you use those skills as one tool among several.

You don't wait for a brief. You ship the brief.

You don't hand off Figma to engineering. You ship working surfaces — in TypeScript, in Tailwind, in React, in whatever else gets the artifact into a customer's hands this week.

You vibe-code. You drive Claude, Cursor, v0, Figma Make, and whatever the next AI build tool turns out to be.

You move fast because the tools moved faster than the discipline did, and you've internalized that the bottleneck is no longer skill — it's taste + judgment + how many real customers you talked to this week.

You'd be at the front of the discovery loop, not at the end.

• You sit in customer calls.
• You watch real editors approve drafts in our human-in-the-loop workflow.
• You see a 14k-product catalog being navigated in real time, and you decide what surface needs to exist so the merchant's catalog manager opens it every Monday the way they open Search Console today.
• You ship the v1, get the customer's reaction, and iterate before the week is out.

You believe that "many roads might be right." When you see a problem, your first instinct is to explore 3-5 directions, prototype them at low cost, and let the customer's reaction collapse the option space. You're skeptical of single-track convictions, including your own.

The shape we're looking for is intellectually pluralistic, sensible, and high-agency. Some markers we'd find credible:

• You've shipped products end-to-end — not handed off design files, shipped working software people use.
• You've used AI tools as a build accelerator (not just generated UI mockups). You can talk specifically about what you've built that wouldn't have shipped without them, and where AI tools fall short for the kind of work you do.
• You know how to define what success looks like for complex problems.
• You can hold a 30-minute conversation with a customer — not a user research script, an actual conversation — and walk out knowing what to ship next.
• You have opinions about taste. You can defend why one micro-interaction reads as Stripe-quality and another reads as 2018-SaaS-tutorial.
• You don't need a product manager to scope your work, but you'll happily work with one. Same for engineers, designers, and CEOs.
• Bonus: you've worked in SaaS, e-commerce, marketing tools, or AI-native products before.

• A founding-team role. You shape the product surface, the design system, and the GTM artefacts. Your fingerprints are on every customer-facing surface.
• A team that's small enough that you'll see your work reach customers in days, not quarters.
• The technical substrate is real. 20+ specialist agents, a closed-loop architecture, multi-language production at scale, a paying enterprise customer running it on 14k SKUs. You're not designing for vapor.
• A category that doesn't exist yet. We're not iterating on a known wedge — we're defining what "catalog operating system" means in the AI-commerce era. Half the work is figuring out what should exist before drawing it.
• Remote setup with a weekly co-working day in Barcelona.

• A specced-out roadmap. We have a vision, priorities, customer feedback, and a closed loop that surfaces what needs shipping next. We don't have quarterly Jira tickets.
• A career ladder. Responsibility grows with you. That's it.
• A design team to lean on. You'd be the design function. (For now.)

Send us:

• Three to five things you've shipped that you're proud of. Especially things where you held the whole loop — discovery, design, build, customer reaction, iteration. If your work isn't online, walk us through it in a short Loom.
• One thing you would build for Pagemind in your first two weeks. Doesn't have to be right. Has to be specific. We care about how you think about the loop, not whether you guessed our roadmap.
• A line about how you've used AI tools to ship things you couldn't otherwise have shipped.

Send to: [email protected]. We read everything. We respond to everyone. If we want to talk, the next step is a 30-minute conversation.