Senior Technical Success Manager, Strategic - West

We need to output HTML fragment with sections only if real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, scam warning, duplicated lines, navigation, cookie, etc. Must preserve all substantive info. We need to parse the posting: It includes company description, values, DEI statements repeated. The role description: "About The Role & Team" then details. Then responsibilities listed as bullet points under "As a Senior Technical Success Manager, Strategic, You Will". Then "Critical Skills Profile" with bullet points of skills. Then "At a Minimum, You Need To Have" with requirements. Then "Nice To Have". Then "Who We Are" with company description again. Then "Some Of Our Benefit Programs Include" with benefits list. Then "Other Fun Facts About Amplitude" with fun facts. Then DEI again, EEO, fraud warning. We need to produce sections: About the role (maybe combine About The Role & Team). Responsibilities (the bullet list under "You Will"). Requirements (the "At a Minimum, You Need To Have" list). Qualifications? Could combine Requirements and Nice To Have? But we should have sections only if real content. Could have "Requirements" for minimum, "Preferred Qualifications" for nice to have. Skills: we have "Critical Skills Profile" which is a list of skills. Could be "Skills". Benefits: we have benefits list. Pay and Schedule: not mentioned, so omit. Also we might have "About the Company" maybe but not required. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We need to preserve all substantive information. So we need to include the company overview? Not required as a heading but could be included in a paragraph before sections. The instruction: 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. So we can include a brief intro paragraph about the company and role summary. We must remove boilerplate: DEI statements repeated, EEO, fraud warning, "Learn more at amplitude.com" maybe considered boilerplate? It's part of description but could be kept? It's not substantive to the role. Might be considered fluff. Safer to remove generic marketing lines. However we need to preserve ALL substantive information; marketing fluff may be considered not substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can remove duplicated lines like repeated DEI, repeated company description, repeated values. Keep one instance maybe. We need to decide what to keep: The role description includes details about team, responsibilities, skills, minimum requirements, nice-to-have, benefits, fun facts (maybe not needed). Fun facts could be considered company info but not essential to role; could be omitted as not substantive for the role. But instruction says preserve ALL substantive information; fun facts are substantive about company but not required for role? Might be considered fluff. Safer to keep them? Might be okay to include as a paragraph under "About the Company". However we have no heading for About the Company; we could just include a paragraph before sections. We need to avoid filler like "commensurate with experience". Not present. Let's extract substantive content: Company overview: "Amplitude is the leading AI analytics platform, helping over 4,700 customers—including Atlassian, Burger King, NBCUniversal, and Square—build better products and digital experiences. With powerful AI Agents embedded across our platform, teams can analyze, test, and optimize user experiences faster than ever. Ranked #1 across multiple categories in G2’s Winter 2026 Report, Amplitude is the best-in-class solution for product, data, and marketing teams." plus values: "As an organization, we deliver for our customers by living our values. We operate from a place of humility, take ownership of problems and successes, approach challenges with a growth mindset, and put our customers at the center of everything we do." Could keep that. DEI statement: maybe keep one instance: "Amplitude believes that diversity enables the creation of better products, improves the ability to solve complex problems, and drives more powerful solutions. We strive to create an environment of inclusion—one focused on psychological safety, empathy, and human connection—that will allow employees of all backgrounds to thrive." But DEI may be considered boilerplate? It's not legal EEO; it's a value statement. Might be okay to keep. Role & Team: "The Customer Success team is responsible for building relationships with and driving long-term value realization for Amplitude's customers. The Senior Technical Success Manager, Strategic owns customer deployment, adoption, and value realization across Amplitude's digital analytics platform. They bring strong product knowledge and fluency in customer technical ecosystems: data foundations, taxonomy, instrumentation patterns, and AI agent configuration. They are execution-first and outcome-driven from presales through implementation, adoption, renewal, and expansion." Then responsibilities bullet list (starting with "As a Senior Technical Success Manager, Strategic, You Will"): - Own customer deployment, adoption, and outcomes for a portfolio of 10 accounts, from presales through renewal - Lead deployment planning and implementation across your book, e.g.: scoping, deployment plan creation, kickoff meetings, use case alignment, coordination of delivery (e.g. managing internal and partner teams), project reporting - Track and manage risks and issues across active deployments, driving resolution before they impact timelines or outcomes - Monitor portfolio health through AI-augmented signals, engaging proactively to accelerate adoption, drive renewals, and deepen stakeholder engagement - Drive product adoption by running live working sessions, identifying new use cases to expand value over time, and showcasing new platform capabilities with a point of view on how they enable customer growth - Develop and maintain success plans tied to customer goals, tracking milestones and risks from onboarding through renewal - Build and deliver executive business reviews that connect Amplitude usage to measurable business impact, turning adoption into a renewal and expansion story - Partner with Account Executives on renewals and expansion, building the value story, coaching champions, and identifying growth opportunities across your book - Serve as the voice of the customer internally, channeling product feedback, market needs, and customer priorities to shape how Amplitude builds and delivers - Continuously improve how you operate: develop repeatable playbooks, share best practices across the team, and find new ways to drive customer outcomes at scale Critical Skills Profile bullet list: - Business Acumen: Understands each customer's business model, growth levers, and priorities. Builds a path to value that connects Amplitude's platform to the outcomes that matter most to the customer. - Technical Fluency: Comfortable with Amplitude data architecture, instrumentation methods, taxonomy design, and AI agent workflows. Able to unlock use cases and guide internal and partner delivery teams. - Delivery Excellence: Drives deployment and implementation quality across a full book of business. Manages timelines, coordinates internal and partner delivery teams, and ensures every account progresses through milestones on time and to standard. - Ownership of Outcomes Across Portfolio: Responsible for retention across your territory. Ruthlessly prioritizes time, resources, and attention to focus on the accounts and actions that drive the most impact. Accountable for ensuring customers achieve measurable business results from Amplitude, and for connecting customer outcomes to commercial value. - Prescriptive Customer Guidance: Sets the standard for what good looks like at each stage of the customer journey. Drives accountability across deployment and ongoing success. Pushes back on bad implementation patterns, guides customers toward proven approaches, and holds them accountable to their own defined success criteria. - Diagnostic Thinking: Proactively recognizes adoption gaps and technical blockers early and drives creative solutions that get customers back on track. - Curiosity and Self-Sufficiency: Defaults to figuring things out independently. Explores edge cases on your own, and comes to conversations with a point of view. This role requires someone who runs toward ambiguity. - AI Innovation: Embeds AI in day-to-day workflow to improve efficiency and customer outcomes. Experiments, iterates, and shares best practices. Minimum requirements bullet list: - 6+ years of experience in Customer Success, Technical Account Management, or a similar customer-facing role in B2B SaaS - 3+ years of experience specifically leading enterprise software deployments where change management and foundational data governance were core priorities. - 2+ years managing a portfolio of 8-10 Strategic accounts - Experience co-owning renewals and contributing to expansion pipeline alongside a sales counterpart - Experience training or enabling non-technical teams to become data-sufficient. - Excellent communication skills to influence everyone from a data engineer to a C-level executive. - Expert-level project management skills and the ability to thrive in an independent and fast-paced environment. Nice to have bullet list: - Prior experience with digital analytics, product analytics, or adjacent data/experimentation platforms - Background in consulting, solutions delivery, or implementation - Experience using Amplitude as a practitioner Benefits list: - Excellent Medical, Dental and Vision insurance coverages, with 100% employer-paid premiums for employee Medical, Dental, Vision on select plans - Flexible time off, paid holidays, and more - Fidelity 401/K - Generous stipends to spend on what matters most to you, whether that’s wellness (monthly), commuter transit/parking (monthly), learning and development (quarterly), home office equipment (annual), and much more - Excellent Parental benefits including: 12-20 weeks of Paid Parental Leave, Carrot Fertility Benefits/Adoption/Surrogacy support, Back-up Child Care support - Mental health and wellness benefits including no cost employee access to Modern Health coaching & therapy Sessions and high quality physician office experience via One Medical membership (select U.S. locations only) - Employee Stock Purchase Program (ESPP) Other fun facts maybe optional; we could include as a paragraph under "About the Company". But we already have company overview. Might be redundant. Could omit fun facts to avoid duplication. We need to avoid repeating duplicated lines. The company overview appears twice at start and later; we keep one. We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Skills, Benefits. Possibly also "Qualifications" but we have Requirements and Nice To Have; we could combine Requirements as "Requirements" and Nice To Have as "Preferred Qualifications". But instruction list includes Qualifications as a possible heading. We could have "Requirements" for minimum, and "Preferred Qualifications" for nice to have. Or we could have "Requirements" and "Qualifications". Let's follow typical: Requirements = minimum, Qualifications = nice-to-have. But we also have Skills separate. Thus sections:

About the role

(maybe include team description)

Responsibilities

Requirements

Qualifications

(nice-to-have)

Skills

Benefits

We need to ensure we don't create empty sections. Now craft HTML. We'll start with a

intro containing company overview and values and DEI statement maybe. Then

About the role

with paragraph describing team and role overview. Then

Responsibilities

with

• ... each. Then

  Requirements

  with
  • ... Then

    Qualifications

    with
    • ... Then

      Skills

      with
      • ... Then

        Benefits

        with
        • ... Make sure to preserve all details exactly as in text, but we can slightly rephrase? Must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the exact wording? Probably we can