Director, Marketing AI & Automation
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.
Thus we need to decide which sections to include based on content.
We have:
- About The Team: description of team and role. Could be "About the team" heading.
- About The Role: Key Responsibilities list (multiple bullet points). Could be "Responsibilities" heading.
- Who you are: qualifications, requirements, skills. Could be "Qualifications" or "Skills" heading.
- Pay: base pay ranges for specific locations, plus equity awards mention. So we can have "Pay" heading with details.
- Benefits: equity awards mentioned, maybe also mention "competitive base salary" and "eligible for equity awards". Could be "Benefits" heading.
- Schedule: Remote position description. Could be "Schedule" heading.
We must not include sections with filler. All these have real content.
We must not repeat job title. Not include Job ID.
We must remove boilerplate like EEO, legal, etc. Also remove "Get to know us" maybe? That's not a required heading but could be considered "About the company". Not in list of allowed headings but we could still include as a section? 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. Probably better to stick to those.
Thus we can have sections: About the team, Responsibilities, Qualifications, Pay, Benefits, Schedule.
We need to preserve all substantive information. Let's extract.
About The Team paragraph: "Zillow Group is seeking a Director, Marketing AI & Automation to lead a new team within Marketing, Technology & Operations. This role will be accountable for delivering Marketing AI big bets, responsible for the roadmap, the platform, the governance, and the path that carries use cases into scaled production. This role is responsible for shepherding AI big bets from strategy development to scaled implementation, including the platform and integration work they depend on, the measurement that proves impact, the change management that makes them stick, and the handoff to the teams who will run them day to day. The role also owns what comes next: sourcing and shaping the next generation of bets as the technology and the business shift, building the case for what to invest behind, and deciding what to retire. This role will be responsible for building and leading a multidisciplinary team responsible for scaling AI use cases. The team is expected to have a mix of strategic, technical and operational skills."
We can put that as prose under About the team
with
.
Responsibilities: list of bullet points from "Key Responsibilities". Let's extract each:
- Own the Marketing AI roadmap: Setting and defending the use-case portfolio, including what gets built, in what order, and for whom, prioritized against reclaimed capacity and business impact
- Run the path from idea to production: Building and operating the intake stage-gate from idea to pilot to production to owned, including the handoff model that transfers run-state to the team accountable for the outcome
- Stand up the agent and orchestration platform: Owning the shared layer, reusable components, and the data and vendor integration that AI use cases depend on, focused on integration and orchestration rather than model building
- Own AI governance for Marketing: Running agent audits, brand-risk scoring, and exclusion zones in partnership with Legal and Brand, aligned to Zillow's AI Principles and to external standards
- Drive adoption across the org: Running the adoption program and the network of embedded AI liaisons so that capability is embedded in day-to-day workflows rather than sitting unused
- Build and lead the team: Hiring into net-new technical and strategic roles, integrating talent redeployed from across Marketing, and setting the performance bar for a newly formed team
- Report value to leadership: Owning the measurement of capacity gained, speed to market, and business impact, including a clear account of what did not work
We'll put each as
- under
.
Qualifications/skills: "Who you are" section includes many bullet points (numbered). Let's extract:
- 10+ years in marketing technology, growth engineering, applied AI, or technical product, including 4+ years leading teams.
- Production track record: Has moved AI use cases from proof of concept to scaled operation, and can speak specifically to what was built, what broke along the way, and what the measured impact was
- Marketing fluency: Strong understanding of how Marketing operate, with enough depth to hold a substantive conversation with a channel leader about where AI helps and where it does not
- Technically credible: Able to go deep with engineers on agent orchestration, data integration, and evaluation, and to distinguish a serious architecture from a demo, without needing to build models directly. Familiarity with a modern composable stack (CDP, reverse ETL, cloud data platform, enterprise LLM tooling) highly valued
- Enablement mindset: Track record running a center-led function that transferred capability outward as it matured, rather than accumulating ownership. Experience standing up a center of excellence or platform team from zero a plus
- Governance judgment: Experience managing brand, legal, and privacy risk in AI systems, and building the review mechanisms rather than resisting them
- Influence without authority: Able to drive outcomes that land inside other teams, on other roadmaps, without direct control
- Build-versus-buy judgment: Experience evaluating and managing AI and martech vendors, with a clear view of when a platform partner beats an internal build
- Bachelor's degree required; advanced degree in a technical or business field (MBA, Computer Science, Engineering, Analytics) a plus
We can put these as - under
Qualifications
(or Skills). Use Qualifications.
Pay: details: "This role has been categorized as a Remote position. “Remote” employees do not have a permanent corporate office workplace and, instead, work from a physical location of their choice, which must be identified to the Company. U.S. employees may live in any of the 50 United States, with limited exceptions. In California, Connecticut, Maryland, Massachusetts, New Jersey, New York, Washington state, and Washington DC the standard base pay range for this role is $231,000.00 - $369,000.00 annually. This base pay range is specific to these locations and may not be applicable to other locations. In Colorado, Hawaii, Illinois, Maine, Minnesota, Nevada, Ohio, Rhode Island, Vermont, and Virginia the standard base pay range for this role is $219,500.00 - $350,600.00 annually. The base pay range is specific to these locations and may not be applicable to other locations. In addition to a competitive base salary this position is also eligible for equity awards based on factors such as experience, performance and location. Actual amounts will vary depending on experience, performance and location. Employees in this role will not be paid below the salary threshold for exempt employees in the state where they reside."
We need Pay section: include base pay ranges and equity awards mention. Could also include note about remote.
We should not include filler like "Actual amounts will vary depending on experience, performance and location." That's substantive.
We'll put under Pay
with containing that info.
Benefits: equity awards already mentioned in Pay; but we could also have Benefits section focusing on equity awards and maybe other benefits? The posting only mentions equity awards. Could still have Benefits: "Eligible for equity awards based on factors such as experience, performance and location." But that's already in Pay. To avoid duplication, maybe we keep Pay only and not Benefits. However instruction says prefer few substantive sections over many thin ones. Could combine Pay and Benefits? But they said use Benefits section if posting actually states them. It does state equity awards, which is a benefit. Could make Benefits section with that detail, and Pay section with base pay ranges. That's fine.
Schedule: Remote position description. We'll put under
Schedule
with describing remote.
We must not include duplicated lines. Ensure we don't repeat same info.
Now produce HTML fragment.
We'll structure:
About the team
...
Responsibilities
- ...
...
Qualifications
- ...
...
Pay
...
Benefits
Eligible for equity awards based on factors such as experience, performance and location.
Schedule
This role is categorized as a Remote position; employees work from a physical location of their choice (must be identified to the company) and may reside in any of the 50 United States, with limited exceptions.
We need to ensure we preserve all substantive info from Pay section: base pay ranges for two sets of states, plus note about not being paid below exempt threshold, plus equity awards mention (we moved equity awards to Benefits). Also mention "In addition to a competitive base salary this position is also eligible for equity awards based on factors such as experience, performance and location." We'll keep equity awards in Benefits; Pay section will include base pay ranges and note about not being paid below exempt threshold.
Let's craft Pay paragraph:
"In California, Connecticut, Maryland, Massachusetts, New Jersey, New York, Washington state, and Washington DC the standard base pay range for this role is $231,000.00 - $369,000.00 annually. In Colorado, Hawaii, Illinois, Maine, Minnesota, Nevada, Ohio, Rhode Island, Vermont, and Virginia the standard base pay range is $219,500.00 - $350,600.00 annually. Employees in this role will not be paid below the salary threshold for exempt employees in the state where they reside."
We could also mention that base pay range is specific to those locations and may not be applicable elsewhere. That's substantive. Include that.
Thus Pay paragraph: include both statements.
Now Benefits paragraph: "Eligible for equity awards based on factors such as experience, performance and location. Actual amounts will vary depending on experience, performance and location."
We could also mention "In addition to a competitive base salary this position is also eligible for equity awards..." but we already have base salary in Pay. Keep Benefits as equity awards.
Now Schedule paragraph: include remote description and US employees may live in any of the 50 states, with limited exceptions.
Now About the team paragraph: we need to preserve all substantive info. Let's rewrite as a single paragraph maybe two sentences but keep all details.
Original About The Team paragraph: "Z
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. Thus we need to decide which sections to include based on content. We have: - About The Team: description of team and role. Could be "About the team" heading. - About The Role: Key Responsibilities list (multiple bullet points). Could be "Responsibilities" heading. - Who you are: qualifications, requirements, skills. Could be "Qualifications" or "Skills" heading. - Pay: base pay ranges for specific locations, plus equity awards mention. So we can have "Pay" heading with details. - Benefits: equity awards mentioned, maybe also mention "competitive base salary" and "eligible for equity awards". Could be "Benefits" heading. - Schedule: Remote position description. Could be "Schedule" heading. We must not include sections with filler. All these have real content. We must not repeat job title. Not include Job ID. We must remove boilerplate like EEO, legal, etc. Also remove "Get to know us" maybe? That's not a required heading but could be considered "About the company". Not in list of allowed headings but we could still include as a section? 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. Probably better to stick to those.
Thus we can have sections: About the team, Responsibilities, Qualifications, Pay, Benefits, Schedule.
We need to preserve all substantive information. Let's extract.
About The Team paragraph: "Zillow Group is seeking a Director, Marketing AI & Automation to lead a new team within Marketing, Technology & Operations. This role will be accountable for delivering Marketing AI big bets, responsible for the roadmap, the platform, the governance, and the path that carries use cases into scaled production. This role is responsible for shepherding AI big bets from strategy development to scaled implementation, including the platform and integration work they depend on, the measurement that proves impact, the change management that makes them stick, and the handoff to the teams who will run them day to day. The role also owns what comes next: sourcing and shaping the next generation of bets as the technology and the business shift, building the case for what to invest behind, and deciding what to retire. This role will be responsible for building and leading a multidisciplinary team responsible for scaling AI use cases. The team is expected to have a mix of strategic, technical and operational skills."
We can put that as prose under About the team
with
. Responsibilities: list of bullet points from "Key Responsibilities". Let's extract each: - Own the Marketing AI roadmap: Setting and defending the use-case portfolio, including what gets built, in what order, and for whom, prioritized against reclaimed capacity and business impact - Run the path from idea to production: Building and operating the intake stage-gate from idea to pilot to production to owned, including the handoff model that transfers run-state to the team accountable for the outcome - Stand up the agent and orchestration platform: Owning the shared layer, reusable components, and the data and vendor integration that AI use cases depend on, focused on integration and orchestration rather than model building - Own AI governance for Marketing: Running agent audits, brand-risk scoring, and exclusion zones in partnership with Legal and Brand, aligned to Zillow's AI Principles and to external standards - Drive adoption across the org: Running the adoption program and the network of embedded AI liaisons so that capability is embedded in day-to-day workflows rather than sitting unused - Build and lead the team: Hiring into net-new technical and strategic roles, integrating talent redeployed from across Marketing, and setting the performance bar for a newly formed team - Report value to leadership: Owning the measurement of capacity gained, speed to market, and business impact, including a clear account of what did not work We'll put each as
- .
Qualifications/skills: "Who you are" section includes many bullet points (numbered). Let's extract:
- 10+ years in marketing technology, growth engineering, applied AI, or technical product, including 4+ years leading teams.
- Production track record: Has moved AI use cases from proof of concept to scaled operation, and can speak specifically to what was built, what broke along the way, and what the measured impact was
- Marketing fluency: Strong understanding of how Marketing operate, with enough depth to hold a substantive conversation with a channel leader about where AI helps and where it does not
- Technically credible: Able to go deep with engineers on agent orchestration, data integration, and evaluation, and to distinguish a serious architecture from a demo, without needing to build models directly. Familiarity with a modern composable stack (CDP, reverse ETL, cloud data platform, enterprise LLM tooling) highly valued
- Enablement mindset: Track record running a center-led function that transferred capability outward as it matured, rather than accumulating ownership. Experience standing up a center of excellence or platform team from zero a plus
- Governance judgment: Experience managing brand, legal, and privacy risk in AI systems, and building the review mechanisms rather than resisting them
- Influence without authority: Able to drive outcomes that land inside other teams, on other roadmaps, without direct control
- Build-versus-buy judgment: Experience evaluating and managing AI and martech vendors, with a clear view of when a platform partner beats an internal build
- Bachelor's degree required; advanced degree in a technical or business field (MBA, Computer Science, Engineering, Analytics) a plus
We can put these as
- under
Qualifications
(or Skills). Use Qualifications. Pay: details: "This role has been categorized as a Remote position. “Remote” employees do not have a permanent corporate office workplace and, instead, work from a physical location of their choice, which must be identified to the Company. U.S. employees may live in any of the 50 United States, with limited exceptions. In California, Connecticut, Maryland, Massachusetts, New Jersey, New York, Washington state, and Washington DC the standard base pay range for this role is $231,000.00 - $369,000.00 annually. This base pay range is specific to these locations and may not be applicable to other locations. In Colorado, Hawaii, Illinois, Maine, Minnesota, Nevada, Ohio, Rhode Island, Vermont, and Virginia the standard base pay range for this role is $219,500.00 - $350,600.00 annually. The base pay range is specific to these locations and may not be applicable to other locations. In addition to a competitive base salary this position is also eligible for equity awards based on factors such as experience, performance and location. Actual amounts will vary depending on experience, performance and location. Employees in this role will not be paid below the salary threshold for exempt employees in the state where they reside." We need Pay section: include base pay ranges and equity awards mention. Could also include note about remote. We should not include filler like "Actual amounts will vary depending on experience, performance and location." That's substantive. We'll put underPay
withcontaining that info. Benefits: equity awards already mentioned in Pay; but we could also have Benefits section focusing on equity awards and maybe other benefits? The posting only mentions equity awards. Could still have Benefits: "Eligible for equity awards based on factors such as experience, performance and location." But that's already in Pay. To avoid duplication, maybe we keep Pay only and not Benefits. However instruction says prefer few substantive sections over many thin ones. Could combine Pay and Benefits? But they said use Benefits section if posting actually states them. It does state equity awards, which is a benefit. Could make Benefits section with that detail, and Pay section with base pay ranges. That's fine. Schedule: Remote position description. We'll put under
Schedule
withdescribing remote. We must not include duplicated lines. Ensure we don't repeat same info. Now produce HTML fragment. We'll structure:
About the team
...
Responsibilities
- ... ...
Qualifications
- ... ...
Pay
...
Benefits
Eligible for equity awards based on factors such as experience, performance and location.
Schedule
This role is categorized as a Remote position; employees work from a physical location of their choice (must be identified to the company) and may reside in any of the 50 United States, with limited exceptions.
We need to ensure we preserve all substantive info from Pay section: base pay ranges for two sets of states, plus note about not being paid below exempt threshold, plus equity awards mention (we moved equity awards to Benefits). Also mention "In addition to a competitive base salary this position is also eligible for equity awards based on factors such as experience, performance and location." We'll keep equity awards in Benefits; Pay section will include base pay ranges and note about not being paid below exempt threshold. Let's craft Pay paragraph: "In California, Connecticut, Maryland, Massachusetts, New Jersey, New York, Washington state, and Washington DC the standard base pay range for this role is $231,000.00 - $369,000.00 annually. In Colorado, Hawaii, Illinois, Maine, Minnesota, Nevada, Ohio, Rhode Island, Vermont, and Virginia the standard base pay range is $219,500.00 - $350,600.00 annually. Employees in this role will not be paid below the salary threshold for exempt employees in the state where they reside." We could also mention that base pay range is specific to those locations and may not be applicable elsewhere. That's substantive. Include that. Thus Pay paragraph: include both statements. Now Benefits paragraph: "Eligible for equity awards based on factors such as experience, performance and location. Actual amounts will vary depending on experience, performance and location." We could also mention "In addition to a competitive base salary this position is also eligible for equity awards..." but we already have base salary in Pay. Keep Benefits as equity awards. Now Schedule paragraph: include remote description and US employees may live in any of the 50 states, with limited exceptions. Now About the team paragraph: we need to preserve all substantive info. Let's rewrite as a single paragraph maybe two sentences but keep all details. Original About The Team paragraph: "Z