Project Manager (Evergreen)

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to extract content from posting. First, identify sections: - About the role: The description: "Help run digital projects transforming the way people engage. As a Technical Project Manager, you’ll jump right in, interacting with clients, collaborating with diverse teams of UXers, Designers, Strategists, and Developers, leading website development, strategy and technical consulting projects from start to finish. You’ll help turn progressive ideas into actionable tactics, timelines, budgets, and deliverables." Also maybe "The company Blue State is a purpose-driven agency..." That's about company, maybe part of About the role? Could be separate but we only have limited headings. Could put company description under About the role as well. - Responsibilities: The list under "A day in the life" bullet points. Those are responsibilities. - Requirements / Qualifications / Skills: The "Some things we're looking for" list includes experience, communication skills, etc. Could split into Requirements (experience) and Skills (soft skills). But we can combine if needed. The instruction: prefer few substantive sections over many thin ones. So we could have Requirements (including experience and skills) and maybe Skills separate if there is distinct content. Let's see: The list includes: "2+ of professional experience as a technical project manager with experience in digital strategy and managing agile website development projects, specifically Wordpress or Drupal builds" "Strong communication skills with the ability to interact with tech folks, business stakeholders, clients, etc." "Excellent written and oral communication skills, team oriented mindset, attention to detail" "Ability to work effectively in a fast-paced (sometimes chaotic) environment while maintaining a sense of perspective." "Ability to adapt to new situations, solve problems on the fly, and communicate with those around you. Teamwork and scrappiness required." "A shared passion and curiosity for making change. This includes comfort with ambiguity, a restlessness that resists the status quo, and a commitment to quality that ensures we’re always making progress." "Empathy, communication, respect, and the ability to act as a role model at Blue State" These are skills/qualities. Could be under Skills. Requirements could be the experience bullet. But we can combine into one Requirements section with both experience and skills. However we have separate headings allowed: Requirements, Qualifications, Skills. We need to decide. We also have Benefits: list under "What we offer". That's benefits. Pay: The salary range: "$78,500–87,500; compensation will be commensurate with experience." The instruction: do NOT include Pay section if it contains filler like "commensurate with experience" only? Actually they say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range, so we can include Pay section with that range. Even though it also says compensation will be commensurate with experience, that's okay; we still have specific range. Schedule: Not mentioned explicitly. There's hybrid model, remote work flexibility, but not a schedule like full-time/part-time. No explicit schedule. So we should not create Schedule section. We also need to include maybe a short

for metadata like Job ID etc. There's none. We must remove boilerplate: evergreen note, LinkedIn note, application instructions, EEO, privacy policy, accommodation request, etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to include the company description, team description, responsibilities list, benefits list, pay range, requirements/skills list. We need to format using

headings,

