Director of Data & Analytics

We need to output HTML fragment with sections: About the role? Actually we have "About Reingold" description. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to decide which sections to include based on content. We have: - About Reingold (company description) maybe "About the role"? Actually "About Reingold" is about company, not role. Could be "About the role" but we have description of role later. We could combine company description under "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only when posting has real specific content. We have content: - About Reingold (company overview) – could go under "About the role"? Might be better as a paragraph 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 paragraph before headings. We can include a

for company overview. Then we have "Essential Functions:" list – that is responsibilities. So we can have

Responsibilities

with

• items. Then we have "This role is a good fit for someone with these qualifications, experience and skills:" then "Required Qualifications:" list, then "Preferred Qualifications:" list. Could combine under

  Requirements

  or

  Qualifications

  . The instruction includes both Requirements and Qualifications as possible headings. We need to decide. Since they list Required Qualifications and Preferred Qualifications, we could use

  Qualifications

  and inside have required and preferred maybe as subheadings? But we cannot add extra headings beyond those? Not prohibited but we should follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We could have

  Requirements

  for required qualifications, and

  Preferred Qualifications

  maybe not in list but could be considered a section. However "Preferred Qualifications" is not in the example list but could be considered under Qualifications. Safer: Use

  Qualifications

  and inside we can separate required and preferred using

  or . But we need to preserve all substantive information; we can list required and preferred as separate

  with headings inside maybe . That's okay. Then we have "Supervisory Responsibilities:" – could be part of Responsibilities or a separate section? Might be included under Responsibilities. Then "Work environment and physical requirements:" – could be under Requirements or maybe a separate section like "Work Environment". Not in list but we could include under Requirements. Then "Additional Information:" includes salary range, benefits, etc. So we need Pay and Benefits sections. We have salary range: base salary $110,000-$175,600. Also mention budgeted starting salary in lower half. Also mention full-time employees eligible for comprehensive health and wellness benefits, 401(k) employer contributions and matching, and other benefits. Thus we can have

  Pay

  with

  containing salary range and note about starting salary.

  Benefits

  with

  listing health and wellness benefits, 401(k) employer contributions and matching, other benefits. Schedule: we have hybrid role requiring at least two days per week on site. So we can have

  Schedule

  with

  describing hybrid schedule. We also have "Work environment and physical requirements:" which could be under Requirements or maybe a separate section like "Work Environment". Not in list but we could incorporate into Requirements. We must remove boilerplate: EEO, equal opportunity, scam warning, legal, cookie/navigation, application instructions, etc. Also remove lines like "This job description is not designed to cover..." etc. Also remove "Additional Information:" heading? We need to keep substantive info but discard the heading itself if it's just a label. We'll extract the substantive info. We must not invent or summarize away detail. Keep all specifics. Let's extract content: Company overview paragraph: "Reingold is a full-service marketing and creative firm in Alexandria, VA. For more than 40 years, we’ve been driven by a simple mission: to help organizations –– whether in the government, nonprofit, or business sector –– as they strive to make the world a better place. We hire top-notch talent to develop and launch compelling, inventive communications campaigns, leveraging the latest technology and digital media strategies that enable our clients to meet their audiences where they are.We’re proud to say we’ve built a team of curious, passionate pros — from marketers and tech wizards to designers and strategists — who love what they do and bring their A-game every day. We take our work seriously, but not ourselves. We believe great ideas come from collaboration, humor, and a little bit of fun along the way.When you work at Reingold, you get more than a job, you get a community. We offer competitive salaries, a comprehensive benefits package, a dynamic hybrid work environment, a vibrant workplace and growth opportunities in a variety of specialty areas. That means when we find great people (and they find us), they stick around for the long term." Then role intro: "That's where you come in. We’re looking for a data and analytics leader to own the architecture, modeling, and measurement strategy behind our client engagements. This role requires a strong analytical mindset, excellent problem-solving skills, and the ability to effectively communicate complex data-driven insights to colleagues, clients and stakeholders.This is a hybrid role, requiring at least two days per week on site at Reingold’s headquarters in Alexandria, VA." Then Essential Functions list (responsibilities): - Understand clients’ goals and translate them into analytics strategies for measuring the effectiveness of digital experience and marketing initiatives, as well as analyze data to provide insights into the performance thereof. - Own the data architecture behind client engagements — warehouse design, dimensional modeling, and pipelines — making the calls on how data is structured, governed, and consumed. - Design and document digital analytics solutions, working closely with developers, content creators, and outreach specialists to ensure that requirements and dependencies are delivered accurately and in accordance with digital analytics best practices. - Spearhead the adoption of analytics best practices across the organization, with a focus on scalability and data privacy. - Bring data to life through compelling storytelling, turning complex analytics findings into clear, actionable narratives that resonate with a range of audiences, from technical teams to executive stakeholders and clients. - Lead the rollout of analytics solutions on clients’ digital platforms using tag managers or similar technologies (e.g., Adobe Launch/Data Collection, Tealium IQ, Google Tag Manager) and, where applicable, manage integrations that include various data sources. - Integrate AI into the daily workflow where appropriate, to streamline processes and strengthen insights. - Help internal teams and clients feel confident in data-driven decisions by presenting insights in a way that is engaging, persuasive, and easy to act on. Then "This job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the employee. Duties, responsibilities and activities may change, or new ones may be assigned at any time." This is boilerplate; we should remove. Then "This role is a good fit for someone with these qualifications, experience and skills:" then "Required Qualifications:" list: - 8+ years building and owning data and analytics solutions, including meaningful time in a senior or lead capacity. - Visualization depth in Looker, Power BI, or Tableau. - Experience in analyzing data trends and generating presentations and reports to inform data-driven decision-making. - Demonstrated data modeling judgment — you’ve designed schemas other people had to live with, and can walk us through the architectural tradeoffs you made. - Experience with automating data collection and reporting through cloud platforms, such as Google Cloud Platform, Snowflake or Amazon Web Services. - Working knowledge of digital analytics and tag management platforms (GA4, Adobe Analytics/CJA, Google Tag Manager, Adobe Launch, Tealium). - Experience in driving data governance and reporting standards across multiple initiatives. - Excellent oral and written communications skills. - A bachelor’s degree in marketing, communications, computer science, math, or a similar field (or equivalent work experience). - Strong SQL and Python — you write production-quality code, not just ad hoc queries — and hands-on experience with a cloud data platform (Google Cloud and BigQuery preferred; Snowflake, Databricks, or AWS equivalents welcome). Then "Preferred Qualifications:" list: - A knack for data storytelling, with the ability to go beyond charts and dashboards to craft "so what" narratives that connect with both technical and non-technical audiences. - Comfort and experience presenting analytics findings to clients and senior stakeholders, including the ability to walk people through your thinking, address questions, and build alignment around a path forward. - Working knowledge of JavaScript, HTML, and CSS, with a strong technical understanding of website architecture and mobile app instrumentation. - Experience with site and marketing testing (Adobe Target, Optimizely), data privacy technologies (cookie banners, etc.) - Experience with other Adobe platforms like AEP, AEM, Audience Manager, Media Optimizer, Campaign preferred. - Experience with Salesforce Data 360 (formerly Data Cloud). - Experience with middleware tools like Mulesoft or Apigee. Then "Supervisory Responsibilities: This position may supervise early-career data and analytics staff, with responsibility for their day-to-day work, development, and growth." Then "Work environment and physical requirements: Prolonged periods sitting at a desk and working on a computer. Must be able to lift up to 15 pounds" Then "Additional Information: The base salary range of $110,000-$175,600 represents the low and high of the company’s pay range for this position. The budgeted starting salary is in the lower half of the base salary range. Individual compensation will vary based on experience, skills, qualifications, internal equity, and business needs. Full-time employees are eligible for comprehensive health and wellness benefits, 401(k) employer contributions and matching, and other benefits." Then EEO etc boilerplate to remove. Thus we need sections: - Maybe a

  for company overview and role intro (combined). Could be two paragraphs. - Responsibilities (

  Responsibilities

  ) with
  . - Qualifications (

  Qualifications

  ) maybe split into Required and Preferred using or separate
  with headings. We could also have

  Requirements

  for required qualifications and

  Preferred Qualifications

  for preferred. But the instruction list includes Requirements and Qualifications as separate possible headings. Might be better to use Requirements for required, Qualifications for preferred? But they are similar. Let's decide: Use

  Requirements

  for required qualifications, and

  Preferred Qualifications

  for preferred (though not in example list but acceptable). However instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. So we can add Preferred Qualifications as a heading. We also have Supervisory Responsibilities - could be part of Responsibilities. Work environment and physical requirements - could be part of Requirements or a separate section like "Work Environment". Not in list but we could add under Requirements as a bullet. Pay and Benefits sections. Schedule section. Let's craft HTML. We'll start with a

  for