Customer Success Manager

We need to output HTML fragment with sections for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. The posting includes: About Luthor (company description) - not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to parse the posting: It includes: - About Luthor (company description) – not a required heading but could be included as a paragraph? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities...). Likely we should only use those headings if content exists. The "About Luthor" is not one of those headings; maybe we can just include it as a

before sections. - About The Role: This is a heading we can use as

About the role

. Then content: description of role, responsibilities, etc. We need to separate Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule if present. Let's extract content: From "About The Role" paragraph: "Customer success is one of the most important functions at Luthor. Our customers are large, highly regulated institutions deploying Luthor into workflows that directly affect what they can say to the public. Making those deployments successful means deeply understanding their business, earning the trust of compliance and marketing teams, and turning Luthor into a product they can’t imagine operating without. This is a very different job from a traditional CSM role. You’ll work directly with the founders: You’ll have a front-row seat to how we build the company and help define the customer success playbook from the ground up.You’ll work with sophisticated customers: Our users sit inside some of the world’s largest financial institutions. You’ll build relationships across compliance, legal, marketing, and leadership teams.You’ll shape the product: You won’t just relay feature requests. You’ll understand how customers actually work, identify what’s blocking adoption, and work directly with engineering to make the product better.You’ll own outcomes, not tickets: Your job is to make customers successful—from onboarding and implementation through adoption, expansion, and renewal.You’ll have real responsibility: We’re still a small team. The systems, processes, and customer relationships you build will become the foundation for the team that follows. The most important quality we’re looking for is customer empathy. You should genuinely care about understanding what someone is trying to accomplish and be relentless about helping them get there. It Also Helps If You’re Exceptional with people: You build trust quickly, make customers feel heard, and can navigate difficult conversations without damaging the relationship.Product-minded: You can tell the difference between a training problem, a workflow problem, and a product problem—and communicate that clearly to engineering.A clear communicator: You’re equally comfortable working with a day-to-day user, a compliance leader, or an executive.Highly organized: You can manage multiple enterprise customers, implementations, priorities, and follow-ups without letting things fall through the cracks.Comfortable with ambiguity: There isn’t a mature CS playbook waiting for you. You’ll help create it. You’ll work directly with the founding team in San Francisco and have an unusually large amount of ownership over how some of the world’s most important financial institutions adopt Luthor. If AI is going to speak for the world’s most important institutions, someone has to make sure they can trust what it says. You’ll help make that happen." Thus we have responsibilities and qualifications/skills mixed. We need to split into sections: About the role (maybe a brief summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to see if any explicit Benefits, Pay, Schedule are mentioned. I don't see any mention of benefits, pay, schedule. So we should NOT create those sections. We need to extract responsibilities: likely the bullet points about working with founders, customers, shaping product, owning outcomes, real responsibility, etc. Requirements/Qualifications/Skills: The list of qualities: customer empathy, exceptional with people, product-minded, clear communicator, highly organized, comfortable with ambiguity. Also maybe "work directly with founding team in San Francisco" (location). Could be considered a requirement. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as they appear, but we can format as

