Senior Customer Success Manager

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: About Us (but not required heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings that match those labels if we have content. The posting includes "About Us" (company description) and "About The Role". The "About Us" could be considered "About the role"? No, it's about company. Not in list. We could maybe treat "About Us" as not needed heading; but we need to preserve all substantive information. We could put it under a

without heading? The instruction: Use

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

for section headings (e.g. ...). Likely we should only use those headings when appropriate. For company overview, we could just put a

without heading. Or we could use

About Us

though not in list but maybe acceptable. Safer to follow instruction: only those headings. So we need to map content to those headings. We have: - About the role: we have "About The Role" section. So heading

About the role

with paragraph(s) from that section. - Responsibilities: "What You'll Do" bullet list. So heading

Responsibilities

with

• items. - Requirements: "What Will Help You Succeed" includes Core Skills etc. Could be Requirements. Also "Preferred Qualifications". Could be Qualifications. Also "Growth Opportunities" maybe Skills? Or we could treat "Core Skills" as Skills. But we have headings: Skills, Requirements, Qualifications, Benefits, Pay, Schedule. We need to decide mapping: - Requirements: maybe the core skills (5-8+ years etc.) as requirements. - Qualifications: Preferred Qualifications. - Skills: maybe "Core Skills" also could be Skills but we already used for Requirements. Could treat Core Skills as Skills and Requirements as something else? But we need to avoid duplication. Let's think: The posting has "Core Skills" bullet list, then "Preferred Qualifications" bullet list, then "Growth Opportunities" bullet list (which are more like opportunities). Could map: - Requirements: Core Skills (mandatory) - Qualifications: Preferred Qualifications - Skills: Growth Opportunities? Not exactly skills but could be considered skill development. However instruction says include a section ONLY when posting has real, specific content for it. We have content for Growth Opportunities, so we could make a section maybe not in list but we could still use

  Growth Opportunities

  though not in list. But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. So we can use other headings as needed, but must be

  . So we can add headings for any section we want, as long as we use

  . So we can include headings like "About Us", "What You'll Do", "What Will Help You Succeed", "Preferred Qualifications", "Growth Opportunities", "Why You Might Be Excited About Alembic", "Why You Might Not Be Excited", "Compensation Range". However they said prefer a few substantive sections over many thin ones. So we should consolidate. We need to preserve all substantive information. We can combine similar items. Potential sections: - About the role (already) - Responsibilities (What You'll Do) - Requirements and Qualifications (maybe combine core skills and preferred qualifications into Requirements? But we need to keep both. Could have Requirements (core skills) and Qualifications (preferred). That's two sections. - Skills (maybe Growth Opportunities as skills development) - Pay (Compensation Range) - Benefits? Not mentioned explicitly. No benefits details. So we should not create Benefits section. - Schedule? Not mentioned besides hybrid and regular onsite time. That's schedule info. Could be Schedule section: mention hybrid, regular onsite time at customer sites in Chicago area. So we can include Schedule. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills (maybe Growth Opportunities), Pay, Schedule. We also need to include location/hybrid info maybe in About the role or Schedule. We'll put schedule. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract each. About Us: We need to keep that info somewhere. Could be placed under a heading "About Us" but not required. Since we want to preserve all substantive info, we need to include it. We could put it under a

  About Us

  (allowed as heading). Or we could incorporate into About the role? But that would mix. Better to have separate About Us heading. Thus headings: About Us, About the role, Responsibilities, Requirements, Qualifications, Skills (Growth Opportunities), Pay, Schedule. Now extract each section's content. About Us: Paragraph(s) from "About Us Alembic is the pioneering Causal AI platform..." up to "...one of the fastest private supercomputers in the world." Let's copy that exactly. About Us text: "Alembic is the pioneering Causal AI platform. We help the world's largest enterprises move past correlation to prove what actually drives business outcomes — the question marketing and growth teams have never been able to answer with confidence. Fortune 100 companies including Nvidia, Delta Air Lines, and Mars use Alembic to make multimillion-dollar decisions on trusted, causal evidence. We're backed by a $145M Series B from WndrCo (founded by Jeffrey Katzenberg), Jensen Huang, Joe Montana, Prysm Capital, and Accenture. Our models run on our own NVIDIA DGX SuperPOD built on Grace Blackwell infrastructure — one of the fastest private supercomputers in the world." We need to preserve punctuation. Now About the role: The section "About The Role" paragraph(s). Let's extract: "We're hiring a Senior Customer Success Manager in Chicago to own the technical deployment and integration of the Alembic platform for our enterprise customers. You'll turn sales promises into technical reality: a fully functional system that meets the customer's requirements and sets the foundation for a long relationship. Causal analysis is only as good as the data going into it, so the quality of your implementation directly determines whether a Fortune 100 marketing organization trusts what our models tell them. Time-to-value is the number that matters, and you'll own it. The seat is in Chicago because a concentration of our most strategic enterprise accounts is here. Kickoffs, data workshops, and go-live moments go materially better in person, and you'll be close enough to do them that way." Now Responsibilities: "What You'll Do" bullet list. Let's extract each bullet: - Lead implementation projects for enterprise B2B SaaS customers, ensuring smooth onboarding and successful adoption of Alembic's platform. - Develop and maintain implementation plans, timelines, and resourcing so projects land on or ahead of schedule. - Ensure data integrations function correctly and meet customer requirements — the integrity of every downstream causal result depends on it. - Create documentation comprehensive enough to enable real knowledge transfer, internally and to the customer. - Act as the liaison between customer success, engineering, and product management to keep everyone aligned and moving. - Build scalable, repeatable processes that cut time-to-value for every new customer after this one. - Run regular check-ins with clients to surface concerns and clear roadblocks before they become escalations. - Monitor and report on implementation metrics and KPIs, and facilitate clean handoffs from implementation to ongoing customer success. We need to keep the em dash? It's fine. Now Requirements: "What Will Help You Succeed" includes Core Skills bullet list. Let's extract those bullets: - 5–8+ years in enterprise implementation, technical account management, solutions consulting, or technical customer success at a B2B SaaS, data, cloud, or AI company. - A track record owning enterprise onboarding end to end — from kickoff through go-live — with named references you're proud of. - Real comfort with data integration mechanics: APIs, ETL/ELT pipelines, cloud warehouses (Snowflake, BigQuery, Redshift), file-based transfer, and troubleshooting a broken feed without escalating on day one. - SQL fluency; Python or scripting is a plus. - Project management discipline — you can hold a multi-workstream plan and a skeptical executive stakeholder at the same time. - Clear written and verbal communication with both engineers and C-level stakeholders. Now Qualifications: "Preferred Qualifications" bullet list: - Experience with marketing and advertising data — CRM, marketing automation, ad platforms, ad servers, DSPs, web and app analytics, or media spend files. - Knowing why a media taxonomy is never clean is a genuine advantage here. - Background at a martech, measurement, or analytics vendor, or inside a large advertiser's or agency's data function. - Familiarity with enterprise procurement, security review, and data governance processes. - Startup or high-growth experience where you built the process rather than inherited it. - Experience mentoring or setting standards for other implementation staff. Now Skills: "Growth Opportunities" bullet list: - Implementation methodology: Develop and refine the methodology that drives faster time-to-value across all of our enterprise clients. - Cross-functional leadership: Become a key connector between customer success and product development, with real influence on what gets built. - Process optimization: Design the approaches that streamline implementation and raise customer satisfaction — and own them as we scale. Now Pay: "Compensation Range: $170K - $190K". We'll put that. Now Schedule: The location/hybrid info: "Location: Chicago, IL — Hybrid, with regular onsite time at customer sites in the Chicago area". Also mention about seat in Chicago etc. Already in About the role. But schedule section can capture hybrid and regular onsite time. We should avoid duplicating. We'll put schedule section with that sentence. Now we need to output HTML fragment only, no markdown fences. We'll structure:

  About Us

  ...

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Pay

  Compensation Range: $170K - $190K

  Schedule

  Location: Chicago, IL — Hybrid, with regular onsite time at customer sites in the Chicago area

  Check for any other substantive info: The "Why You Might Be Excited About Alembic" and "Why You Might Not Be Excited" sections contain substantive info but maybe considered fluff? They are reasons to be excited/not excited. They are substantive. Should we include? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include those as well. However we already have many sections; adding more may be many thin ones. But we could combine them into a section like "Why Alembic" or keep them as separate? The instruction says prefer a few substantive sections over many thin ones. So we should try to consolidate.