Technical Customer Success Manager

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes location info, description, responsibilities, requirements, benefits. No explicit Pay or Schedule. So we should not include Pay or Schedule sections. Also we should not repeat job title as heading. We need to preserve all substantive info, remove boilerplate like EEO, etc. We need to include location info maybe in a paragraph. Use

for prose. Use

• for lists. We need to decide sections: About the role (maybe intro), Responsibilities, Requirements, Qualifications (maybe combined?), Skills, Benefits. The posting includes "What you’ll do here" (responsibilities), "You’ll love this job if you are…" (skills/qualities), "How you’ll grow within one month..." etc (maybe growth but not required). Also "What we do" (about the company) maybe about the role? Could be About the role. Also location info. We need to avoid filler like "commensurate with experience". Not present. We need to include Benefits section: they list benefits with emojis. Should include them as list. We need to not include application instructions, EEO, etc. Let's extract: Location: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US) About the role: description: "The Technical Technical Customer Success Manager is a perfect role for someone who is technical enough to sit in a customer's codebase and docs, curious enough to become the deepest product expert in the room, and wants to own the customer relationship at a fast-moving startup. You'll be on calls with enterprise engineering and docs teams every week, you'll own a book of accounts end to end, and you'll be the person who figures out how to make ReadMe work for whatever they're trying to do, not the person who files the ticket and waits. At ReadMe the Sales team finds companies that we can solve problems for, and you take over from there. Your role is to oversee a swift and effective implementation, partner with the customer to have a successful first year, identify opportunities for growth and optimization, and make sure the right resources get tapped in to support whatever the customer needs to be successful with ReadMe. You'll solve most technical questions yourself, and know when and how to pull in Engineering or Solutions Architects for the rest." Also "What we do" section: description of company. Responsibilities: "What you’ll do here" bullet list: Own a book of enterprise accounts end to end. Onboarding, adoption, renewal assistance, and expansion. Be the primary technical and strategic contact for each. Be on customer calls regularly, including: implementation kickoffs, working sessions, QBRs, and escalations. This is a customer-facing role, not a ticket-queue role. Act as the product SME for your accounts. Know ReadMe deeply enough to answer product questions in real time, and debug alongside customers when something isn't working. Get hands-on with the technical implementation. Review OAS files, help wire up CI/CD syncing via the ReadMe CLI or API, troubleshoot custom JS/CSS and auth setups, and prototype solutions before handing off to Engineering. Build AI into how you work. Use AI tools to draft implementation plans, analyze account health across your book, triage and summarize customer requests, prototype scripts, and automate the repetitive parts of the job so you spend more time solving real problems. Identify expansion and growth opportunities across your book and partner with Sales to close them. Advocate for customers internally, surface health risks early, and feed structured product and bug feedback to Product and Engineering. Requirements/Qualifications/Skills: "You’ll love this job if you are…" list: Passionate about working with others; you’d be collaborating with lots of new customers, and our Sales, Product, Support and Enterprise Engineering teams! An outstanding communicator, very organized, and able to manage multiple projects at once. Technical enough to read an OpenAPI spec, poke at a customer's HTML/CSS/JS, understand SSO and auth flows, and use Git and a CLI comfortably. You don't need to be a software engineer, but you should be able to hold your own with one. Someone who uses AI as a working tool. You've built prompts, workflows, or small automations that changed how you actually get work done, and you're eager to keep doing that. A problem solver who'd rather figure out the answer than escalate it. You enjoy the puzzle of making a product bend to a customer's real-world constraints. Also growth timeline sections maybe not needed as separate sections; could be part of responsibilities or about role but not required headings. We can include a section "What you’ll do here" as Responsibilities. "You’ll love this job if you are…" as Skills or Qualifications. Could split into Skills and Qualifications but we can combine. We need to avoid duplicate content. Let's craft HTML:

  About the role

  Location: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US).

  [the description about role and company]

  But we need to avoid repeating job title. Already not. We'll include location in a paragraph. Now Responsibilities:

  Responsibilities

  • ...
  ... We need to preserve all bullet points. Let's extract each bullet as separate
  • . From "What you’ll do here": - Own a book of enterprise accounts end to end. - Onboarding, adoption, renewal assistance, and expansion. - Be the primary technical and strategic contact for each. - Be on customer calls regularly, including: implementation kickoffs, working sessions, QBRs, and escalations. - This is a customer-facing role, not a ticket-queue role. - Act as the product SME for your accounts. - Know ReadMe deeply enough to answer product questions in real time, and debug alongside customers when something isn't working. - Get hands-on with the technical implementation. - Review OAS files, help wire up CI/CD syncing via the ReadMe CLI or API, troubleshoot custom JS/CSS and auth setups, and prototype solutions before handing off to Engineering. - Build AI into how you work. - Use AI tools to draft implementation plans, analyze account health across your book, triage and summarize customer requests, prototype scripts, and automate the repetitive parts of the job so you spend more time solving real problems. - Identify expansion and growth opportunities across your book and partner with Sales to close them. - Advocate for customers internally, surface health risks early, and feed structured product and bug feedback to Product and Engineering. We need to ensure each bullet is a separate
  • . Some sentences contain multiple ideas but okay. Now Skills/Qualifications:

    Skills and Qualifications

    • Passionate about working with others; you’d be collaborating with lots of new customers, and our Sales, Product, Support and Enterprise Engineering teams!
    • An outstanding communicator, very organized, and able to manage multiple projects at once.
    • Technical enough to read an OpenAPI spec, poke at a customer's HTML/CSS/JS, understand SSO and auth flows, and use Git and a CLI comfortably.
    • You don't need to be a software engineer, but you should be able to hold your own with one.
    • Someone who uses AI as a working tool. You've built prompts, workflows, or small automations that changed how you actually get work done, and you're eager to keep doing that.
    • A problem solver who'd rather figure out the answer than escalate it. You enjoy the puzzle of making a product bend to a customer's real-world constraints.
    Now Benefits:

    Benefits

    • Unlimited PTO with a three-week minimum.
    • Fully covered medical, dental, and vision insurance for you, and your dependents.
    • A One Medical membership.
    • A wellness stipend for therapy of up to $350 per month for up to 6 months.
    • A wellness stipend of up to $150 per month.
    • One-to-one donation matching of up to $1,000 per year.
    • Twelve weeks of paid parental leave after the birth or adoption of a child.
    • Work from home office stipend of $500.
    • Offsite retreats to get together with coworkers and plan for the quarter ahead.
    We should not include the line "Take a look at our handbook for more information on our benefits!" as it's a reference; could be omitted as it's not substantive benefit. Also remove emojis. We should not include the "Not sure if you’d be the right fit? Apply anyway!" etc. That's application instruction/boilerplate. Also remove EEO statements. Now we need to ensure we didn't miss any substantive info: The "What we do" description about company: "We're a small team of humans (and one owl) working together to do big things, and that’s where you come in. In this role you’ll have a transformational impact on ReadMe across both the trajectory of the business and our thriving culture. ReadMe helps more than 5,000 leading startups and tech companies build beautiful, personalized, and interactive developer hubs. If you’ve ever visited the developer docs for Amazon, Samsara, or Nvidia, you’ve used ReadMe! We love what we do because it’s so much more than just documentation. We’re providing tools for teams to build a better developer experience and make their products and APIs easier to use. We’ve got great support from our investors at Accel who led our Series A, and our interview process reflects the open, caring, and whimsical culture we want to maintain as we scale." We could include that in About the role section. Also the growth timeline sections: "How you’ll grow within one month", "Within three months", "Within six months". Could be part of About the role or maybe a separate section "Growth and Development". But the instruction says prefer few substantive sections over many thin ones. Could incorporate into About the role or Responsibilities? Might be better to include as a separate section "What you’ll achieve" but not required headings list includes only those specific headings. We could put under About the role as prose. Thus About the role will contain location, company description, and growth timeline. Let's craft About the role paragraph(s). Use

    for prose. We'll have:

    About the role

    Location: San Francisco (Hybrid), New York (Hybrid), Columbus (Hybrid), or Remote (US).

    The Technical Customer Success Manager is a perfect role for someone who is technical enough to sit in a customer's codebase and docs, curious enough to become the deepest product expert in the room, and wants to own the customer relationship at a fast-moving startup. You'll be on calls with enterprise engineering and docs teams every week, you'll own a book of accounts end to end, and you'll be the person who figures out how to make ReadMe work for whatever they're trying to do, not the person who files the ticket and waits. At ReadMe the Sales team finds companies that we can solve problems for, and you take over from there. Your role is to oversee a swift and effective implementation, partner with the customer to have a successful first year, identify opportunities for growth and optimization, and make sure the right resources get tapped in to support whatever the customer needs to be successful with ReadMe. You'll solve most technical questions yourself, and know when and how to pull in Engineering or Solutions Architects for the rest.

    We're a small team of humans (and one owl) working together to do big things, and that’s where you come in. In this role you’ll have a transformational impact on ReadMe across both the trajectory of the business and our thriving culture. Read