Sr. Client Director

We need to output HTML fragment with sections: About the role? The posting includes "Who We Are", "What We Are Looking For", "YOUR DAY TO DAY", "What You Bring To Tealium", "Wage Transparency", "Benefits", "Compensation Range", "WHY YOU WANT TO WORK HERE". Also maybe "Team Tealium" etc. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The instructions: 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. 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on actual content. We have: - Who We Are: description of company. Could be "About the role"? Actually "About the role" is typical but we have "Who We Are". Could map to "About the role"? 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 can also use other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests we should use those headings when appropriate. If content doesn't match, maybe we still use those headings but adapt? Probably we should map content to those headings: About the role (company overview), Responsibilities (day-to-day), Requirements/Qualifications/Skills (what you bring), Benefits, Pay (compensation range), Schedule (maybe remote? but schedule not given). We shouldn't create Schedule if not present. Thus sections: - About the role: Who We Are + maybe also "What We Are Looking For"? Actually "What We Are Looking For" describes the role. Could be part of About the role or Responsibilities. But we need to avoid thin sections. Perhaps combine. Better: Use sections:

  About the role

  - include Who We Are and What We Are Looking For (role description).

  Responsibilities

  - YOUR DAY TO DAY bullet list.

  Qualifications

  - What You Bring To Tealium (requirements/skills).

  Benefits

  - Benefits description.

  Pay

  - Compensation Range. We should not include Schedule as not provided. We must use
  • for any list of duties/requirements/benefits. So for responsibilities list, we need
    • . For qualifications list maybe also list. For benefits list also list. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all points from each section. Let's extract content. Who We Are: paragraphs about Tealium being leader in CDP, etc. We'll keep as prose. What We Are Looking For: description of Sr. Client Director role: results-driven, own commercial strategy, retention, growth, etc. We'll include as prose under About the role maybe. Responsibilities (YOUR DAY TO DAY): bullet list of items: - Own the commercial strategy and account plan for a portfolio of enterprise customers, with accountability for retention, expansion, and overall account growth. - Build and maintain a healthy expansion pipeline by identifying whitespace, uncovering new business initiatives and use cases, and proactively creating opportunities across the Tealium platform. - Develop and maintain multi-threaded relationships across customer organizations, building strong partnerships with key stakeholders, economic buyers, and executive decision-makers. - Lead renewal and expansion strategies from opportunity identification through negotiation and contract execution, with a focus on protecting recurring revenue and growing customer investment in Tealium. - Build compelling business cases and expansion proposals that connect customer priorities and business outcomes to Tealium’s capabilities, demonstrating measurable value and ROI. - Partner with Solutions Consulting, Professional Services, Support, Product, and Marketing to drive successful customer outcomes, accelerate adoption, and identify opportunities for additional growth. - Leverage product usage, customer health signals, account intelligence, and AI-enabled tools to identify whitespace, prioritize opportunities, mitigate churn and downsell risk, and inform account strategy. - Maintain disciplined pipeline management and forecasting, providing accurate visibility into renewals, expansion opportunities, risks, next steps, and expected outcomes. - Continuously identify opportunities to expand Tealium’s strategic footprint by introducing new products, capabilities, and use cases aligned with each customer’s evolving business priorities. We'll put each as
    • . Qualifications (What You Bring To Tealium): list of bullet points: - 7+ years in customer-facing roles (Solutions Consulting, Account Executive, Customer Success, Technical Account Manager) within SaaS, Customer Data Infrastructure, Customer Data Platforms (CDP), Tag Management, Data Clouds, or Digital Marketing ecosystems. - Proven ability to establish credibility with decision-makers and construct data-driven business cases that align complex technology solutions with client goals. - Exceptional cross-functional collaboration skills with a track record of aligning internal stakeholders, including Sales, Operations, Legal, and Finance, to streamline deal execution. - Project and program management capability, with experience coordinating complex, cross-functional customer initiatives, managing dependencies, risks, timelines, and stakeholders to drive clear accountability and successful delivery. - Technical fluency and agility, with the ability to quickly translate complex data architecture concepts into clear, value-oriented business impact for non-technical stakeholders. - Modern operational mindset, leveraging AI tools and predictive analytics to improve productivity, track health metrics, and make informed strategic account decisions. - Adaptable, resourceful problem-solving approach paired with a commitment to continuous learning in an evolving martech landscape. - Strong negotiation capability combined with transparent, polished communication skills that foster long-term customer trust and alignment. - Ability to support customers across Western U.S. time zones and travel throughout the region as needed; candidates based in the Western U.S. are strongly preferred. We'll put as
      • . Benefits: The paragraph under "Benefits" includes many details: U.S. pay range, base pay may vary, robust benefits package includes: annual bonus and stock options; medical, dental, vision, life, disability insurance; 401k plan with company matching; flexible paid time-off and extended paid parental leave; 11 paid holidays annually with additional Healium Be-Well break; 15 hours of paid work time for volunteer activities; sick leave accrual details (various categories). Also note: "An overview of our benefits and perks can be found on our careers page, https://tealium.com/careers/. Additional details regarding the benefits package will be provided during your interview process." We need to preserve all substantive information. We'll put as
        • each benefit item. Pay: Compensation Range- $120,000 - $150,000 Base + Variable Compensation. Also note "Wage Transparency" paragraph: In many U.S. states, employers are required to include a pay range for posted positions. Although this isn't a requirement in every state, communicating transparently is a cornerstone of our operations at Tealium, and we believe in making this information available to all applicants. Also "The U.S. pay range for this full-time position is listed below, however, base pay offered may vary depending on job-related knowledge, skills, and experience." So we need to include that prose. Thus Pay section: include the wage transparency paragraph and the compensation range. We should not include Schedule. We also have "WHY YOU WANT TO WORK HERE" section with many bullet-like items: Tealium WOWs, Mosaic, Tealium Cares, Tealium Connects, Tealium Ownership, Tealium Time, Healium, Tealium LIFT, Health and Related Benefits Programs, mosaic statement, EEO statement. This is basically culture/benefits/EEO. Some of this may be considered boilerplate EEO etc. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement at the end: "It is our continuing philosophy to recruit and employ the best qualified individuals without regard to race, color, sex, religion, national origin, disability, age, sexual orientation, gender identity, and/or any other protected characteristic. Tealium does not tolerate unlawful discrimination of any kind and strives to be an inclusive and respectful workplace." That's EEO boilerplate; should be removed. Also the earlier part about "Offerings vary by level and location." maybe not needed. The "WHY YOU WANT TO WORK HERE" includes many culture items that could be considered benefits? But we already have Benefits section. Some of those items are benefits like paid time-off, volunteer hours, parental leave, holidays, wellness programs, learning programs, equity grants, remote-first stipend, etc. Those are already covered in Benefits section? Actually Benefits section already listed many: annual bonus, stock options, medical/dental/vision/life/disability, 401k matching, flexible PTO, extended parental leave, 11 paid holidays, Healium Be-Well break, 15 hours volunteer time, sick leave accrual details. The "WHY YOU WANT TO WORK HERE" includes: Tealium WOWs (Ways of Work) culture, Mosaic (DEI), Tealium Cares (volunteer hours), Tealium Connects (remote-first working, new hire stipends), Tealium Ownership (equity grants), Tealium Time (PTO policy), Healium (health and wellness programs), Tealium LIFT (learning programs), Health and Related Benefits Programs (market competitive benefits). Many of these overlap with Benefits section but some are cultural aspects. The instruction says prefer a few substantive sections over many thin ones. We could incorporate those culture points into Benefits section as additional bullet points, or we could create a separate "Culture" section but not in the prescribed headings. However 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 but suggests using those. To be safe, we could incorporate the culture points into Benefits section as additional list items, as they are benefits/perks. That would keep sections few. Thus Benefits section will include all benefits and perks listed: from Benefits paragraph plus the WHY YOU WANT TO WORK HERE items (excluding EEO). We'll need to list them as

          . We must not duplicate lines. Ensure we don't repeat same info. Let's compile Benefits items: From Benefits paragraph: - Annual bonus and stock options. - Medical, dental, vision, life, and disability insurance. - Option to enroll in