Technical Customer Success Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "The job", "About You", "What we offer". Need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's extract content. About Us: description of company. Could be "About the role"? Actually "About Us" is company description, not role. But we can put under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings as appropriate. The posting includes "About Us" (company overview). Could be placed under "About the role"? Might be better to treat as "About the role" includes description of role and company? But we have separate sections: "The job" describes responsibilities. "About You" describes requirements/qualifications/skills. "What we offer" describes benefits. Thus we can create sections: - About the role: maybe combine About Us + The job? But we should not repeat job title as heading. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have heading About the role (h3) and then content about role and company. - Responsibilities: from "The job" details. - Requirements: from "About You" maybe split into Requirements and Qualifications? Could combine. - Skills: maybe from "About You" technical comfort etc. - Benefits: from "What we offer": Competitive base, variable, equity, health benefits, etc. - Pay: not specified explicitly; they say Competitive base, variable, and significant equity. That's pay info. So we can include Pay section with that. - Schedule: they mention role is in person, with travel to meet customers. So schedule: in-person, travel. We must not include sections with filler like "not specified". We have actual content. We must remove boilerplate: navigation, legal, EEO, etc. At end there is "Prefer to have your agent apply? Point it at https://www.mintmcp.com/hiring/mcp" - that's application instruction, should be removed. Also remove duplicated lines. Now craft HTML. Structure:

About the role

... combine About Us and maybe brief role overview.

Responsibilities

• ... list items from The job.

Requirements

• ... from About You: exceptional with customers, owned customer relationships end to end, can run a plan, comfortable in technical conversations, carried retention and expansion, built structure, calm under pressure, AI-native or will get there fast, move fast, want to grow into leading a team, bonus AI solutions engineer background, sold to/supported technical buyers, experience with enterprise rollouts, comfort representing company in person.

Maybe also Qualifications separate? Could combine Requirements and Qualifications but we need to decide. The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we have both headings allowed. Might be better to have Requirements and Qualifications separate if we have distinct content. However we can put all under Requirements and skip Qualifications to avoid thin section. Similarly Skills could be merged. But we need to include Skills section if we have specific skill content. The About You includes technical comfort, AI-native, etc. Could be skills. But we can combine. Given instruction to prefer few substantive sections, we could have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. Let's extract details precisely. About Us content: "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. Our product gives those agents governed access to company data and tools. That has to start from trust. 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 description: "You own the customer once the deal is signed, all the way through. On day one that means building the mutual delivery plan with the customer: what success looks like, who does what, and by when. You drive onboarding, get the product live against real use cases, and stay close as usage grows. You are the person the customer trusts to make their rollout work. From there you own the whole arc. You track account health, run the check-ins and business reviews, catch problems before they become risks, and pull in engineering or the founders when a customer needs more than you can give them alone. You own renewals, and you find and grow expansion, more teams, more agents, more of the company's work running on us. When something is on fire, you are the one who owns getting it resolved. You'll also push in both directions. On the customer side, that means telling them when what they've asked for isn't what they need, and reframing it against what we've seen work elsewhere. Internally, it means advocating for your customers clearly and directly to the founders — while weighing what they want against what the company needs to prioritize. We'd rather you argue with us than quietly agree with a customer. You are our first dedicated post-sales hire, so you also build the function. You turn what works into a repeatable motion: the delivery plan template, health scoring, the review rhythm, the handoff from sales. As the customer base grows, you help decide who we hire next and grow into leading customer success. The role is in person, with travel to meet customers." About You: "You are exceptional with customers. People trust you quickly, and you keep a rollout on track without being told to. This is the core of the job. You have owned customer relationships end to end, in customer success, account management, consulting, or a client-delivery role. You can run a plan and drive it to an outcome across a customer's team, aligning stakeholders, tracking commitments, and keeping momentum. You are comfortable in technical conversations without being an engineer. You can hold your own with a technical buyer, explain what the product does and why it matters, and know when to pull in the team for the deep end. You do not write config or debug integrations. You have carried retention and expansion, or have the commercial instinct to, and can point to relationships you kept and grew. You have built structure where there was none, playbooks, templates, cadences, and you would rather build the motion than inherit one. You are calm under pressure and own the outcome when a customer is unhappy. You are AI-native, or will get there fast, and are genuinely curious about AI, agents, and how companies adopt them. You move fast without a lot of process, and you want to grow into leading a team. Bonus AI solutions engineer or forward-deployed engineer background. You've sold to or supported technical and engineering buyers. Experience with enterprise rollouts where security review, procurement, and multi-threading are part of the relationship. Comfort representing the company in person: business reviews, dinners, and on-site meetings with technical and security leaders." What we offer: "Competitive base, variable, and significant equity. Full ownership of your accounts, with room to build the function and grow into leadership. Direct access to the CEO, customers, and product decisions. Health benefits, on a team that puts family and health first." Now we need to map to sections. About the role: combine About Us and maybe brief role overview? Could include company description and role overview (the job summary). But we have separate Responsibilities section. So About the role could be company description plus maybe high-level role purpose. Let's put About Us content there. Responsibilities: list items from The job. Requirements: list items from About You (excluding bonus maybe). Could include all. Benefits: from What we offer (excluding compensation). Benefits: Full ownership of accounts, room to build function and grow into leadership, Direct access to CEO, customers, product decisions, Health benefits, team that puts family and health first. Pay: Competitive base, variable, and significant equity. Schedule: The role is in person, with travel to meet customers. Now ensure we don't include filler like "not specified". All good. Now produce HTML fragment. We need to use

for each section heading. Use

• for lists. Use

  for prose. We'll output:

  About the role

  ... (About Us paragraph)

  Responsibilities

  • Own the customer once the deal is signed, all the way through.
  • Build the mutual delivery plan with the customer: define success, responsibilities, and timeline.
  • Drive onboarding and get the product live against real use cases.
  • Stay close as usage grows and be the trusted person for the rollout.
  • Track account health, run check-ins and business reviews.
  • Catch problems before they become risks and pull in engineering or founders when needed.
  • Own renewals and find/expand expansion: more teams, more agents, more of the company's work on the platform.
  • Own incident resolution when something is on fire.
  • Advocate for customers internally to founders while balancing company priorities.
  • Build the post‑sales function: create delivery‑plan template, health scoring, review rhythm, handoff from sales.
  • Help shape future hiring and grow into leading customer success as the base expands.

  Requirements

  • Exceptional with customers; able to earn trust quickly and keep rollouts on track.
  • Proven experience owning customer relationships end‑to‑end in customer success, account management, consulting, or client‑delivery roles.
  • Ability to run a plan and drive it to an outcome across a customer's team, aligning stakeholders, tracking commitments, and maintaining momentum.
  • Comfortable in technical conversations without being an engineer; can explain the product’s value to technical buyers and know when to involve deeper expertise.
  • Experience carrying retention and expansion, or strong commercial instinct to do so, with demonstrable relationships kept and grown.
  • Track record of building structure where none existed: creating playbooks, templates, cadences, and prefer