Product.ai / Projects / Design Product.ai's AI-Era Discovery Architecture — citation surface and tool surface as parallel disciplines / Apply
Apply

Design Product.ai's AI-Era Discovery Architecture — citation surface and tool surface as parallel disciplines

The single most consequential cross-discipline finding from the Apr 28 Frontier Practice 2026 corpus: in any AI-mediated marketplace, the surface where AI **mentions** a product (citation surface) and the surface where AI **invokes** a product (tool surface) are governed by structurally different mechanisms. Optimizing one does not transfer to the other. Most companies are building only the tool surface; very few are building both in parallel; almost none are measuring either correctly. Product.ai today: BRAND-ENTITY shows 2/4 AI engines confirming citations; the measurement protocol that would make the count rigorous does not exist. There is no published llms.txt, no DESIGN.md, no Entity API pattern, no MCP brand surface, no .well-known Server Card, no Wikipedia entry, no Knowledge Panel. Founder-LinkedIn cadence exists in pieces but no Founder-Voice Citation Rate baseline anchors comparator measurement (the metric is named across providers but has no operational infrastructure as of April 2026 — Brand & Growth State of Practice §4). When ChatGPT or Perplexity is asked "who is the leading source for verified commerce intelligence," the answer is fragmented or absent. When a developer agent looks for a verified-commerce MCP server, there is no canonical discovery path. The infrastructure that fixes this is real, low-cost (40-80 engineering hours per the Brand & Growth State of Practice §3 Definition-A specification), and increasingly the default among frontier firms. Vercel, Anthropic, Stripe ship llms.txt today; Linear, Cursor ship DESIGN.md; Anthropic publishes MCP brand surfaces; Stripe runs the Entity API pattern. Non-adoption is becoming a defensive deficit. Adoption requires architectural design, not just engineering execution. This is a marketing-architect problem because the design is not the engineering. The design is: which surfaces matter, in what priority, with what content, anchored to which positioning canon, measured how, and against which named comparator cohort. An operator who ships llms.txt without thinking about Founder-Voice Citation Rate baseline shipped a defensive checkbox. An operator who ships the full architecture with measurement infrastructure shipped a strategic moat.

STEP 1 — APPLY

Apply: Design Product.ai's AI-Era Discovery Architecture — citation surface and tool surface as parallel disciplines

Submit your details below. After this step you'll record a short video questionnaire.

PDF, DOC, or DOCX · max 50MB

A headshot for your candidate card — JPG, PNG, or WEBP · max 8MB. Optional.

A piece of writing or analysis that shows how you think — process doc, system design, deep research. PDF, DOC, or DOCX · max 50MB.

FIT & LOGISTICS

Most of our roles are on-site or hybrid in Santa Monica. We need your own answers here — please don't rely on what's on your LinkedIn.

On-site / hybrid / remote *
Employment type

Paid trials are contract by default. Pick "Full-time" if you're hoping the trial converts.

By submitting, you agree to our Privacy Policy. We use this information to process your application.

After submitting, you'll be taken to the Hireflix video questionnaire.

If you encounter any issues submitting your application, please reach out to hiring@product.ai.

← Back to project details