Associate Director, Programmatic
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. 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.
We need to decide which sections to include based on content.
Content sections:
- WHY DEPT®? (company description) could be "About the role"? Actually "About the role" is about the role itself, not company. But we could treat "WHY DEPT®?" as "About the company" but not in list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly add other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we could use other headings if needed? But likely we should stick to those. The posting includes "THE ROLE:" description, "WHAT YOU’LL DO:" responsibilities, "WHAT YOU BRING:" qualifications/requirements/skills, "WHAT DO WE OFFER?" benefits, and salary range.
Thus we can map:
- About the role: maybe the "THE ROLE:" paragraph describing role purpose. Could be used as About the role.
- Responsibilities: "WHAT YOU’LL DO:" list.
- Requirements: maybe "WHAT YOU BRING:" includes experience, skills, etc. Could split into Requirements and Qualifications and Skills. But we need to avoid thin sections. Could combine Requirements and Qualifications into one? But we have to follow instruction: use headings for those categories if we have content. We could make a single "Requirements" heading covering experience, skills, etc. Or we could split into Requirements (experience) and Skills (platforms). But we need to avoid thin sections; better to have a few substantive sections.
We have salary range: "US Remote Range $96,200—$115,000 USD". That's pay info, so we can create Pay section.
Benefits: "WHAT DO WE OFFER?" list: Healthcare, Dental, Vision coverage; 401K plan, plus matching; PTO; Paid Company Holidays; Parental Leave. That's benefits.
Schedule: Not mentioned explicitly; maybe implied 40-hour workweek mentioned in salary note: "This is based on a 40-hour workweek and leveling." That's schedule info (40-hour workweek). So we could include Schedule section with that detail.
We must not create sections with filler like "not specified". We have actual content for Pay, Benefits, Schedule.
Now we need to remove boilerplate: EEO, E-Verify, B Corp, diversity statements, etc. Also remove duplicated lines, application instructions. Also remove "WHY DEPT®?" maybe we could incorporate into About the role? But we have a separate "About the role" heading for role description; we could also include company description under About the role? Might be okay.
We need to preserve all substantive information: that includes company description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description from WHY DEPT®? as part of the output. Where to put it? Could be a preceding paragraph before headings, maybe as a
intro. Since we cannot add arbitrary headings not in list, we can just put it as a
before the first heading. That's allowed.
Similarly, the diversity statement etc is boilerplate to remove.
Also remove "DEPT® participates in E-Verify..." etc.
Also remove "Learn more about DEPT® DIVERSITY, EQUITY, & INCLUSION..." etc.
Also remove "We are a B Corp-certified company..." etc.
Also remove "We’re 50|50 tech and marketing..." etc.
Also remove "Clients include Google, Lufthansa, Coach, eBay, and OpenAI." That's substantive? It's about company; maybe keep? It's part of company description; but it's after diversity section. Might be considered substantive but could be considered boilerplate? It's factual about clients; maybe keep as part of company description. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Client list is not boilerplate; it's substantive. So we keep it.
But we need to avoid duplication: there is also earlier line "DEPT® is a Growth Invention company built to help the world’s most ambitious brands grow faster." repeated later. We should keep only one instance? The instruction says remove duplicated lines. So we should deduplicate.
Let's extract substantive content:
From WHY DEPT®?:
"We are a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, we create what is next by pioneering ideas, acting fast, and moving further because standing still just is not in our DNA. We are drawn to people who stay curious, move with intent, and never stop inventing. Our culture runs on three values: better together, relentlessly curious, and get sh*t done. It is how we work, how we grow, and how we make things that matter. At DEPT®, you will find the freedom to explore, the space to collaborate, and the trust to make a real impact for our clients, for each other, and for the world we are helping to build."
Later duplicate: "DEPT® is a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, our 4,000+ specialists deliver growth invention across Brand & Media, Experience, Commerce, CRM, and Technology & Data. We’re 50|50 tech and marketing, partner-led, and first to move. Clients include Google, Lufthansa, Coach, eBay, and OpenAI."
We need to keep unique info: first paragraph plus the second paragraph's additional details: "our 4,000+ specialists deliver growth invention across Brand & Media, Experience, Commerce, CRM, and Technology & Data. We’re 50|50 tech and marketing, partner-led, and first to move. Clients include Google, Lufthansa, Coach, eBay, and OpenAI."
We should combine them without duplication.
Now THE ROLE: paragraph.
WHAT YOU’LL DO: list of responsibilities (multiple sentences each starting with a verb). We need to turn into
- items.
WHAT YOU BRING: list of qualifications/experience/skills. We need to turn into list items maybe under Requirements or Skills.
WHAT DO WE OFFER: benefits list.
Pay: salary range.
Schedule: 40-hour workweek note.
Now we need to decide headings.
Potential sections:
- About the role: could include THE ROLE paragraph plus maybe company description? But we already have company description before headings. Let's put company description as a leading
(no heading). Then
About the role
with the THE ROLE paragraph.
- Responsibilities
with of WHAT YOU’LL DO items.
- Requirements
with of WHAT YOU BRING items (maybe split into experience, skills, etc). But we could also have Skills
for platforms etc. However to avoid thin sections, we could combine all into Requirements.
But we also have "Advanced proficiency across leading programmatic platforms..." etc. That's skills.
We could have Qualifications
for experience and leadership, and Skills
for platforms and technical abilities. But that may be two sections; still okay if they have substantive content.
Let's see content of WHAT YOU BRING:
"5–7 years of programmatic experience, within an agency on fast-paced, agile, enterprise account(s).
Advanced proficiency across leading programmatic platforms including The Trade Desk, DV360, Amazon DSP, Google Ads, and CM360. Deep experience with YouTube activation, measurement, and optimization is required.
Confident mastery of campaign activation, optimization, measurement, troubleshooting, and quality assurance across complex programmatic campaigns.
A “Better Together” spirit, demonstrated through a passion for collaboration, mentorship, and developing future leaders. Proven experience leading and developing teams, with the ability to coach, influence, and create opportunities for others to grow.
Experience operating as a senior contributor within enterprise accounts, embodying a true “self-starter” mindset.
Demonstrated ability to build trust, stay organized, maintain exceptional attention to detail, fluidly manage changing deliverables and deadlines, and communicate effectively across stakeholders.
Strong analytical and problem-solving skills, with the ability to translate performance data into actionable recommendations and clear business insights.
A "get sh*t done" mentality when it comes to troubleshooting technical issues or navigating industry shifts.
Ability to balance strategic thinking with operational execution, comfortably moving between high-level recommendations, story-led presentations, and detailed campaign reviews.
A collaborative, curious, and solutions-oriented approach aligned with DEPT®'s values and culture."
We could split into:
- Requirements: experience (5-7 years, agency, enterprise accounts, senior contributor, self-starter, leading teams, etc.)
- Skills: platform proficiency, campaign activation, optimization, measurement, troubleshooting, QA, analytical, problem-solving, strategic vs operational, etc.
- Qualifications: maybe leadership spirit, Better Together, get sh*t done mentality, collaborative curious solutions-oriented.
But to avoid many thin sections, we could combine into one Requirements section with all items as - . That's okay; it's substantive.
Thus we will have:
About the role
...
Responsibilities
...
Requirements
...
Benefits
...
Pay
US Remote Range $96,200—$115,000 USD
Schedule
Based on a 40‑hour workweek.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to remove duplicated lines: we already deduped company description.
Now we need to ensure we don't include any application instructions like "Apply", "Learn more", etc. Remove those.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, company description paragraph: combine unique sentences.
Let's write:
We are a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, we create what is next by pioneering ideas, acting fast, and
for prose. Do NOT repeat the job title as a heading. 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. We need to decide which sections to include based on content. Content sections: - WHY DEPT®? (company description) could be "About the role"? Actually "About the role" is about the role itself, not company. But we could treat "WHY DEPT®?" as "About the company" but not in list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly add other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we could use other headings if needed? But likely we should stick to those. The posting includes "THE ROLE:" description, "WHAT YOU’LL DO:" responsibilities, "WHAT YOU BRING:" qualifications/requirements/skills, "WHAT DO WE OFFER?" benefits, and salary range. Thus we can map: - About the role: maybe the "THE ROLE:" paragraph describing role purpose. Could be used as About the role. - Responsibilities: "WHAT YOU’LL DO:" list. - Requirements: maybe "WHAT YOU BRING:" includes experience, skills, etc. Could split into Requirements and Qualifications and Skills. But we need to avoid thin sections. Could combine Requirements and Qualifications into one? But we have to follow instruction: use headings for those categories if we have content. We could make a single "Requirements" heading covering experience, skills, etc. Or we could split into Requirements (experience) and Skills (platforms). But we need to avoid thin sections; better to have a few substantive sections. We have salary range: "US Remote Range $96,200—$115,000 USD". That's pay info, so we can create Pay section. Benefits: "WHAT DO WE OFFER?" list: Healthcare, Dental, Vision coverage; 401K plan, plus matching; PTO; Paid Company Holidays; Parental Leave. That's benefits. Schedule: Not mentioned explicitly; maybe implied 40-hour workweek mentioned in salary note: "This is based on a 40-hour workweek and leveling." That's schedule info (40-hour workweek). So we could include Schedule section with that detail. We must not create sections with filler like "not specified". We have actual content for Pay, Benefits, Schedule. Now we need to remove boilerplate: EEO, E-Verify, B Corp, diversity statements, etc. Also remove duplicated lines, application instructions. Also remove "WHY DEPT®?" maybe we could incorporate into About the role? But we have a separate "About the role" heading for role description; we could also include company description under About the role? Might be okay. We need to preserve all substantive information: that includes company description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description from WHY DEPT®? as part of the output. Where to put it? Could be a preceding paragraph before headings, maybe as a
intro. Since we cannot add arbitrary headings not in list, we can just put it as a
before the first heading. That's allowed. Similarly, the diversity statement etc is boilerplate to remove. Also remove "DEPT® participates in E-Verify..." etc. Also remove "Learn more about DEPT® DIVERSITY, EQUITY, & INCLUSION..." etc. Also remove "We are a B Corp-certified company..." etc. Also remove "We’re 50|50 tech and marketing..." etc. Also remove "Clients include Google, Lufthansa, Coach, eBay, and OpenAI." That's substantive? It's about company; maybe keep? It's part of company description; but it's after diversity section. Might be considered substantive but could be considered boilerplate? It's factual about clients; maybe keep as part of company description. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Client list is not boilerplate; it's substantive. So we keep it. But we need to avoid duplication: there is also earlier line "DEPT® is a Growth Invention company built to help the world’s most ambitious brands grow faster." repeated later. We should keep only one instance? The instruction says remove duplicated lines. So we should deduplicate. Let's extract substantive content: From WHY DEPT®?: "We are a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, we create what is next by pioneering ideas, acting fast, and moving further because standing still just is not in our DNA. We are drawn to people who stay curious, move with intent, and never stop inventing. Our culture runs on three values: better together, relentlessly curious, and get sh*t done. It is how we work, how we grow, and how we make things that matter. At DEPT®, you will find the freedom to explore, the space to collaborate, and the trust to make a real impact for our clients, for each other, and for the world we are helping to build." Later duplicate: "DEPT® is a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, our 4,000+ specialists deliver growth invention across Brand & Media, Experience, Commerce, CRM, and Technology & Data. We’re 50|50 tech and marketing, partner-led, and first to move. Clients include Google, Lufthansa, Coach, eBay, and OpenAI." We need to keep unique info: first paragraph plus the second paragraph's additional details: "our 4,000+ specialists deliver growth invention across Brand & Media, Experience, Commerce, CRM, and Technology & Data. We’re 50|50 tech and marketing, partner-led, and first to move. Clients include Google, Lufthansa, Coach, eBay, and OpenAI." We should combine them without duplication. Now THE ROLE: paragraph. WHAT YOU’LL DO: list of responsibilities (multiple sentences each starting with a verb). We need to turn into
- items.
WHAT YOU BRING: list of qualifications/experience/skills. We need to turn into list items maybe under Requirements or Skills.
WHAT DO WE OFFER: benefits list.
Pay: salary range.
Schedule: 40-hour workweek note.
Now we need to decide headings.
Potential sections:
- About the role: could include THE ROLE paragraph plus maybe company description? But we already have company description before headings. Let's put company description as a leading
(no heading). Then
About the role
with the THE ROLE paragraph. -Responsibilities
with- of WHAT YOU’LL DO items.
-
- . That's okay; it's substantive.
Thus we will have:
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Pay
US Remote Range $96,200—$115,000 USD
Schedule
Based on a 40‑hour workweek.
We need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to remove duplicated lines: we already deduped company description. Now we need to ensure we don't include any application instructions like "Apply", "Learn more", etc. Remove those. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. First, company description paragraph: combine unique sentences. Let's write:We are a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, we create what is next by pioneering ideas, acting fast, and
Requirements
with- of WHAT YOU BRING items (maybe split into experience, skills, etc). But we could also have
Skills
for platforms etc. However to avoid thin sections, we could combine all into Requirements. But we also have "Advanced proficiency across leading programmatic platforms..." etc. That's skills. We could haveQualifications
for experience and leadership, andSkills
for platforms and technical abilities. But that may be two sections; still okay if they have substantive content. Let's see content of WHAT YOU BRING: "5–7 years of programmatic experience, within an agency on fast-paced, agile, enterprise account(s). Advanced proficiency across leading programmatic platforms including The Trade Desk, DV360, Amazon DSP, Google Ads, and CM360. Deep experience with YouTube activation, measurement, and optimization is required. Confident mastery of campaign activation, optimization, measurement, troubleshooting, and quality assurance across complex programmatic campaigns. A “Better Together” spirit, demonstrated through a passion for collaboration, mentorship, and developing future leaders. Proven experience leading and developing teams, with the ability to coach, influence, and create opportunities for others to grow. Experience operating as a senior contributor within enterprise accounts, embodying a true “self-starter” mindset. Demonstrated ability to build trust, stay organized, maintain exceptional attention to detail, fluidly manage changing deliverables and deadlines, and communicate effectively across stakeholders. Strong analytical and problem-solving skills, with the ability to translate performance data into actionable recommendations and clear business insights. A "get sh*t done" mentality when it comes to troubleshooting technical issues or navigating industry shifts. Ability to balance strategic thinking with operational execution, comfortably moving between high-level recommendations, story-led presentations, and detailed campaign reviews. A collaborative, curious, and solutions-oriented approach aligned with DEPT®'s values and culture." We could split into: - Requirements: experience (5-7 years, agency, enterprise accounts, senior contributor, self-starter, leading teams, etc.) - Skills: platform proficiency, campaign activation, optimization, measurement, troubleshooting, QA, analytical, problem-solving, strategic vs operational, etc. - Qualifications: maybe leadership spirit, Better Together, get sh*t done mentality, collaborative curious solutions-oriented. But to avoid many thin sections, we could combine into one Requirements section with all items as - . That's okay; it's substantive.
Thus we will have: