Program Manager

We need to output HTML fragment with sections: About the role (but note there is already "About The Role" heading in the posting; we should use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if there is real specific content. We need to parse the posting: It starts with "About Darkroom" description (company overview). Then "About The Role" description. Then "What You'll Do" (responsibilities). Then "You Should Apply If This Sounds Like You" (requirements/qualifications/skills). Then "What It's Like to Work at Darkroom" (benefits/culture). Then "Our Hiring Process and Compensation:" includes compensation and benefits summary. Then "Equal Opportunity Statement" which we should remove (boilerplate). Also need to remove cookie/navigation/legal/EEO etc. We need to preserve all substantive information, not invent or summarize away detail. Remove duplicated lines. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: we have "About The Role" section describing the role. So we can output

About the role

with a

containing that description. - Responsibilities: we have "What You'll Do" with bullet list of duties. So we can output

Responsibilities

with

• items. - Requirements/Qualifications/Skills: The "You Should Apply If This Sounds Like You" includes experience, skills, tools. Could split into Requirements (experience), Qualifications (maybe same), Skills (tools). But we need to avoid thin sections. Perhaps combine into one section "Requirements" or "Qualifications". The instruction says prefer a few substantive sections over many thin ones. So we could have one section for Requirements/Qualifications/Skills combined? But we need to use headings exactly as listed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose which to include. We should not create empty sections. So we can include Requirements (experience), Skills (tools), maybe Benefits, Pay. We have benefits described in "What It's Like to Work at Darkroom" and also in "Our Hiring Process and Compensation:" includes compensation and benefits summary. So we can have Benefits section with details: Unlimited PTO + US holidays, Remote-First Culture, Health & Wellness (medical, dental, vision), Finances, growth, retirement (401k with match and profit-sharing), Parental Leave, Growth (interdisciplinary model). Also maybe mention "Company-sponsored medical, dental, and vision coverage." etc. Pay: we have compensation: base salary range $120,000 per year (range? Actually says base salary range for this role is $120,000 per year. This range represents the anticipated minimum and maximum for this position...). So it's a single number? It says base salary range is $120,000 per year. That seems like both min and max are $120k. We'll include that as Pay. Schedule: we have "This is a fully remote role supporting a team in the EST time zone (9 AM–5 PM EST)." So schedule: remote, EST hours 9-5. We also need to include maybe "About Darkroom" as company overview? Not required heading; we could include as a

  before sections? 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 a general intro paragraph. We could include a brief

  about Darkroom before sections. But we need to preserve all substantive information. The "About Darkroom" paragraph is substantive; we should keep it. It could be placed before the first heading as a

  . That seems acceptable. We must remove boilerplate: Equal Opportunity Statement, maybe also "Our Hiring Process and Compensation:" includes hiring process description (phone screen, hiring manager, Executive calls). That's substantive? Could be considered part of hiring process; but we might keep it under a section? Not listed as a heading option. Could fold into a

  under Benefits or Pay? Might be considered minor metadata? The instruction says "fold minor metadata into a short

  or drop it." The hiring process steps could be considered minor metadata; but it's substantive? Might be okay to keep as a

  under a section like "About the role"? Not ideal. Perhaps we can include a short

  under a section like "About the role" or separate? The instruction says we can fold minor metadata into a short

  . So we could create a

  for hiring process details. But we also need to avoid duplication: The "Our Hiring Process and Compensation:" also includes compensation and benefits summary which we already captured. Thus plan: - Opening

  about Darkroom (the "About Darkroom" paragraph). -

  About the role

  with

  containing the "About The Role" paragraph. -

  Responsibilities

  with
  • items from "What You'll Do". -

    Requirements

    with
    • items from "You Should Apply If This Sounds Like You": experience 3-5+ years, conversant in paid media workflows, build tracker, proactive communicator, Notion guru, comfortable with Slack, Toggl, Google Sheets, juggle multiple accounts, high bar for output. -

      Skills

      maybe we could include tools: Notion, Slack, Toggl, Google Sheets. But we already included those in Requirements; maybe better to combine. To avoid thin sections, we could have just Requirements covering experience and skills. But we have separate headings list; we could omit Skills if we think it's thin. However we have specific skill mentions; we could include them under Requirements as part of list items. -

      Benefits

      with
      • items: Unlimited PTO + US holidays, Remote-First Culture (many roles fully remote; employees near NY or Lisbon HQ expected hybrid weekly in-office; hub locations include Brazil and Spain), Health & Wellness (company-sponsored medical, dental, vision coverage), Finances, growth, retirement (robust 401(k) program with company match and profit-sharing), Parental Leave (flexible parental leave), Growth (interdisciplinary model gives exposure beyond core role, grow skills, expand influence, stay at forefront). -

        Pay

        with

        containing base salary range $120,000 per year (minimum and maximum). Also mention performance-based compensation eligibility. -

        Schedule

        with

        containing fully remote role supporting a team in EST time zone (9 AM–5 PM EST). We also need to include maybe the hiring process steps as a short

        somewhere; maybe under About the role? Could add a

        after About the role: "The hiring process typically follows three stages: phone screen, hiring manager, and Executive calls." This is minor metadata; we can fold into a short

        . We must not include boilerplate like Equal Opportunity Statement. We must not repeat job title as heading. We must not include markdown fences. We must output only HTML fragment. Let's craft. Check for any duplicated lines: Ensure we don't repeat same content. Now produce HTML. We'll start with a

        about Darkroom. Then

        About the role

        ...

        Then

        Responsibilities

        ...
        Then

        Requirements

        ...
        Then

        Benefits

        ...
        Then

        Pay

        ...

        Then

        Schedule

        ...

        Optionally add a

        for hiring process after About the role or after Requirements? Let's put after About the role as a short

        . Make sure to close tags properly. Now write content. About Darkroom paragraph: "Darkroom is the leading next-generation growth marketing firm engineering the brands of tomorrow. Founded in 2017, we set out to redefine what a modern agency could be, by replacing the inertia of legacy advertising behemoths with a model built for speed, intelligence, and measurable impact. At our core, Darkroom is a human services company powered by Shadow, a universal AI commerce layer that integrates executive-level strategy with proprietary agentic technology. This fusion enables our teams to deliver outsized returns by enhancing creative output, operational efficiency, and revenue generation across every stage of the customer journey. Our track record speaks for itself: billions in attributable revenue driven across e-commerce marketplaces, media networks, DTC ecosystems, and social commerce platforms. Every engagement feeds into our proprietary data infrastructure, enabling a continuous feedback loop that accelerates growth, improves margins, and compounds results across our client portfolio. What began as a boutique design studio has evolved into one of the fastest-growing private companies in America (Inc. 5000) and among the most effective performance media agencies of the 2020s (Varos). Our founders were recognized by Forbes 30 Under 30 for advancing the intersection of technology, marketing, and advertising, cementing Darkroom's role as a defining player in the future of media innovation." About The Role paragraph: "This is a dedicated role on a single account, helping a key client bring a brand new product to market, with Darkroom owning all media channels. You are the operational owner of that engagement: the person accountable for the program running on time, in scope, and against every commitment, with no slips in timeline. That makes this different from a typical agency PM job. You are not coordinating a portfolio. You are going deep on one enterprise client, holding the operating rhythm, and creating accountability within the layers of Darkroom. You will report to the Director of Growth Strategy on the Hark engagement, with a dotted line to the Managing Director, Paid Media. You will work daily with Paid Social and Paid Search Specialists, Analytics, Creative, and the client's own program leads. This is a fully remote role supporting a team in the EST time zone (9 AM–5 PM EST)." Note: The schedule mention appears also there; but we will also have Schedule section. Might duplicate; but we need to preserve all substantive information. Could keep schedule mention in About the role paragraph; it's okay to have duplicate? The instruction says remove duplicated lines. So we should avoid duplicating the schedule sentence. We could remove it from About the role paragraph and keep only in Schedule section. However the About The Role paragraph includes that sentence; if we remove it, we are losing some info? But we will have Schedule section with that info, so it's not lost. So we can edit About The Role paragraph to exclude the schedule sentence. Let's do that: remove "This is a fully remote role supporting a team in the EST time zone (9 AM–5 PM EST)." from About The Role paragraph. Now Responsibilities: list from "What You'll Do". Items: - Service level accountability. You track our contracted SLAs, produce the reporting that evidences adherence, and escalate early when something is trending toward a miss. When the client asks whether we hit our commitments, the answer comes from you and it is already documented. - The Shared Model. You maintain Darkroom's side of the jointly held media plan, forecast, and ramp model, keep it reconciled against actuals, and manage the cad