We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Own"), Requirements (Candidate Profile Must Haves), maybe Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes "About the Role" heading. Then "What You'll Own" is responsibilities. Then "Candidate Profile" with Must Haves and Nice-to-Haves and Not a Fit If. Then Benefits listed. Also schedule: "This role is required to be in office 5 days per week at our Lehi HQ." So schedule info present. Pay not mentioned, so we should not include Pay section. Benefits present. Also maybe "Qualifications" not separate; we can treat Must Haves as Requirements. Skills maybe not separate; we can embed within Must Haves. But we need to follow instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with content. So we will have:
About the role
... (the paragraph after About the Role heading)
Responsibilities
- ... list items from What You'll Own
Requirements
Maybe also include Nice-to-Haves as part of Requirements? Could be separate but we can keep as part of Requirements or maybe as a separate section "Preferred Qualifications". But instruction only lists certain headings; we could add "Qualifications" for Nice-to-Haves. But better to keep only sections with real content: About the role, Responsibilities, Requirements (Must Haves), Benefits, Schedule. Also maybe include "Skills" but we can incorporate into Requirements. We'll not create empty sections.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title. Must not include boilerplate like EEO etc. Remove duplicated lines.
We need to extract the About the role paragraph: It starts after "About the RoleWe are transforming..." Actually the text: "About the RoleWe are transforming the way Aesthetic businesses operate with an AI workforce, and we're hiring the Director who will run marketing demand generation end to end. Think of this as the CMO of a sub-vertical: you own the monthly revenue, pipeline, and efficiency numbers the business is counting on. You own the strategy and channel execution to get there.This is a builder and operator role: you'll roll up your sleeves, drive critical projects, lean in deeply with a team of direct and indirect reports, and IC where needed to get the job done. You're deeply performance and demand focused.The right person is highly biased towards action, hungry to drive impact, exercises extreme ownership, thrives at a startup pace, and can set a vision that inspires the team. You're a heavy AI user, passionate about building a marketing engine at the bleeding edge of what's possible.This role is required to be in office 5 days per week at our Lehi HQ."
We need to separate schedule line maybe later. But the About the role paragraph includes schedule line at end. However schedule is separate section; we could keep schedule line in About the role or move to Schedule section. The instruction: include a section ONLY when posting has real specific content for it. Schedule content exists: "This role is required to be in office 5 days per week at our Lehi HQ." So we should put that in Schedule section. So we should remove that sentence from About the role paragraph.
Thus About the role paragraph: everything up to before schedule sentence.
Let's extract: "About the RoleWe are transforming the way Aesthetic businesses operate with an AI workforce, and we're hiring the Director who will run marketing demand generation end to end. Think of this as the CMO of a sub-vertical: you own the monthly revenue, pipeline, and efficiency numbers the business is counting on. You own the strategy and channel execution to get there.This is a builder and operator role: you'll roll up your sleeves, drive critical projects, lean in deeply with a team of direct and indirect reports, and IC where needed to get the job done. You're deeply performance and demand focused.The right person is highly biased towards action, hungry to drive impact, exercises extreme ownership, thrives at a startup pace, and can set a vision that inspires the team. You're a heavy AI user, passionate about building a marketing engine at the bleeding edge of what's possible."
We need to ensure proper spacing and punctuation. We'll output as
About the RoleWe are transforming...
but note that "About the Role" is heading, not part of paragraph. So paragraph starts after that. We'll just put the content.
Now Responsibilities: "What You'll Own" bullet points. Let's extract each line:
- Set an integrated Aesthetics marketing strategy that delivers on demand targets and rallies the team. Set the vision, set the pace, and hold the org to it.
- Hold full accountability for marketing's monthly revenue, pipeline, and efficiency targets, plus the levers underneath them: channel mix, budget allocation, execution, comms calendar, and demand content. You own the number and how it gets hit.
- Track pacing and pipeline against targets, and proactively lead the team in building and executing on gap plans the moment funnel targets slip.
- Lead, coach and raise the ceiling for a lean team of direct reports owning trade show/events, partner marketing, webinars, third-party media, lifecycle and content marketing channels.
- Proactively collaborate with a team of indirect reports (centralized marketing subject matter experts) across digital channels, AEO/SEO, and web, to execute on the highest impact strategies in your vertical.
- Rigorously measure the efficacy of tactics/channels/funnel and continuously optimize via experimentation. Align marketing portfolio bets to maximize impact.
- Manage the vertical budget, spending within profitability constraints, surfacing opportunities. Drive AOP planning prep and recommendations.
- Regularly report on marketing performance and strategy to leadership / exec team.
- Set the standard for AI-first marketing in tooling, planning, and agent building, deploying AI workflows that transform impact.
- Work closely with marketing leadership across other verticals (auto, aesthetics) and partnering functions (design, product marketing) to prep for launches, align on resourcing and positioning. Align with Sales, CS, Product, Finance, and Revenue Operations leaders on goals and priorities.
We need to put each as
.
Now Requirements (Must Haves): list:
- Successful track record of leading an integrated, demand generation strategy/function or channel group with accountability to a revenue number, a budget, and ROI.
- Hands-on depth across relevant marketing channels like trade shows, field or partner marketing, lifecycle, webinars, content marketing, digital, and ABM. You've personally run a collection of channels at similar scale.
- Extreme ownership and bias to action. You move fast without waiting for consensus, and you're comfortable building a strategy out of ambiguity and high change.
- Critical thinker and analytically rigorous. You make data informed decisions using full funnel metrics and know what inputs are most important to drive to a decision.
- Highly performance focused and ROI minded. Understands the right balance of investment into higher funnel initiatives and the limitations of various attribution methods.
- Excellent communicator. Clear, decisive, and collaborative.
- Sets a high bar for the team and provides the coaching, vision and accountability to get there.
- Excellent project management skills. Can drive action and alignment.
- Customer first. Draws on a deep understanding of the customer, industry and Podium value.
- Uses AI heavily, building workflows and agents. Can show what you've built.
- A strong cross-functional partner. Builds trust and alignment across the org.
Nice-to-Haves could be omitted or could be placed under "Qualifications" but we might not need separate section. Since we have Requirements, we could add a "Qualifications" section for Nice-to-Haves. But instruction says prefer few substantive sections over many thin ones. So maybe we incorporate Nice-to-Haves into Requirements as additional bullet points but label? Could just add them as part of Requirements but it's okay. However we must not invent or summarize away detail; we need to preserve all substantive information. So we should include Nice-to-Haves somewhere. Could add a subsection under Requirements with heading "Nice-to-haves" but that's not one of the allowed headings. Allowed headings list includes Skills, Qualifications, etc. We could put Nice-to-Haves under "Qualifications". That seems appropriate: Qualifications section for nice-to-haves. So we will have:
Requirements
Qualifications
Now Benefits: list:
- Work in Lehi, UT, 5 days a week (but that's schedule; we already have schedule separate)
- Open and transparent culture
- Life insurance, long and short-term disability coverage
- Paid maternity and paternity leave
- Fertility Benefits
- Generous vacation time, plus three 4-day summer holiday weekends
- Excellent medical, dental, and vision benefits
- 401k Plan
- Bi-annual swag drops with cool Podium gear and apparel
- A stellar HQ (Utah) gym with local professional coaches and classes offered
- Onsite HQ (Utah) child care center, subsidized for employees
We should not duplicate schedule line. So Benefits list excludes the schedule line.
Now Schedule: "This role is required to be in office 5 days per week at our Lehi HQ."
Now we need to ensure we don't include any boilerplate like EEO etc. Remove that.
Now produce HTML fragment: start with About the role
...
then Responsibilities
etc.
Make sure no extra text outside HTML.
Let's craft.
Check for any duplicated lines: The posting also had earlier paragraph about Podium description; we should not include that as it's not part of the job posting content after "About the Role"? Actually the initial paragraphs before "About the Role" are company overview; they might be considered part of the posting but not under a heading. The instruction: "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 didn't say to drop company overview. However we need to preserve ALL substantive information. The company overview is substantive. Should we include it? It appears before "About the Role". It's not under a heading. We could include it as a
before the first heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having a leading paragraph before any heading. It says "Output ONLY the HTML fragment". So we could include a
with the company overview. However the instruction about sections: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having a leading paragraph. So we should include the company overview as a paragraph before the first heading.
Let's extract company overview: At Podium, we bring AI Employees to local businesses that turn every conversation into revenue. Trusted by 60,000+ businesses across Auto, Home Services, and Aesthetics, Podium captures and converts leads 24/7, driving both new business and repeat customers.In under 24 months, we crossed $100M in AI Agent ARR, scaling 300% year-over-year. During this time, we’ve deployed 10,000 AI employees to empower real business outcomes for our customers. Podium is building what we believe will be the most impactful AI employee ecosystem for local business.Podium has been recognized as the Best AI Implementation by Inc. Magazine, highlighted by OpenAI for building revenue-driving AI Agents, and awarded the #1 AI