• for lists,

  for prose. We must not repeat job title as heading. Let's craft sections:

  About the role

  Help run digital projects transforming the way people engage. As a Technical Project Manager, you’ll jump right in, interacting with clients, collaborating with diverse teams of UXers, Designers, Strategists, and Developers, leading website development, strategy and technical consulting projects from start to finish. You’ll help turn progressive ideas into actionable tactics, timelines, budgets, and deliverables.

  Blue State is a purpose‑driven agency that partners with leading causes, brands, and campaigns to create real change—from AARP and Doctors Without Borders to Amnesty International and Oxfam. Led by creative and analytical minds from the political, nonprofit, and brand worlds, Blue State is an independent agency with offices in the US and London.

  You’ll be part of the global Project Management team and work with a cross‑disciplinary team of Account Leads, Designers, Developers, Strategists, and other creative folks to get the job done.

  That seems good.

  Responsibilities

  • Scope, define, estimate, and manage budgets and timelines for strategy, website redesign & platform focused projects
  • Work with teams to define product specifications and functional requirements
  • Support senior members of the team in managing client relationships and coordination of internal creative and delivery teams
  • Manage operational aspects of projects, including communication of client needs to team and vice versa as well as internal team resourcing and financial health tracking
  • Lead project status meetings and updates with internal teams and clients
  • Manage multiple website build projects simultaneously and understand project priorities in the context of agency and client expectations
  • Minimize exposure to risk on a project by identifying potential scope creep and working with internal teams and client to mitigate this risk
  • Manage and participate in testing and quality control for all deliverables
  • Lead post project assessments and make recommendations for future projects or project optimization
  • Ensure project documents are complete, current, and archived appropriately

  Requirements

  • 2+ years of professional experience as a technical project manager with experience in digital strategy and managing agile website development projects, specifically WordPress or Drupal builds

  Skills

  • Strong communication skills with the ability to interact with tech folks, business stakeholders, clients, etc.
  • Excellent written and oral communication skills, team‑oriented mindset, attention to detail
  • Ability to work effectively in a fast‑paced (sometimes chaotic) environment while maintaining a sense of perspective
  • Ability to adapt to new situations, solve problems on the fly, and communicate with those around you; teamwork and scrappiness required
  • A shared passion and curiosity for making change, including comfort with ambiguity, a restlessness that resists the status quo, and a commitment to quality that ensures continual progress
  • Empathy, communication, respect, and the ability to act as a role model at Blue State

  Benefits

  • Unlimited time‑off (inclusive of sick, personal, and vacation days)
  • $1,000 annually in professional development funds
  • Competitive health, dental, and vision insurance
  • Inclusive family planning coverage, including fertility, surrogacy, and adoption benefits
  • Flexible and health savings accounts
  • 401K & employer match
  • Generous paid holiday schedule
  • 12‑week fully‑paid parental leave for all parents‑to‑be
  • Short‑term and long‑term disability insurance
  • Pre‑tax commuter benefits
  • Remote work flexibility

  Pay

  The salary range for this position is $78,500–$87,500; compensation will be commensurate with experience.

  We should not include Schedule section. Check for any duplicated content: we have covered all substantive info. We removed evergreen note, LinkedIn note, application instructions, EEO, accommodation request, privacy policy, etc. We kept hybrid model mention? Actually we didn't include hybrid model or vaccination requirement. Those are part of "We approach in-office working..." and vaccination requirement. Are those substantive? They are about work arrangement and policy. Should we include them? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info. Where to place? Could be under Benefits or maybe a separate section like "Work Arrangement". But we only have allowed headings list; we could add under Benefits or maybe under About the role. The hybrid model and vaccination requirement are substantive. We should include them. We have Benefits section already; we could add items about hybrid model and vaccination requirement there, but they are not benefits exactly. Could add a new section like "Work Arrangement" but not in allowed headings. However we could put them under Benefits as they are policies. But maybe better to add a section "Work Arrangement" but not allowed. The instruction says: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should fit the hybrid model and vaccination info into one of those sections, perhaps Benefits or About the role. Benefits already includes many items; we could add "Hybrid work model (remote flexibility with optional on‑site presence in NY/DC offices)" and "COVID‑19 vaccination requirement (including booster) with accommodations reviewed case‑by‑case". Those are more like policies than benefits but okay. We also have "Remote work flexibility" already in benefits; we can expand that. Let's adjust Benefits list to include hybrid model and vaccination. Add items: - Hybrid work model: remote work flexibility with optional on‑site presence for US staff within commuting distance of NY or DC offices; managers may require in‑person attendance as needed. - COVID‑19 vaccination requirement (including booster) for office access and events, with accommodations reviewed case‑by‑case. We'll incorporate. Now check if any other substantive info: "Managers retain discretion to require in-person attendance for folks on their discipline or client teams as necessary, including for those whose roles require them to be in person." That's covered. Also "To enter our US offices or attend Blue State events, staff and visitors must be fully vaccinated against COVID-19, including with a booster shot when eligible. Exceptions for protected grounds will be reviewed on a case-by-case basis." Already covered. Now ensure we didn't miss any responsibilities: we have all. Check if any other sections like "Qualifications" maybe we could combine experience there. But we have Requirements and Skills; that's fine. Now ensure we didn't include any boilerplate like "Even if you don’t think your current skill set checks every box below, but this role seems to align with your strengths, we want to hear from you." That's encouraging but maybe considered boilerplate? It's part of the posting encouraging applicants; it's substantive? It's more of a call to action. The instruction: remove application instructions. This is not exactly application instruction but encouraging to apply. Might be considered boilerplate? Safer to remove. Also remove "At Blue State, diversity is a necessity, not a nice-to-have..." That's EEO statement; remove. Also remove "Blue State is committed to creating an inclusive and accessible application and interview process..." remove. Also remove "If you would like to request a reasonable accommodation..." remove. Also remove "Your privacy is important to us..." remove. Thus final HTML includes sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Make sure to use proper HTML