Jobs · Consulting · Texas

Director, Marketing & Data Science

Material · Austin, Texas Metropolitan Area · 1 mo ago
HybridConsulting$145k–$170k/yrFull-time
We need to output HTML fragment with sections: About Us, About The Director, Marketing & Data Science Role (maybe heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have sections: About Us (maybe not required but we can include as a heading? The instruction says use those headings for sections; but we can include other headings if they have content? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow those typical ones. However we have "About Us" content; maybe we can treat as "About the role"? Actually "About Us" is separate from role. The instruction says 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. It doesn't forbid other headings like "About Us". But the examples given are typical sections. Probably we should include headings: About Us, About the role (maybe "About The Director, Marketing & Data Science Role"), Responsibilities (What You'll Do), Requirements (Required), Qualifications (maybe combine with Requirements?), Skills (Nice to Have), Benefits (Why Work for Material?), Pay (Pay Range). Schedule not present, so omit. We must not create sections with filler like "commensurate with experience". We have actual content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points etc. We need to use

  • for any list of duties/requirements/benefits, and

    for prose. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO, Privacy Statement etc. Remove those. Also remove duplicated lines? Not seeing duplicates. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

    About Us

    We drive intelligent growth for ambitious businesses and leading brands. Customer understanding is more potent and drives greater value when insights go to work directly within marketing and experience priorities. To give our clients that advantage, we put an insights-driven operating system at the core of our design, go-to-market, and digital experience solutions. Material clients make smarter growth choices because they can see clearly how and when to take the shots that count. Together, we connect consumer intelligence with customer demand generation to build lasting, profitable relationships.

    About the Director, Marketing & Data Science Role

    Material is seeking a Director for the Marketing & Data Science team who is passionate about using data science to solve complex marketing and customer problems. This role sits at the intersection of advanced analytics, market research, customer data, and business strategy. You will lead engagements that bring together consumer surveys, first-party CRM and CDP data, transactional data, and digital behavior to help clients make better decisions and drive measurable growth. You lead by doing: shaping the analytical approach, guiding your team through execution, and translating model outputs into clear stories for senior, non-technical audiences. You are curious about human behavior, rigorous about methodology, and practical about how AI can accelerate the work without replacing the judgment.

    Now responsibilities: "What You'll Do" with subsections: AI & Behavioral Analytics Leadership, Client & Strategic Leadership, Team Leadership. Each has bullet points. We can make a

    Responsibilities

    then
    • each bullet. But we have subheadings inside; maybe we can keep subheadings as

      ? Not allowed? Only h3 for section headings; but we could still use

      for sub-sub? Not prohibited. Safer to keep as

      Responsibilities

      and then list all bullets under that, maybe grouping with headings inside
    • ? But we need to preserve structure. Could do

      Responsibilities

      • AI & Behavioral Analytics Leadership: ... then sub-bullets? Might be messy. Alternative: Keep subheadings as

        as well, but then we would have many sections. 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 we should prefer those. However we can still use

        for each major section: AI & Behavioral Analytics Leadership, Client & Strategic Leadership, Team Leadership. That might be okay. But we also need Requirements, Qualifications, Skills, Benefits, Pay sections. Let's map: - Responsibilities: Could be split into three subsections as above. - Requirements: "Required" bullet list. - Qualifications: maybe "Bachelor's degree..." etc. Could be part of Requirements; but we can separate. - Skills: "Nice to Have" list. - Benefits: "Why Work for Material?" paragraph. - Pay: "Pay Range: $145,000.00- 170,000.00" plus note. We'll not include Schedule. Now we need to ensure we don't include boilerplate: EEO, Privacy Statement etc. Let's extract content. About Us paragraph already captured. About the role paragraph captured. Now Responsibilities: AI & Behavioral Analytics Leadership: - Apply AI and machine learning - including LLMs and generative techniques - to accelerate segmentation, synthetic data generation, qualitative-to-quantitative synthesis, and automated insight generation. - Design and execute behavioral analytics engagements: clickstream analysis, passive behavioral data, digital journey mapping, engagement modeling, propensity and churn prediction, and customer lifetime value. - Integrate behavioral signals - from CRM, CDP, digital, transactional, and survey sources - into unified analytical frameworks that reflect how customers actually make decisions. - Lead technical execution in Python or R across the full modeling lifecycle: feature engineering, model selection, validation, interpretation, and deployment planning. - Stay current on advances in AI, machine learning, and behavioral science - identifying what's practically useful for clients versus what's hype. Client & Strategic Leadership: - Own the analytical workstream end-to-end: converting business questions into clear analytic plans, timelines, and decision-ready outputs. - Deliver executive-ready narratives that connect behavioral findings to marketing actions and measurable business outcomes. - Serve as a trusted subject matter expert - explaining complex methods, defending recommendations, and redirecting analyses that won't answer the underlying question. - Partner across research, strategy, technology, and data engineering to build solutions that can be activated in client environments. - Support business development by shaping analytical approaches, scoping work, and contributing to proposals. Team Leadership: - Lead and mentor a pod of analysts and data scientists, providing direction, code review, and opportunities for technical and professional growth. - Review analytical plans, model outputs, and client deliverables; catch risks early and help teams troubleshoot. - Contribute to practice growth through knowledge sharing, capability development, and methodological innovation. Now Requirements (Required): - 7–10+ years in data science, marketing analytics, or quantitative research - agency, consulting, or in-house. - Solid grounding in model validation, data quality, and the practical tradeoffs of applying analytics to real business decisions. - Working knowledge of SQL and cloud data environments (Snowflake, BigQuery, AWS). - Bachelor's degree in statistics, data science, economics, computer science, or a related quantitative field; advanced degree preferred. Qualifications: maybe we could treat the degree as qualification; but we already included. Could separate: "Bachelor's degree..." as Qualifications. But we have already included in Required. To avoid duplication, maybe we keep Required as experience and skills, and Qualifications as education. Let's split: Required (experience): - 7–10+ years in data science, marketing analytics, or quantitative research - agency, consulting, or in-house. - Solid grounding in model validation, data quality, and the practical tradeoffs of applying analytics to real business decisions. - Working knowledge of SQL and cloud data environments (Snowflake, BigQuery, AWS). Qualifications (education): - Bachelor's degree in statistics, data science, economics, computer science, or a related quantitative field; advanced degree preferred. Skills (Nice to Have): - Experience operationalizing models in CRM, CDP, or marketing automation platforms (Salesforce, HubSpot, mParticle, Braze, or similar). - Familiarity with passive behavioral or digital measurement data providers. - Experience designing agile test-and-learn programs and measuring incremental impact. - BI/visualization tools: Tableau, Power BI, or Looker Studio. Benefits (Why Work for Material?): Paragraph: "Material is a global company and we work with leading brands worldwide. We create and launch new brands and products, putting innovation and value creation at the center of our practice. Our clients are leaders in their class, across sectors from technology to retail, transportation, finance, and healthcare. Material employees join a peer group of exceptionally talented colleagues across the company, the country, and the world. We develop capabilities and leading-edge market offerings across seven global practices including strategy and insights, design, data & analytics, technology, and tracking. A community focused on learning and making an impact. Material is an outcomes-focused company. We create experiences that matter, create new value, and make a difference in our clients’ lives and their customers’ lives." We need to preserve line breaks? Use

        maybe multiple paragraphs. Pay: "Pay Range: $145,000.00- 170,000.00 The range shown represents a grouping of relevant ranges currently in use at Material. Actual range for this position may differ, depending on location and specific skillset required for the work itself." We'll put that in

        . Now ensure we don't include any boilerplate like "Equal Employment Opportunity..." etc. Now produce HTML:

        About Us

        ...

        About the Director, Marketing & Data Science Role

        ...

        AI & Behavioral Analytics Leadership

        • Apply AI and machine learning - including LLMs and generative techniques - to accelerate segmentation, synthetic data generation, qualitative-to-quantitative synthesis, and automated insight generation.
        • Design and execute behavioral analytics engagements: clickstream analysis, passive behavioral data, digital journey mapping, engagement modeling, propensity and churn prediction, and customer lifetime value.
        • Integrate behavioral signals - from CRM, CDP, digital, transactional, and survey sources - into unified analytical frameworks that reflect how customers actually make decisions.
        • Lead technical execution in Python or R across the full modeling lifecycle: feature engineering, model selection, validation, interpretation, and deployment planning.
        • Stay current on advances in AI, machine learning, and behavioral science - identifying what's practically useful for clients versus what's hype.

        Client & Strategic Leadership

          ...

        Team Leadership

          ...

        Required

          ...

        Qualifications

          ...

        Skills

          ...

        Benefits

        ...

        Pay

        ...

        Check that we didn't miss any content: The location hybrid mention: "This role is to be based near one of our offices in Los Angeles, New York City or Austin. (Hybrid)" This is minor metadata; we could fold into a short

        maybe under About the role? The instruction says fold minor metadata into a short

        or drop it. We could include a short paragraph after About the

Similar jobs