Director, Analytics (Evergreen)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Remove boilerplate, navigation, EEO, etc. Keep substantive info. We need to parse the posting. Key parts: - Intro: "Interested in joining Blue State's Media Team? Submit your application here..." That's application instruction, remove. - "Please note: this is an 'evergreen' job post (i.e. not an active job post), but your expression of interest matters to us. While interviews aren't ongoing, we're excited to connect with talented individuals who share our commitment to Blue State's mission. If you came across this job via LinkedIn, please note that it is an evergreen role; Linked In does not differentiate, but we prefer to." This is meta, maybe drop. - "What to know We're looking for a Director of Analytics to lead and evolve our data practice at a pivotal moment — for Blue State, for our clients, and for the nonprofit and advocacy sector. Philanthropy and civic engagement are being reshaped by new technologies and shifting donor behaviors, and this person will help us navigate that with clarity, rigor, and creativity. You'll lead a team of talented analysts, actively coaching and developing them while staying hands-on in client work. You're as comfortable commanding a room with C-suite clients as you are in the weeds of a measurement framework, and you know how to make data feel like strategy rather than reporting. You work fluidly across engineering, strategy, paid media, and account teams to build integrated solutions. You're self-sufficient, you develop new tools and frameworks that push our offerings forward, and you're genuinely excited about what AI and emerging technologies can bring to analytics work. Above all, you understand not just how to measure programs, but why those choices matter for organizations trying to grow revenue, deepen supporter relationships, and create lasting impact. If that's you, we'd love to hear from you." That's description of role, could be "About the role" or "Responsibilities". We'll treat as "About the role". - "The company Blue State is a purpose-driven agency. We partner with leading causes, brands, and campaigns and create real change. From AARP and Doctors Without Borders to Amnesty International and Oxfam, we transform how brands and causes raise money, influence policy, build platforms, and grow communities of supporters. Led by the most creative and analytical minds from the political, nonprofit, and brand worlds, Blue State is an independent agency in the US and London." That's about company, could be "About the company". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Could include "About the role" and maybe "About the company" not in list; but we could incorporate into About the role or maybe skip. The instruction says use headings for those specific section names; we should not create other headings. So we can put company description under About the role or maybe under Responsibilities? Probably better to put under About the role. - "A day in the life Manage and mentor a team of analysts, working with individuals to craft goals and professional development plans, providing regular feedback and guidance, addressing training and onboarding needs, and conducting annual performance reviews.Set a vision for the smart use of data to improve outcomes for our clients. Chart a path for team growth, including but not limited to: quality of work, staffing and hiring, cross-team integration, team goals and utilization, and identification of product and project opportunities.Foster a team culture grounded in collaboration and enthusiasm. Contribute to a portfolio of clients and projects, providing strategic leadership and expertise in driving data strategy across multiple touch points. Help pursue new business and maintain the health of existing accounts. Assist with regular development and review of pitches and proposals. Develop scalable industry best practices and product offerings for the Analytics Team and across departments. Drive cross-client and company-wide innovation as well as strategic, programmatic, and procedural improvements.Drive understanding of how analytics programs fit into broader programs, and pursue a commitment to improving ROI for our clients by working closely with other teams to ensure that all pieces are moving together to accomplish client goals.Develop and deliver effective and persuasive presentations demonstrating the value of our work for client teams, business development, and partners. Uncover core insights from data.Speak publicly on behalf of the company at events, in publication, and in the media." That's responsibilities list. Could be under Responsibilities heading. - "What we offer Unlimited time-off (inclusive of sick, personal, and vacation days)$1,250 annually in professional development fundsCompetitive health, dental, and vision insuranceFlexible and health savings accounts401K & employer matchGenerous paid holiday schedule12-week fully-paid parental leave for all parents-to-beShort-term and long-term disability insurancePre-tax commuter benefitsRemote work flexibility We approach in-office working with a hybrid model. On-site presence is welcome for US staff who are within commuting distance of the NY or DC office. 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 benefits and schedule info. We have Benefits and Pay and Schedule sections. Benefits: list items. Pay: salary range. Schedule: hybrid model description. - "The salary range for this position is $125,000-$150,000; compensation will be commensurate with experience." That's pay info. We should include Pay section with that sentence. However "compensation will be commensurate with experience" is filler? It's a phrase but it's actual statement. The instruction says: do NOT 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. It says do NOT emit a heading followed by filler/placeholder text like "commensurate with experience". That seems to indicate we should not include that phrase if it's just filler. But the sentence includes both a range and that phrase. We could keep the range and maybe drop the phrase? But we must preserve ALL substantive information; do NOT invent or summarize away detail. The phrase "compensation will be commensurate with experience" is substantive? It's basically saying salary depends on experience, which is implied by a range. Might be considered filler. The instruction says not to emit a heading followed by filler/placeholder text (e.g. "commensurate with experience"). That suggests if the only content under Pay is that phrase, we should not create Pay section. But we have actual range, so we can include Pay section with the range, maybe omit the phrase. However we must preserve ALL substantive information; removing that phrase might be losing some nuance but it's arguably redundant. I'd keep the range and maybe drop the phrase to avoid filler. Could include both but the phrase is filler; better to omit. - Schedule: hybrid model description. That's substantive. - Benefits: list items. - Requirements/Qualifications/Skills: The posting includes "Some things we’re looking for" then a list of qualifications. We need to split into Requirements, Qualifications, Skills maybe. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we have headings for each; we could use Requirements for mandatory experience, Qualifications for preferred, Skills for technical skills. Let's parse. From "Some things we’re looking for": - 9+ years of experience in digital analytics with direct experience working with CRM data, paid media analytics, web analytics suites such as Google Analytics, A/B testing solutions such as Optimizely (or equivalent), and data analysis in Excel or Google Sheets. - Experience in mass marketing with fundraising, advocacy, or ecommerce preferred. - Experience with digital martech is a plus! - You are an expert in SQL, and feel comfortable managing, optimizing, and troubleshooting in a data warehouse environment, such as BigQuery or Snowflake. - The ideal candidate will have experience in data modeling, familiarity with ETL processes, and deep expertise in leveraging large datasets to enable strategic decision-making. - Strong people and team management skills. You are able to identify and solve issues, and escalate when appropriate. You resolve conflicts constructively. You proactively identify and communicate growth goals for yourself and others. You are an exceptional listener. You build teams with a recognizable culture of cooperation. You stay at the forefront of AI and emerging technologies and their application to marketing analytics work — experimenting with new tools, developing a point of view on where they add genuine value, and building team fluency and confidence with them over time. - Brings an informed perspective on the nonprofit and advocacy sector — understanding the pressures, opportunities, and structural shifts shaping philanthropy and civic engagement today, and translating that context into smarter measurement strategies and more relevant client counsel. - Excellent communication skills. Ability to interact with all levels of end users, including executive leadership and day-to-day practitioners, and colleagues from across departments.. Strong collaborator and relationship builder. - Ability to adapt to new situations, solve problems on the fly, stay organized, and clearly 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. At Blue State, diversity is a necessity, not a nice-to-hack. We encourage those from underrepresented communities — women, people of color, LGBTQIA+, immigrants, those with disabilities and people at all the intersections in between — to apply. Even if you don’t think your current skill set checks every box, but this role seems to align with your strengths, we want to hear from you. - Blue State is committed to creating an inclusive and accessible application and interview process. If you would like to request a reasonable accommodation for a disability, including the use of AI tools throughout the hiring process, please contact us at recruiting@bluestate.co with the subject line: Accommodation Request to get started. Your privacy is important to us. You can find out more information on how we handle your data for recruiting purposes in our Privacy Policy for Recruitment. The last paragraphs are EEO/accommodation/privacy boilerplate; we should remove. Thus we need to extract substantive qualifications. We could create sections: - About the role (intro + company description) - Responsibilities (day in the life list) - Requirements (maybe the mandatory experience: 9+ years, CRM data, paid media, web analytics, A/B testing, Excel/Sheets, SQL expertise, data warehouse, data modeling, ETL, people management, nonprofit sector perspective, communication skills, adaptability, passion for change, empathy, etc.) - Qualifications (preferred: mass marketing fundraising/advocacy/ecommerce, digital martech plus, AI emerging tech, etc.) - Skills (maybe technical: SQL, BigQuery/Snowflake, data modeling, ETL, Excel/Sheets, Google Analytics, Optimizely, etc.) But we might combine. Given instruction to prefer few substantive sections over many thin ones, maybe we combine Requirements and Qualifications into one "Requirements" section, and Skills into another? Or combine all into "Requirements". But we have headings list; we can use only those we need. Let's decide: - About the role: includes intro and company description. - Responsibilities: day in the life bullet list. - Requirements: combine mandatory experience and qualifications (including preferred). Could be a list. - Benefits: list. - Pay: salary range. - Schedule: hybrid model description. We should not include Skills separate if we merge into Requirements. Now we need to format using

for each section heading, then content:

for prose,

• for lists. We must not repeat job title as heading. No Job ID. We must strip boilerplate: evergreen note, application instructions, LinkedIn note, EEO/diversity