Senior Customer Success Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Cyvl" then "THE ROLE" then "What You'll Do", "What You Bring", "NICE TO HAVE", "WHY CYVL", "What We Ask", "Benefits", "OUR VALUES", "SEE OUR WORK", "Compensation Range". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we must only include sections when posting has real specific content. We need to map content to appropriate headings. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? Probably we should use those headings where applicable. For example "About the role" could correspond to description of role. "Responsibilities" for What You'll Do. "Requirements" for What You Bring (maybe plus Nice to Have?). "Qualifications" maybe similar. "Skills" maybe for specific skills. "Benefits" for Benefits. "Pay" for Compensation Range. "Schedule" maybe not present; we should not include if not present. Also we need to avoid repeating job title as heading. Also we should not include Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. So we need to extract substantive paragraphs and lists. We need to output only HTML fragment, no /, no markdown fences. We need to use

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

  for prose. We need to decide which sections to include. Let's parse the posting: - About Cyvl: description of company. Could be "About the role"? Actually "About the role" is about the role, not company. But we have "About Cyvl". 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, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. But we could also include "About Cyvl" as a section? Not in list. Might be considered not needed. However we need to preserve ALL substantive information. If we omit About Cyvl, we lose info. But maybe we can incorporate that into "About the role"? Not exactly. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but they gave examples. Probably they want us to map content to those standard headings. However "About Cyvl" is about the company, not the role. Could be considered "About the role"? Not really. But maybe we can treat "About Cyvl" as "About the role"? That seems odd. Better to include a section "About the company" maybe not allowed. But we could embed that info in a

  before sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid other headings besides those examples. It said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings for sections. But we could also have other headings if needed? The examples are just examples; they didn't say exclusively those. However to be safe, we could map: - About Cyvl -> maybe "About the role"? Not accurate but could be considered overview. But we could also add a section "About Cyvl" as

  About Cyvl

  . That is still a heading; not in examples but still a heading. The instruction didn't forbid other headings; it just gave examples. I'd include it. But we need to avoid filler headings. So we will include sections where there is real content. Let's list substantive sections: 1. About Cyvl (company description) 2. The Role (overview) - maybe "About the role" 3. What You'll Do (Responsibilities) 4. What You Bring (Requirements/Qualifications) 5. NICE TO HAVE (maybe "Preferred Qualifications" or "Skills") 6. WHY CYVL (maybe "About the company" or "Culture") 7. What We Ask (maybe "Work Expectations" or "Location/Travel") 8. Benefits 9. OUR VALUES (maybe "Culture") 10. SEE OUR WORK (maybe "Impact" or "Case Studies") 11. Compensation Range (Pay) We need to avoid duplication. Also we need to remove boilerplate like EEO, legal, etc. Not present. We need to preserve all substantive information: So we need to include all paragraphs and bullet points. Let's extract content: About Cyvl paragraph: "The best infrastructure is invisible. You only notice it when it fails. For decades, the people responsible for our roads, bridges and sidewalks have been asked to manage the physical world with tools that can't see it. Cyvl is the Physical AI company changing that. We build purpose-built sensors, computer vision and AI that turn every drive into current data: what exists, where it is and what condition it's in. 500+ cities and towns use our Infrastructure Intelligence Platform to direct the work and fix problems before they fail. 1 in 30 Americans drive on roads managed with Cyvl data. The proof isn't a dashboard. It's a smoother commute, a safer walk to school and public dollars going where they matter most. We're a fast-moving team in Boston building hardware, software and AI for the real world. If you believe technology's highest calling is public good, come build with us." THE ROLE heading: "As our Senior Customer Success Manager, you'll own the full customer lifecycle for our most complex strategic accounts, from onboarding through renewal, and play a direct role in how they achieve measurable outcomes with our platform. You've owned renewals end to end and know what it takes to build the processes and playbooks that help a CS team scale. Here, you're not just following the playbook, you're helping write it. This role is based in Somerville, MA, or remote from San Francisco, CA." What You'll Do (list): - Own a portfolio of enterprise and strategic accounts as their trusted advisor through onboarding, adoption, expansion, and renewal. - Work with key stakeholders to define success metrics, track progress, and show the impact Cyvl delivers against their goals. - Own renewals from start to finish, from early forecasting and multi-stakeholder alignment through negotiation and close, and grow expansion across your book. - Deliver hands-on training, strategic business reviews, and in-person engagements that deepen relationships and drive advocacy. - Build and refine CS processes and playbooks, and partner with Product, Marketing, and Data Ops on discovery, case studies, and customer events. What You Bring (list): - 5+ years of Customer Success experience, including owning complex enterprise or strategic customer relationships - Ownership of the full renewal process, including forecasting, negotiation, and close - Experience building CS processes and playbooks in an early-stage or scaling environment - A track record leading strategic customer moments: onboarding, QBRs, and renewal cycles - A strong analytical mindset; you use data to spot trends, measure impact, and uncover expansion - An AI-first approach; you use AI tools to work more efficiently and maximize high-impact customer time - Exceptional communication in writing, on a call, and in the room - Ability to travel for customer meetings (~25%) NICE TO HAVE (list): - Experience with local governments, municipalities, or public sector organizations of varying sizes - Familiarity with infrastructure, field operations, or GIS-adjacent technology WHY CYVL (paragraphs): - "Hard tech. Real streets. Your name on it." - "Hard problems in the real world. You build end-to-end: our own hardware, software and AI, with work that shows up on the street in the real world." - "Ownership that compounds. You own outcomes, not tasks. You work directly with customers and across our team, and you'll own more, sooner, than almost anywhere else." - "Intense, with heart. We're building a category, so it's not a place to coast. We also take care of each other, have genuine fun together, and believe in what we are doing." What We Ask (paragraphs): - "Cross lanes. 'Not my job' doesn't exist here." - "Own without a playbook. The plan is still being written, often by you." - "Try, miss, try again. We make big bets. Some won't land, and we learn fast." - "Be in the room. We're on-site in Somerville about 90% of the time. If you're based in San Francisco, this role is remote, and you'll be with the team in Somerville for the moments that matter like onboarding, kick-offs, and milestones." - "We're a startup building a category. If that sounds like the draw, not the risk, we'd love to talk." Benefits (list): - Equity. You'll own a piece of what you're building. - Health, dental, and vision. Cyvl covers most of the premium for you and your family. - 401k with a real match, vested day one. Your money is yours from the start. - Generous PTO & Paid Parental leave. Doing hard work well includes stepping away from it. - Learning stipend. Spend it on whatever makes you sharper. - Paid to live close. A monthly bonus for living near our Boston office. - Team events. Time together in Boston with a team you’ll love working with. OUR VALUES (list with descriptions): - Real: Authentic and transparent. Focused on solving real problems with simple, effective solutions. - All Out: Bold, driven, and committed to delivering results that matter. - Accelerating: Always learning, growing, and moving with intention. - Reliable: We follow through and deliver at a consistently high bar. - Empowering: We lift each other up and help governments build infrastructure they can be proud of. SEE OUR WORK (list): - How Atlanta cut downtown potholes by 60% - How Buffalo turned a campaign promise into a paving plan - How to rebuild US infrastructure smarter - "We build for every community, so we hire from all of them. The best people for this work come from different backgrounds, paths, and places, and many of them don't check every box. If this role excites you, apply anyway. If you need an adjustment to our interview process, tell us and we'll make it work." Compensation Range: "$170K - $185K" We need to avoid repeating job title as heading. Not needed. We need to not include Pay/Schedule/Benefits unless posting actually states them. Benefits present, Pay present, Schedule not present (no schedule). So we include Benefits and Pay sections. We need to use

  for section headings. We'll decide which headings to use. Potential headings: - About Cyvl (maybe not in examples but okay) - About the role (could be THE ROLE paragraph) - Responsibilities (What You'll Do) - Requirements (What You Bring) - Skills (NICE TO HAVE maybe) - Benefits - Pay (Compensation Range) - Culture/Values (WHY CYVL, OUR VALUES, SEE OUR WORK, What We Ask) maybe combine? But we need to avoid thin sections. Could combine WHY CYVL, What We Ask, OUR VALUES, SE