Founding Product Marketing Manager

We need to output HTML fragment with sections: About Us, The Job, About You, Details? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting: It includes "About Us", "The Job", "About You", "Details". Also there is "Competitive salary and meaningful early-stage equity (add a range before posting)." That's a mention of salary but not a specific range; they say "add a range before posting". So we should not create a Pay section because no actual range given. Benefits? Not mentioned. Schedule? Not mentioned. So we should only include sections with substantive content: About Us, The Job, About You, Details (location). Possibly also "Nice to Have" could be part of About You or Requirements. But we need to follow headings: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However they gave examples but we can use other headings? Likely we should use those standard headings if applicable. But we have sections like About Us, The Job, About You, Details. Those are not in the list but they are headings in the posting. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not limited to those. So we can use any heading but must be

  . So we will output

  About Us

  , etc. We need to use
  • for any list of duties/requirements/benefits. In the posting, there are bullet-like sentences but not explicit bullet lists. We can convert sentences that are lists into
    • . For example, in About Us: "Our first product is an MCP gateway that gives those agents governed access to company data and tools. Before agents can touch Slack, GitHub, Jira, Snowflake, internal databases, or production systems, you need to know what they can reach, what they did, and why they were allowed to do it." That's not a list but could be turned into list? Probably not needed. The "You'll..." sentences in The Job are a series of responsibilities; we could make a
      • for each responsibility. Similarly About You bullet points could be list. Details: location and salary/equity mention. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting ends with "To apply: email hiring@mintmcp.com and tell us why you're interested." That's application instructions; we should remove that. Also "Details In person, San Mateo and San Francisco. Competitive salary and meaningful early-stage equity (add a range before posting)." That's details; we keep location and equity mention but not the "add a range before posting" maybe it's part of the sentence; we keep it as is? It's part of the sentence; we should keep the substantive info: "Competitive salary and meaningful early-stage equity". The parenthetical "(add a range before posting)" is instructional for the poster; maybe we should drop that as it's not substantive to candidate. Could be considered boilerplate? It's a note to the poster; we should drop it. So we keep "Competitive salary and meaningful early-stage equity." Now we need to avoid creating Pay/Schedule/Benefits sections unless posting actually states them. It mentions competitive salary and equity but not specific range or benefits. So we should not create a Pay section; we can include that info in Details section as prose. Now we need to ensure we don't create sections with filler text. All sections we create have content. Let's draft:

        About Us

        MintMCP helps companies put agents to work safely. We exist to help companies do more of their work with agents, and we build the infrastructure that makes a company's own work runnable by them. That has to start from trust. Our first product is an MCP gateway that gives those agents governed access to company data and tools. Before agents can touch Slack, GitHub, Jira, Snowflake, internal databases, or production systems, you need to know what they can reach, what they did, and why they were allowed to do it. Most people carry far more permissions than any single task needs. If an agent uses your token directly, it inherits all of them. MintMCP scopes that access down to exactly what an agent needs to do its job and captures the data flows and audit logs security teams need. From there we are building the rest of the agent stack: connectors, monitoring, sandboxing, long-running agents, and memory, with the goal of becoming the system a company's work runs on. We work in person in the San Francisco Bay Area. The structure is flat and the market moves fast, so you have a lot of latitude over what you work on and how. We are AI-native. Everyone uses Claude and Codex every day, and we have more agents than employees. They run in Slack alongside the team and handle sales, marketing, deal ops, and engineering on the same gateway we sell to customers, and we are building an entire company operating system around them. Since launching in February 2026, we have grown to 50+ paying customers, with strong inbound demand. Customers include Coursera, Arlo, and Braze. We are backed by Cowboy Ventures and Coatue, with angels including Frederic Kerrest (Okta), Michael Grinich (WorkOS), Andrej Karpathy, Jeff Dean, and Scott Belsky. Our founders are machine learning experts from Stanford, Berkeley, and CMU, with applied research at Google Brain and Waymo, and one co-founded Coursera.

        The Job

        You own how MintMCP shows up in the world. We're defining a category as it forms — how enterprises put AI agents to work without handing over the keys — and you're the one who turns a deep, fast-moving technical product into a story that engineers, security leaders, and buyers actually get. This is a founding role, so you own the whole arc. You'll set our messaging and narrative, the source of truth for what we say, to whom, and why it matters, and you'll hold it steady as the product and the market move underneath you. You'll drive launches end to end, from narrative to release to follow-through, staying close enough to customers to carry each release from beta to broad availability and own how activated people are on what ships. You'll turn customers like Coursera, Stability AI, and Modern Treasury into case studies and proof. You'll establish MintMCP's point of view on agent governance and get it heard through thought leadership, the SEO/AEO engine, and the agencies that scale it. And you'll build the sales content system that equips our AEs with the collateral they own for prospects and customers. You'll scale yourself with MintMCP’s team of coworker agents (our own product). You'll sit with engineers to learn how the product really works and with customers to hear how it lands, and turn both into differentiated, jargon-free messaging. Do it well and MintMCP's story becomes the one the whole category gets described in.

        We could also convert the "You'll..." sentences into a list. The instruction: Use
        • for any list of duties/requirements/benefits. The responsibilities are a list; we could make a
          • for each. Let's do that to follow instruction. So after

            The Job

            , we can have
            • You set our messaging and narrative, the source of truth for what we say, to whom, and why it matters, and you'll hold it steady as the product and the market move underneath you.
            ... etc. But we need to keep the introductory sentences before the list? The paragraph "You own how MintMCP shows up in the world.... This is a founding role, so you own the whole arc." Could be kept as prose before the list. Then list the responsibilities. Let's do:

            You own how MintMCP shows up in the world. We're defining a category as it forms — how enterprises put AI agents to work without handing over the keys — and you're the one who turns a deep, fast-moving technical product into a story that engineers, security leaders, and buyers actually get. This is a founding role, so you own the whole arc.

            • Set our messaging and narrative, the source of truth for what we say, to whom, and why it matters, and hold it steady as the product and the market move underneath you.
            • Drive launches end to end, from narrative to release to follow-through, staying close enough to customers to carry each release from beta to broad availability and own how activated people are on what ships.
            • Turn customers like Coursera, Stability AI, and Modern Treasury into case studies and proof.
            • Establish MintMCP's point of view on agent governance and get it heard through thought leadership, the SEO/AEO engine, and the agencies that scale it.
            • Build the sales content system that equips our AEs with the collateral they own for prospects and customers.
            • Scale yourself with MintMCP’s team of coworker agents (our own product).
            • Sit with engineers to learn how the product really works and with customers to hear how it lands, and turn both into differentiated, jargon-free messaging.

            Do it well and MintMCP's story becomes the one the whole category gets described in.

            Now About You section: similar approach.

            About You

            5+ years in product marketing, ideally with technical or infrastructure products. A strong writer and storyteller who can turn deep technical capability into a clear narrative. You can sit with engineers and customers, absorb deep technical detail, and turn it into differentiated, jargon-free messaging. A strategic thinker — you set positioning and priorities, make sharp trade-offs about what not to do, and tie marketing back to company goals. Agent-native — you use Claude and agents to scale your own output, with the judgment to tell a differentiated, on-strategy idea from one that only sounds good. Well organized — the scope is broad, and you'll wrangle engineers, internal teams, customers, and agencies at once without letting things slip. Bias to ship — you can run a launch and move fast. A track record you can point to: a product or category you positioned, a launch you ran, and the results that followed.

            Nice to Have

            • Familiarity with MCP, AI agents, or enterprise security.
            • You know the CIO, CISO, and platform/IT buyer