Sr. Director, Value Creation Insights

We need to output HTML fragment with sections only where there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes sections: "What You'll Do" (role description), "What Your Responsibilities Will Be" (list of responsibilities), "What Success Looks Like" (maybe not a standard heading; could be part of responsibilities or maybe we can treat as part of responsibilities? The instruction: include a section ONLY when posting has real, specific content for it. We have content for responsibilities, qualifications, maybe benefits (they mention total rewards, health & wellness benefits, inclusive culture). Pay not specified (just "great compensation package" but no specifics). Schedule not mentioned. So we should not create Pay or Schedule sections. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "What You'll Do" which is about the role. So we can map that to About the role. Responsibilities: "What Your Responsibilities Will Be" with bullet points. Qualifications: "What You’ll Need To Be Successful" includes qualifications list. Skills: maybe we can extract skills from qualifications? But we could also create a Skills section if there is specific skill content. The qualifications list includes many skills: Snowflake, SQL, dbt, etc. Could put them under Skills. But we need to avoid duplication. Perhaps we put Qualifications heading for the list of qualifications (experience, etc.) and Skills heading for technical skills. However instruction: Prefer a few substantive sections over many thin ones. Might combine qualifications and skills into one Qualifications section. But we have to use allowed headings; we can omit Skills if not needed. The instruction: Use headings only when posting has real, specific content for it. So we can include About the role, Responsibilities, Qualifications, Benefits. Possibly also "What Success Looks Like" could be part of Responsibilities or maybe we could add a section "Success Metrics" but not in allowed headings. So we ignore. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from each section. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement etc. Remove that. We need to output only HTML fragment. Let's extract content. About the role: The paragraph starting "What You'll Do The Sr. Director, Value Creation Insights leads the analytics and insights function..." We'll keep that as prose

. Responsibilities: There's a list under "What Your Responsibilities Will Be" with headings: Revenue & Forecasting Analytics, Predictive Modeling & Scoring, Data Infrastructure & Governance, AI-Enabled Analytics & Platform Modernization, Stakeholder Partnership & Executive Communication, Team Leadership & Development, Strategic Initiatives. Each has bullet-like sentences. We need to use

• for any list of duties/requirements/benefits. So we can create a
  with each responsibility as
  • . Inside each
  • we can keep the prose (maybe multiple sentences). That's fine. Qualifications: Under "What You’ll Need To Be Successful Qualifications" then a list of bullet points (starting with "10+ years of experience..."). We'll make a
    • for each. Benefits: Under "How We’ll Take Care Of You Total Rewards" etc. There's description: "Total Rewards In addition to a great compensation package, paid time off, and paid parental leave, many Avalara employees are eligible for bonuses. Health & Wellness Benefits vary by location but generally include private medical, life, and disability insurance. Inclusive culture and diversity Avalara strongly supports diversity, equity, and inclusion, and is committed to integrating them into our business practices and our organizational culture. We also have a total of 8 employee-run resource groups, each with senior leadership and exec sponsorship." We'll make a Benefits section with
      • for each benefit? Could be separate items: great compensation package, paid time off, paid parental leave, bonuses eligibility, private medical, life, disability insurance, inclusive culture, 8 employee-run resource groups. We'll keep as list. We must not include Pay or Schedule sections. We must not repeat job title as heading. We must not include Job ID etc. Now produce HTML:

        About the role

        ...

        Responsibilities

        • Revenue & Forecasting Analytics: Own the design and maintenance of Avalara's revenue forecasting models, including providing feedback on policy and revenue recognition; Lead development and governance of the demand generation reporting platform, which will serve as the company's primary source of truth for funnel performance including opportunity stage tracking, TOFU metrics, and marketing pipeline KPIs; Partner with FP&A on forecast methodology, variance analysis, and reconciliation; Drive identification and resolution of forecast discrepancies, including being the driver of discovery and remediation of any assumption misses.
        • Predictive Modeling & Scoring: Lead the design and ongoing evolution of Avalara's prospect and customer scoring ecosystem, including product fit scores (A–D grade), propensity-to-buy models, ICP scoring, and customer health metrics; Own the alignment process across GTM stakeholders to define model success metrics, validate predictive performance, and ensure score adoption by Marketing, Sales Development, and Sales; Drive operationalization of scoring tools by ensuring models are not only built but actively embedded into sales workflows, SDR outreach, prospect targeting, and account prioritization.
        • Data Infrastructure & Governance: Oversee the team's analytics engineering function, including Fivetran-based ingestion, dbt model development, Snowflake schema design, and data pipeline quality for commercial datasets; Own the integration and governance of third-party data sources including ZoomInfo, Cognism, D&B, and Clay; Manage Snowflake data access, permissions, and ingestion pipelines for commercial data domains (Salesforce, Gong, Google Ads, AvaTax, Marketo, and more); Partner with the Data Platform Engineering team on infrastructure decisions, the migration off legacy Hex / Power BI reporting onto Omni Analytics, and capacity planning; Own governance of core metric definitions and calculation logic (e.g., funnel stages, scoring inputs, forecast components) that feed into company-wide KPIs, ensuring consistency between this team's models and the definitions maintained centrally by GAI.
        • AI-Enabled Analytics & Platform Modernization: Own and drive the AI roadmap for the team's analytical domains (forecasting, scoring, GTM/commercial analytics), defining where LLM-powered insight generation, conversational analytics, and agentic workflows create real business leverage; Lead the team's transition from traditional dashboard-based BI (Hex, Power BI) to Omni Analytics as the semantic layer and conversational analytics interface, including model/metric layer design so that natural-language querying returns governed, trustworthy answers; Design and ship AI agents embedded directly into GTM, Finance, and Sales workflows (e.g., automated deal/account insights, forecast variance flags, scoring explainability) rather than standalone reporting, with clear ownership of accuracy, guardrails, and adoption; Evaluate build-vs-buy tradeoffs for AI/LLM tooling, balancing speed, cost, data security, and long-term flexibility, and bring recommendations to the VP with a clear point of view.
        • Stakeholder Partnership & Executive Communication: Serve as the analytics partner to senior leadership across Revenue Operations, Marketing, Sales, and Finance, translating complex analytical outputs into clear, actionable narratives; Drive cross-functional alignment on key company metrics including OKR definitions, MBO criteria, and performance measurement frameworks; Present analytical findings, forecast updates, and strategic recommendations directly to VP and C-suite stakeholders; Build and maintain a formal operating model with FP&A that ensures a single source of analytical truth reaches executive leadership.
        • Team Leadership & Development: Lead and develop a team of roughly 30, including direct reports at the analyst to principal analyst level plus analytics engineers, across prospect analytics, value creation, marketing analytics, financial insights, and AI-enabled analytics, spanning onshore and offshore locations; Build and manage a globally distributed team model, including offshore hiring, onboarding, and time-zone-aware working norms that keep quality, security, and stakeholder responsiveness consistent regardless of location; Own performance management, goal setting, and career development for team members; Establish team prioritization processes, sprint cadences, and stakeholder intake workflows; Set technical and analytical standards for the team, including coding practices, modeling methodology, documentation, and reproducibility.
        • Strategic Initiatives: Identify and drive high-priority analytical initiatives proactively by not simply responding to requests, but surfacing opportunities where data can create business value and taking ownership of moving those opportunities to action; Lead complex, organization-wide data transitions and knowledge transfers while protecting business partner continuity; Represent the team's AI-enabled analytics work in company-wide AI and automation forums, and bring back emerging tooling, patterns, and risks relevant to the team's roadmap.

        Qualifications

        • 10+ years of experience in analytics, data science, or data engineering, with at least 4 years in a people management role
        • Deep expertise in Snowflake, SQL, dbt, and modern data stack tooling; experience with Omni, Power BI, Hex, or similar BI/semantic-layer platforms
        • Hands-on experience with LLM-powered / conversational analytics tools and building AI agents or automated workflows on top of a governed data model (vs. one-off prompting); able to distinguish genuine analytical leverage from AI novelty
        • Experience building and managing distributed teams that blend onshore and offshore talent across time zones, with a track record of sustaining quality, security, and stakeholder trust at that scale
        • Strong command of statistical modeling, predictive analytics, and machine learning concepts applied to commercial use cases
        • Proven ability to work with and influence senior stakeholders across multiple functions
        • Experience owning complex, multi-stakeholder analytical initiatives from problem framing through to business adoption
        • Exceptional communication skills with strong ability to translate technical output into executive-ready narratives
        • SaaS business model fluency, including ARR, GRR, NRR, bookings, revenue recognition, and GTM funnel mechanics
        • Experience with Salesforce data, marketing automation platforms, and CRM analytics a strong plus

        Benefits

        • Great compensation package
        • Paid time off
        • Paid parental leave
        • Eligibility for bonuses
        • Private medical insurance
        • Life insurance
        • Disability insurance
        • Inclusive culture and diversity commitment
        • Eight employee-run resource groups with senior leadership and exec sponsorship
        We need to ensure we didn't include any boilerplate like "Avalara is an AI-first Company" etc. That content is under "How We’ll Take Care Of You" maybe considered part of benefits? Actually that paragraph about AI-first is more about culture; we could include it under Benefits or maybe as a separate section? Not in allowed headings. Could incorporate into Benefits as a bullet: "AI-first culture with AI embedded in workflows, decision-making, and products". But the instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that info somewhere. Where? Could be under Benefits as a bullet about AI-first culture. Or we could add a section "About the company" but not allowed heading. So we add to Benefits. Also there is "What You Need To Know About Avalara" describing the company mission etc. That's substantive. Should we include? It's about the company, not role-specific but still substantive. Could be placed under Benefits or maybe a separate section "About the company" but not allowed heading. We could incorporate into Benefits as well