Founding Marketer
or drop it." The "About Us" is company description; maybe we can include as a paragraph before sections? Not required to have a heading for About Us. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. The "About Us" could be placed as a
before sections. But they didn't list it as a heading; we can just include as a paragraph. Then "The Job" section: description of role. That likely maps to "About the role" or "Responsibilities". We need to decide. We have "About You": qualifications/requirements. We have "What we offer": benefits. We have no explicit Pay or Schedule. So we should not include those sections. We need to extract substantive content. Let's parse: About Us: description of MintMCP. We'll keep as a paragraph. The Job: "You own how MintMCP grows. Turn heavy inbound into measurable, repeatable pipeline across both motions: self-serve, where an engineer tries the gateway, and sales-assisted, where security review turns into a company-wide deal. You own positioning for a technical buyer and demand gen across SEO, AEO, paid, and content. You run a webinar series and a steady stream of campaign experiments, build outbound from the ground up with the AE team, and own the lifecycle that turns signups, trials, and security reviews into pipeline. You also own the numbers: how every channel performs, CAC, payback, and a forecast the team can plan against. What makes this different is how you do it. You will not run every campaign by hand, and you will not wait to hire a team. You orchestrate a fleet of agents to do the research, enrichment, sequencing, follow-up, content drafts, and reporting, so one marketer covers more ground than a traditional team. Agents take on the repeatable work, so the role can stay broad. This role calls for a senior growth marketer with the range to set the message, pick the highest-leverage bets, and instrument the funnel, then use agents to run it. The work is to look at a messy funnel, find the bottleneck, design the experiment, ship it the same day, and read the data the next morning. You report to the CEO and work across the GTM team. The role is in person." That's responsibilities and maybe some qualifications. About You: bullet list of requirements. Let's extract: - You have built a growth marketing function from zero. - You have turned messy demand into measurable pipeline at an early-stage B2B company, ideally dev-tools, infra, or security, and you can point to the number. - You have real positioning and messaging instincts for a technical buyer. - You can hold a conversation with engineers, security leaders, and AI leaders, and turn it into content and campaigns that land. - You have run demand across multiple channels, some mix of SEO, AEO, paid, lifecycle, and content, and you know how to pick the next lever, not just operate the one you know best. - You have run both a self-serve PLG motion and a sales-assist motion into a buying committee, and you know they need different plays. - You own the numbers. You are fluent in attribution and funnel analytics, and you can model CAC, payback, and a forecast the team can plan against. - If that is not your background, you partner well with whoever owns it. - You are deeply AI-native and already use agents to multiply yourself. - You have built or directed agentic workflows, not just used AI tools, and you are excited to run a fleet of agents as your team instead of hiring one. - You thrive before the playbook exists. You decide what matters, ship within hours, measure what happened, and change direction without a mature org around you. - Nice to have: You have stood up outbound that worked, partnering closely with AEs on targeting, messaging, and sequencing, not just running campaigns on your own. - Experience taking a product upmarket, or repositioning and repricing one. - Having built this once already at an AI-native company. - Field marketing or events experience. What we offer: "Competitive compensation and meaningful equity. The room to define how a fast-growing infrastructure company goes to market, and to build the first AI-native growth engine from scratch. Direct access to the CEO, customers, and product direction. Health benefits, on a team that puts family and health first. Prefer to have your agent apply? Point it at https://www.mintmcp.com/hiring/mcp" We should not include application instructions? The instruction says remove application instructions. The last sentence "Prefer to have your agent apply? Point it at ..." is application instruction, so we should drop that line. Also maybe remove the URL. Thus benefits: Competitive compensation and meaningful equity. The room to define how a fast-growing infrastructure company goes to market, and to build the first AI-native growth engine from scratch. Direct access to the CEO, customers, and product direction. Health benefits, on a team that puts family and health first. We could format as a
- list.
Now decide sections:
- About the role: maybe a short paragraph summarizing role? Could use the "The Job" paragraph as About the role.
- Responsibilities: could list specific duties from The Job: own pipeline, positioning, demand gen, webinar series, campaign experiments, outbound, lifecycle, own numbers, orchestrate agents, etc.
- Requirements/Qualifications/Skills: Could combine About You into Requirements and Skills. But we need to avoid duplication. Perhaps we make Requirements for hard requirements, Skills for abilities. But we can just have one section "Requirements" with list.
Given instruction: Prefer a few substantive sections over many thin ones. So we could have About the role (paragraph), Responsibilities (list), Requirements (list), Benefits (list). No Pay or Schedule.
We must not include placeholder text.
Let's craft.
First, a paragraph for About Us (company description) maybe as
before sections. Then
About the role
with a paragraph summarizing role: maybe combine The Job description but not too long. But we must preserve ALL substantive information; cannot summarize away detail. So we need to keep all details, not summarizing. If we put a paragraph that summarizes, we may lose detail. So better to keep the full The Job text as a paragraph under About the role. That preserves all detail. Then Responsibilities: we could extract bullet list of duties from The Job. But that would duplicate content; we would be repeating info. The instruction says preserve ALL substantive information; does not forbid duplication, but we should avoid unnecessary duplication? It didn't forbid duplication but we should not invent or summarize away detail. Duplication is okay but maybe better to avoid redundancy. However we need to include sections only when posting has real specific content for it. The posting has responsibilities described in The Job. We could put them under Responsibilities as a list, and not repeat them elsewhere. Then About the role could be a brief summary? But that would be summarizing, which we should avoid. So maybe we treat About the role as a short intro that is not summarizing but just a heading; but we need to preserve all info, so we need to include the responsibilities somewhere. If we put them under Responsibilities, we have covered them. Then About the role could be a short paragraph that is not summarizing but maybe just a generic statement like "The role is senior growth marketer..." but that would be summarizing. However the instruction says "Do NOT ... emit a heading followed by filler/placeholder text". It doesn't forbid a short summary as long as it's substantive. But we risk losing detail if we don't include the details elsewhere. We could put the full responsibilities under Responsibilities and keep About the role as a brief intro that is not required to capture all details; but we still need to preserve all substantive information somewhere. If we put all details under Responsibilities, we are fine. About the role could be something like "You will own growth marketing at MintMCP, driving pipeline through self-serve and sales-assisted motions." That's still a summary but not filler; it's derived from the details. It's okay. But we must be careful not to lose any detail: we need to ensure that all details from The Job appear either in About the role or Responsibilities. If we put them in Responsibilities list, we covered them. About the role can be a short framing sentence. Thus:About the role
You will own growth marketing at MintMCP, driving pipeline through self-serve and sales-assisted motions, leveraging AI agents to scale execution.
Then Responsibilities list: - Own how MintMCP grows: turn heavy inbound into measurable, repeatable pipeline across self-serve (engineer tries gateway) and sales-assisted (security review → company-wide deal). - Own positioning for a technical buyer and demand gen across SEO, AEO, paid, and content. - Run a webinar series and a steady stream of campaign experiments. - Build outbound from the ground up with the AE team. - Own the lifecycle that turns signups, trials, and security reviews into pipeline. - Own the numbers: channel performance, CAC, payback, forecast for team planning. - Orchestrate a fleet of agents to do research, enrichment, sequencing, follow-up, content drafts, and reporting. - Look at a messy funnel, find bottleneck, design experiment, ship same day, read data next morning. - Report to the CEO and work across the GTM team. - Role is in person (San Francisco Bay Area). Now Requirements list from About You: - Built a growth marketing function from zero. - Turned messy demand into measurable pipeline at an early-stage B2B company (ideally dev-tools, infra, or security); can point to the number. - Real positioning and messaging instincts for a technical buyer. - Able to hold conversation with engineers, security leaders, AI leaders and turn into content/campaigns that land. - Run demand across multiple channels (mix of SEO, AEO, paid, lifecycle, content); know how to pick next lever. - Run both self-serve PLG motion and sales-assist motion into buying committee; understand different plays. - Own the numbers: fluent in attribution and funnel analytics; can model CAC, payback, forecast. - If not background, partner well with whoever owns it. - Deeply AI-native; already use agents to multiply yourself. - Built or directed agentic workflows (not just used AI tools); excited to run a fleet of agents as team. - Thrive before playbook exists; decide what matters, ship within hours, measure, change direction without mature org. - Nice to have: stood up outbound that worked, partnering closely with AEs on targeting, messaging, sequencing. - Experience taking a product upmarket, or repositioning and repricing one. - Having built this once already at an AI-native company. - Field marketing or events experience. We could separate Nice to have as separate list under Requirements or maybe under Skills. But we can include them as part of Requirements list with note "(Nice to have)". Or we could have a Skills section. But we can keep as Requirements. Benefits list: - Competitive compensation and meaningful equity. - Room to define how a fast-growing infrastructure company goes to market, and to build the first AI-native growth engine from scratch. - Direct access to the CEO, customers, and product direction. - Health benefits, on a team that puts family and health first. We should not include