• for lists. We need to avoid filler like "commensurate with experience". Not present. Thus we can produce:

  About Luthor: ...

  maybe. Then

  About the role

  with a paragraph summarizing the role? But the instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having a paragraph under About the role. So we can put a short paragraph summarizing the role (maybe the first few sentences). Then separate Responsibilities as

  Responsibilities

  with
  • items. Then

    Requirements

    maybe with
    • items for customer empathy, etc. Or we could split into Qualifications and Skills. But we need to decide based on content. The posting lists: "The most important quality we’re looking for is customer empathy. You should genuinely care about understanding what someone is trying to accomplish and be relentless about helping them get there. It Also Helps If You’re Exceptional with people: You build trust quickly, make customers feel heard, and can navigate difficult conversations without damaging the relationship.Product-minded: You can tell the difference between a training problem, a workflow problem, and a product problem—and communicate that clearly to engineering.A clear communicator: You’re equally comfortable working with a day-to-day user, a compliance leader, or an executive.Highly organized: You can manage multiple enterprise customers, implementations, priorities, and follow-ups without letting things fall through the cracks.Comfortable with ambiguity: There isn’t a mature CS playbook waiting for you. You’ll help create it." These are skills/qualities. Could be considered Skills. Could also be Qualifications. The instruction includes both Qualifications and Skills as possible headings. We could put them under Skills. Or we could split: Qualifications: maybe "work directly with founding team in San Francisco", "experience with enterprise customers"? Not explicit. Better to put all those under

      Skills

      as a list. We could also have

      Requirements

      for maybe "experience with financial institutions"? Not explicit. Thus we can have: - About the role (paragraph) - Responsibilities (list) - Skills (list) We should not create Requirements or Qualifications if not distinct. Check if any explicit "Requirements" like "You’ll work directly with the founding team in San Francisco" could be a requirement (location). Could be included under Responsibilities or Skills? It's more about location/working arrangement. Could be a requirement. But we can include it under Responsibilities as a bullet: "Work directly with the founding team in San Francisco". However the posting says: "You’ll work directly with the founding team in San Francisco and have an unusually large amount of ownership over how some of the world’s most important financial institutions adopt Luthor." That's more about responsibility/ownership. Thus we can incorporate that into Responsibilities. Now we need to ensure we preserve all substantive information. Let's extract all sentences from the About The Role section and allocate. Paragraph 1: "Customer success is one of the most important functions at Luthor. Our customers are large, highly regulated institutions deploying Luthor into workflows that directly affect what they can say to the public. Making those deployments successful means deeply understanding their business, earning the trust of compliance and marketing teams, and turning Luthor into a product they can’t imagine operating without." That's a general description. Paragraph 2: "This is a very different job from a traditional CSM role. You’ll work directly with the founders: You’ll have a front-row seat to how we build the company and help define the customer success playbook from the ground up." Paragraph 3: "You’ll work with sophisticated customers: Our users sit inside some of the world’s largest financial institutions. You’ll build relationships across compliance, legal, marketing, and leadership teams." Paragraph 4: "You’ll shape the product: You won’t just relay feature requests. You’ll understand how customers actually work, identify what’s blocking adoption, and work directly with engineering to make the product better." Paragraph 5: "You’ll own outcomes, not tickets: Your job is to make customers successful—from onboarding and implementation through adoption, expansion, and renewal." Paragraph 6: "You’ll have real responsibility: We’re still a small team. The systems, processes, and customer relationships you build will become the foundation for the team that follows." Paragraph 7: "The most important quality we’re looking for is customer empathy. You should genuinely care about understanding what someone is trying to accomplish and be relentless about helping them get there." Paragraph 8: "It Also Helps If You’re Exceptional with people: You build trust quickly, make customers feel heard, and can navigate difficult conversations without damaging the relationship." Paragraph 9: "Product-minded: You can tell the difference between a training problem, a workflow problem, and a product problem—and communicate that clearly to engineering." Paragraph 10: "A clear communicator: You’re equally comfortable working with a day-to-day user, a compliance leader, or an executive." Paragraph 11: "Highly organized: You can manage multiple enterprise customers, implementations, priorities, and follow-ups without letting things fall through the cracks." Paragraph 12: "Comfortable with ambiguity: There isn’t a mature CS playbook waiting for you. You’ll help create it." Paragraph 13: "You’ll work directly with the founding team in San Francisco and have an unusually large amount of ownership over how some of the world’s most important financial institutions adopt Luthor." Paragraph 14: "If AI is going to speak for the world’s most important institutions, someone has to make sure they can trust what it says. You’ll help make that happen." Thus we can create:

      About the role

      Customer success is one of the most important functions at Luthor. Our customers are large, highly regulated institutions deploying Luthor into workflows that directly affect what they can say to the public. Making those deployments successful means deeply understanding their business, earning the trust of compliance and marketing teams, and turning Luthor into a product they can’t imagine operating without. This is a very different job from a traditional CSM role.

      Then responsibilities: maybe combine the actionable duties: work directly with founders, front-row seat, help define CS playbook; work with sophisticated customers, build relationships across compliance, legal, marketing, leadership; shape product, understand customers, identify blockers, work with engineering; own outcomes (onboarding, implementation, adoption, expansion, renewal); have real responsibility (build systems, processes, customer relationships that become foundation); work directly with founding team in SF, have ownership over adoption; ensure trust in AI output. We can list each as
    • . Then Skills: list customer empathy,