Research and Evaluation Associate

We need to output HTML fragment with sections: About the role? The posting includes a Position Summary paragraph. Could treat that as About the role? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Position Summary (could be About the role) - Responsibilities (list) - Qualifications (list) - Advantages and Learning Opportunities (maybe Benefits? but they say Benefits: None; but there is a section "Advantages and Learning Opportunities" which is like benefits/learning. Could treat as Benefits? But they said never create Benefits sections unless posting actually states them. The posting says "Benefits: None". So we should not create a Benefits section because it's none. However we have "Advantages and Learning Opportunities" which is substantive. Could we treat that as a section like "Learning Opportunities"? Not in the list of allowed headings. The allowed headings are examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly add other headings if needed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use others if needed? It says "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 other headings, but the examples given are typical. Safer to stick to those headings. We have content for About the role (Position Summary). Responsibilities (list). Qualifications (list). Possibly Skills? The qualifications include skills like Excel, Tableau, etc. Could separate Skills section? But we already have Qualifications covering education/experience and skills. Could we split? Might be thin. Better to keep Qualifications as one section covering both education/experience and skills. Pay: posting includes "Compensation: $18-20/hour". That's pay info, so we should include Pay section. Schedule: posting includes "Hours per Week: Approximately 20-25hours/week, from October through December". Also "This is a part-time “at-will” position for the period October through December, with the potential for extension based on organizational needs." So we have schedule info. So we should include Schedule section. Benefits: posting says "Benefits: None". According to instruction, never create Benefits sections unless posting actually states them. It does state them (none). But they say never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Benefits: None. However they also say "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "None" is not filler? It's a specific statement. Could we include Benefits section with

  None

  ? Might be okay. But they also say "Prefer a few substantive sections over many thin ones." Benefits: None is thin. Might be better to omit Benefits section because it's not substantive. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but we could still choose not to include if we think it's not substantive? The instruction says "include a section ONLY when the posting has real, specific content for it". "Benefits: None" is real specific content. So we should include Benefits section with that content. However they also say "Prefer a few substantive sections over many thin ones." Benefits: None is thin but still specific. I'd include it. Also we have "Advantages and Learning Opportunities" which could be considered as part of Benefits or maybe as a separate section like "Learning Opportunities". Not in the list but we could incorporate into Benefits? But Benefits already says None, which contradicts advantages. Actually the posting says Benefits: None, then later "Advantages and Learning Opportunities". So they differentiate: benefits (like health insurance) none, but advantages (learning opportunities) exist. So we could keep Benefits section as None, and also include a separate section maybe "Advantages" but not in allowed headings. Could we treat Advantages as part of "About the role"? Or maybe we could incorporate into Responsibilities? Not ideal. Given the instruction to prefer few substantive sections, maybe we combine Advantages and Learning Opportunities into a section called "Benefits" despite the line saying Benefits: None? That would be contradictory. Better to keep Benefits: None as a short paragraph, and also include a section for "Advantages and Learning Opportunities" using a heading like "Advantages". But the instruction only gave examples; not strict. I'd include a heading "Advantages and Learning Opportunities" as

  . It's specific content. Thus sections: About the role (Position Summary), Responsibilities, Qualifications, Pay, Schedule, Benefits (None), Advantages and Learning Opportunities. Check for duplicated lines: The posting repeats "This is a part-time “at-will” position for the period October through December, with the potential for extension based on organizational needs." and also earlier "This is a part-time “at-will” associate position reporting to the Director of Research and Evaluation." and later "This is a part-time “at-will” position for the period October through December, with the potential for extension based on organizational needs." We should preserve all substantive information but avoid duplication. We can combine. We need to remove boilerplate: EEO, equal opportunity, vaccination requirement? Vaccination requirement is substantive? It's about employment condition. It's not boilerplate? It's a requirement. Should we keep? It's not navigation/legal/EEO/equal-opportunity/scam-warning. Vaccination requirement is a condition of employment, could be kept. It's under "As part of our commitment to maintaining a safe and healthy workplace..." That's substantive. We'll keep it maybe under Qualifications or a separate section? Could be part of Qualifications? It's a requirement. Might be better to include under Qualifications as a bullet? But it's not a qualification per se. Could be a separate section "Requirements". The instruction includes Requirements as a possible heading. We have not used Requirements yet. We could put vaccination requirement under Requirements. Also the requirement to meet applicable vaccination requirements. Also maybe other requirements like ability to work independently etc are in Qualifications. So we can have Requirements section for vaccination requirement and maybe other mandatory conditions. Let's parse content: - Position Summary paragraph(s): "We are seeking a detail-oriented Research and Evaluation Associate to provide part-time analytical, data-management and reporting support across The Fresh Air Fund’s summer and school-year programs. The Associate will help manage recurring evaluation workflows-- from survey administration and data preparation through routine analysis, visualization and reporting-- and will contribute to emerging work related to participant retention, alumni-data infrastructure and long-term impact measurement. This is a part-time “at-will” associate position reporting to the Director of Research and Evaluation. The Associate will work within established R&E methods and protocols, allowing the Director to focus on evaluation strategy, research design, interpretation, organizational learning and decision support. This is a part-time “at-will” position for the period October through December, with the potential for extension based on organizational needs." We can combine into About the role. - Responsibilities: list bullet points (the long list). We'll output as

  • each. - Qualifications: list bullet points (education, experience, skills, etc). We'll output as
    • . - Requirements: maybe vaccination requirement and maybe commitment to mission? Actually commitment to mission is in Qualifications. Vaccination requirement is separate. Also maybe "Ability to work independently and collaboratively" is in Qualifications. So Requirements could just be vaccination requirement. We'll include as

      or

      ? It's a single statement. Use

      . - Pay: "Compensation: $18-20/hour". We'll output as

      $18-20/hour

      or maybe
      but single. - Schedule: "Hours per Week: Approximately 20-25hours/week, from October through December". Also mention part-time at-will Oct-Dec with potential extension. We'll combine. - Benefits: "Benefits: None". We'll output as

      None

      . - Advantages and Learning Opportunities: paragraph(s) about gain hands-on experience, contribute to meaningful evidence, build experience with retention, flexible part-time schedule, primarily NYC office occasional remote. We'll output as

      ...

      maybe also list? It's a paragraph. We must not include application instructions, EEO, etc. Also remove duplicated lines like "This is a part-time “at-will” associate position reporting to the Director of Research and Evaluation." and later duplicate. We'll keep only one instance. Now craft HTML. We'll start with

      About the role

      then

      ...

      . Then

      Responsibilities

      with each responsibility as
      • . Need to split the long list into items. Let's extract responsibilities from text: "Coordinate recurring survey administration and data-processing workflows across summer and school-year programs, including schedules, files, status tracking and follow-up. Prepare survey instruments, data structures and trackers; monitor response rates, missing information and other data-quality indicators. Process electronic and paper-based survey and observation data, including data entry or oversight of data entry during peak periods. Clean, match, merge, code and organize quantitative and qualitative data, completing systematic quality-control checks and documenting any issues. Conduct routine descriptive analyses, pre/post comparisons, subgroup summaries and qualitative coding using methods established with the Director of Research and Evaluation. Develop clear tables, charts, dashboards, presentation slides and routine program reports, including annual school-year and summer reporting and strategic-plan measurement. Support inventories of current measures, historical records and alumni reachability, and help document participant-to-alumni matching and data-stewardship workflows with R&E and IS&T. Provide research and production support for evidence reviews, measure scans, feasibility assessments and bounded analyses related to long-term outcomes. Maintain organized files, data dictionaries, codebooks, process documentation and quality-control checklists, and track R&E project milestones and review cycles. Maintain confidentiality and handle participant, alumni and staff information in accordance with applicable privacy, security, consent and data-use requirements. Other responsibilities as assigned." We'll make each as
      • . Qualifications list: "Relevant education, training or professional experience in psychology, sociology, education, public policy, public health, statistics, data analytics, or related fields. A college degree is not required. At least two years of relevant experience supporting research, evaluation, data analysis, program learning or a comparable applied function. Experience cleaning, organizing, analyzing and quality-checking quantitative data using Microsoft Excel or comparable tools. Experience working with survey data and summarizing findings accurately for nontechnical audiences. Experience with qualitative coding,