Jobs · Engineering · Texas

Senior Technical Success Manager, Emerging Enterprise - East/Central

Amplitude · Texas, United States · 1 mo ago
HybridEngineering$194k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. Let's extract relevant content. First paragraph: "Amplitude is the leading AI analytics platform..." That's company description, not needed? Probably not part of role specifics. Could be omitted as boilerplate? It's generic company description, not role-specific. Might be considered boilerplate but it's about company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview maybe not required but could be considered not needed. However we need to preserve ALL substantive information; do not invent or summarize away detail. The company overview is substantive about the company but not about the role. The instruction says we should output only sections relevant to role. The company description may be considered not needed for role sections. It might be okay to omit as it's not role-specific. However we need to be careful: The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit company description, are we losing substantive info? It's about the company, not the role. The role posting includes that as intro. But the instruction about sections: we only output sections when posting has real specific content for it. The company description is not a section heading like About the role etc. It could be placed in a

before sections? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have extra

outside sections. But they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose." So we can have prose paragraphs outside sections? Probably they expect sections only. But we could include a brief intro paragraph before sections if it's substantive. However they said "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 have

    for metadata. Thus we could include a short

    summarizing company description? Might be considered minor metadata? It's not minor; it's descriptive. But maybe we can keep it as a

    before sections. Nevertheless, the main content: About The Role & Team section includes description of role and team. That maps to "About the role". We'll put that in

    About the role

    with

    content. Then responsibilities: The bullet list under "As a Senior Technical Success Manager, Strategic, You Will ..." includes many duties. That's responsibilities. Then requirements: The "At a Minimum, You Need To Have" list. Then qualifications? Could be same as requirements? Might combine. But we have "Critical Skills Profile" which lists skills. That could be Skills section. Also "Nice To Have" could be Qualifications? Or maybe we treat as Qualifications (preferred). The instruction: Use sections only when posting has real specific content. So we can have About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Qualifications maybe not needed if we have Requirements and Skills. Benefits: There's a list under "Some Of Our Benefit Programs Include". That's benefits. Pay: There's NYC salary range: "$194,000 - $291,000 total target cash (inclusive of bonus or commission)". That's pay. Schedule: Not mentioned. No schedule info. So we should not include Schedule section. Also there is "We were recognized..." etc. That's company fun facts, maybe not needed. Could be omitted as boilerplate? It's not role-specific. Might be considered extra but could be omitted. We need to ensure we don't include duplicated lines. Also remove EEO, scam warning, etc. Let's extract exact text for each section. About the role: The section "About The Role & Team" includes: "Amplitude is the leading AI-first digital analytics platform that helped over 4,000 customers build better products and digital experiences. Our customer base includes Atlassian, Burger King, NBCUniversal, Square, and Under Armour. 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 Fall 2025 Report, Amplitude is the best-in-class solution for product, data, and marketing teams. Learn more at amplitude.com. 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. 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, Emerging Enterprise 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." We need to preserve all that. Might be long but okay. Responsibilities: The list after "As a Senior Technical Success Manager, Strategic, You Will" includes many items each starting with a verb. Let's capture them as bullet points. List: - Own customer deployment, adoption, and outcomes for a portfolio of 40-50 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 We need to ensure we keep the exact phrasing. Requirements: "At a Minimum, You Need To Have" list: - 5+ 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. We should keep each as

  • . Skills: "Critical Skills Profile" includes bullet points each with a bold heading and description. We need to preserve the content. Could format as
    • 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.
    • etc. 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. We'll keep those. Benefits: Under "Some Of Our Benefit Programs Include". The list includes: - 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) We need to keep as bullet list. Pay: NYC salary range: "$194,000 - $291,000 total target cash (inclusive of bonus or commission)". Also note "This role is eligible for equity, benefits and other forms of compensation." Could include that as part of pay? Might be separate but we can include in Pay section. Schedule: none. We also might include a short

      for metadata like "Based on legislation in New York City, the following details are for individuals who will work for Amplitude in New York City." That's minor metadata; we can fold into Pay section as a preamble. We must not include duplicated lines. Ensure we don't repeat the company description twice. Now produce HTML. Structure:

      About the role

      ... (the about role text)

      Responsibilities

      • ... each

      Requirements

      • ... each

      Skills

      • ...

Similar jobs