Data & IT Coordinator

We need to output HTML fragment with sections: About the role? The posting includes description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We have: - About the role: description paragraph about mission and role. - Responsibilities: bullet list under "Responsibilities Will Include" with subcategories: Data Systems and Reporting, IT, Servers, and Security, Web Forms and Data Tools, Salesforce Support. Should we break into subheadings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only top-level sections. Within Responsibilities we can have

• items. Could include nested? Probably just list items. - Requirements: maybe "Required Qualifications". That's qualifications. Also "Preferred Qualifications". Could combine as Qualifications section with required and preferred? But we have separate headings: Requirements, Qualifications, Skills. We need to decide what content fits each. We have "Required Qualifications" list. That's qualifications. Also "Preferred Qualifications". Could put under Qualifications. We have "Passion for addressing global climate change..." etc. That's also qualification. We have "Skills": maybe list of technical skills: SQL, Python, JavaScript, server administration, etc. Could extract from Required Qualifications. We have Benefits: detailed list. Pay: hourly rate $28.88. Schedule: Full-time 40 per week non-exempt position. Also mention flexible schedule with periodic in-person meetings. Location: Candidates must be based in Massachusetts. Could be part of About the role or maybe a separate section? Not in list; we could include in About the role paragraph. We must not include boilerplate like EEO etc. Remove equal opportunity employer lines. We must not include application instructions, links like "Learn more about us here!" maybe keep? It's not substantive? It's a link to drive. Might be considered navigation? Probably remove. We must preserve all substantive information. So keep description of mission, role, responsibilities, qualifications, preferred qualifications, benefits, pay, schedule, location. We must not repeat job title as heading. We must not include Job ID etc. We must not create sections with filler like "commensurate with experience". Not present. Now craft HTML. Structure:

  About the role

  ...

  Responsibilities

  • Data Systems and Reporting: Support All In Energy teams and external partners by configuring, monitoring, and quality-checking data imports, reports, and exports; produce regular reports on key program metrics; perform data updates, cleanup, and bulk uploads; implement changes to data infrastructure and systems for new and ongoing programs.
  • IT, Servers, and Security: Perform basic server administration, maintenance, and troubleshooting; document technical processes; support staff with basic IT and data security needs.
  • Web Forms and Data Tools: Develop and maintain web forms, scripts, and data intake, imports, and exports; work with team to translate program needs into technical solutions.
  • Salesforce Support: Help maintain data quality and consistency across Salesforce; provide ad hoc support including configuration changes, reports, data updates, troubleshooting.

  Qualifications

  • Experience working with data systems, databases, CRMs, and spreadsheets.
  • Experience with SQL, Python, JavaScript, or another programming language.
  • Ability to troubleshoot technical and data-related problems and develop practical solutions.
  • Experience with server administration, system maintenance, cloud infrastructure, or information security.
  • Strong attention to detail and commitment to data accuracy and quality.
  • Ability to learn new software, systems, and technical processes independently.
  • Strong organizational skills and ability to manage multiple priorities across programs and teams.
  • Ability to communicate clearly about technical issues with varying technical expertise.
  • Passion for addressing global climate change, equitable clean energy access, or economic and environmental justice.
  Maybe also include Preferred Qualifications as part of Qualifications? Could add a note: "Preferred qualifications include..." but we can add another
  under Qualifications with heading? But we cannot add extra headings besides allowed ones. Could embed preferred qualifications within same list, maybe label them. But we need to preserve all info. Could add a

  before list: "Preferred qualifications:" then list. Better: Keep Qualifications section for required, and add a separate

  Skills? But we already have Skills heading possible. Could put technical skills under Skills, and other qualifications under Qualifications. Let's parse: Required Qualifications list includes experience, SQL/Python/JS, troubleshooting, server admin, attention to detail, ability to learn, organizational skills, communication, passion. Preferred Qualifications list includes Salesforce experience, web forms, data imports/exports, external partner troubleshooting, Asana, language fluency. Skills could be technical: SQL, Python, JavaScript, server administration, etc. But we already have those in Required Qualifications. Might be redundant. Given instruction: Prefer a few substantive sections over many thin ones. So maybe combine Required and Preferred into Qualifications, and maybe Skills not needed. But we need to include Skills section only if there is real specific content. We could extract skills: SQL, Python, JavaScript, server administration, cloud infrastructure, information security, web forms, scripts, Salesforce, Asana, language fluency. That's substantive. Thus we could have:

  Skills

  • SQL, Python, JavaScript (or another programming language)
  • Server administration, system maintenance, cloud infrastructure, information security
  • Web forms and scripts development
  • Salesforce CRM
  • Data imports/exports, APIs
  • Project management tools (e.g., Asana)
  • Language fluency: Spanish, Portuguese, or other community languages (preferred)
  But we need to avoid duplication with Qualifications. Might be okay if we keep both but ensure not repeating same content verbatim. Could rephrase. Alternatively, we could have only Qualifications and Skills combined, but we need to follow instruction: use headings only when posting has real specific content. It does have qualifications and skills. So we can have both. Now Benefits: we have list. Pay: hourly rate $28.88. Schedule: Full-time 40 per week non-exempt; flexible schedule with periodic in-person meetings in Massachusetts. We could combine Pay and Schedule into one section? But headings separate. We'll include both. Now About the role paragraph: include mission and role description. Let's craft About the role:

  All In Energy is a nonprofit expanding access to climate solutions and green jobs across Massachusetts, working to accelerate an inclusive clean energy economy by connecting communities of color, non‑English speakers, and renters/landlords to energy‑saving programs and affordable renewable energy, saving families money, improving home health, and combating climate change while creating pathways into clean energy jobs for diverse talent. The Data Coordinator supports the data systems, infrastructure, and tools that enable these programs, working across teams and with external partners to maintain accurate data, build and maintain data intake and reporting tools, and support organizational technology systems.

  That captures. Now Responsibilities: we already have. Now Qualifications: maybe separate Required and Preferred as two lists with headings? But we cannot add extra headings beyond allowed. Could embed both in one list with labels. Better: Provide two

  paragraphs: one for Required Qualifications, one for Preferred Qualifications, each followed by

  . That's allowed because headings only for sections; inside we can have paragraphs and lists. Thus:

  Qualifications

  Required qualifications:

  ...

  Preferred qualifications:

  ...
  Now Skills: maybe we can omit if we feel it's redundant. But we have technical skills already in qualifications. Could still include Skills but risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe better to omit Skills section and keep Qualifications only. However we need to include Pay, Schedule, Benefits sections. So we will have About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Check if we have any content for Skills that is not covered elsewhere: language fluency, Asana, etc. Those are in Preferred Qualifications. So covered. Thus final HTML:

  About the role

  ...

  Responsibilities

  ...

  Qualifications

  Required qualifications:

  ...

  Preferred qualifications:

  ...

  Benefits

  ...

  Pay

  $28.88 per hour (full‑time, 40 hours/week, non‑exempt)

  Schedule

  Full‑time 40 hours per week with a flexible schedule and periodic in‑person meetings in Massachusetts.

  We also need to mention location: Candidates must be based in Massachusetts. Could add to About the role or Schedule. Add to Schedule paragraph: "Candidates must be based in Massachusetts." Now ensure we removed boilerplate: EEO lines, equal opportunity employer, etc. Also removed "Learn more about us here!" link, and the drive link. Also removed "Hours, Benefits, and Compensation: For a detailed list of benefits, go to bit.ly/AIEbenefits" but we kept benefits detail. We need to preserve all substantive information: benefits list includes flexible schedule, PTO details, health/dental/vision, FSA, EAP, 401k, stipends for workspace ergonomics, professional development, remote work, wellness, technology, provided work laptop. Also mention "Generous Paid Time Off package: 12 Vacation Days, 10 Sick/ Mental Health Time, 3 Floating Holidays, 13 Paid State and Federal Holidays, 1 Volunteer day, the week between Christmas and New Years off". Also "Health, Dental, and Vision insurance, Flexible Spending Account, Employee Assistance Program, 401k Retirement Plan". Also "Stipends for Workspace Ergonomics Furniture, Professional Development, Remote Work, Wellness, Technology Benefits, and a Provided Work Laptop". Also "Flexible schedule with periodic in-person meetings in Massachusetts". Already in schedule. Now ensure we didn't miss any: "Full-time 40 per week non-exempt position with an hourly rate of $28.88". Already. Now check for any other substantive: "We encourage candidates with a wide range of lived and professional experience to apply even if you don’t meet every qualification." That's motivational but maybe considered boilerplate? It's not a requirement; could be considered encouraging but maybe we can keep as part of Qualifications paragraph? It's not a specific qualification; it's a statement. Might be considered boilerplate? It's not EEO but it's encouraging. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those. It's more like encouraging statement. Could keep but maybe not needed. Safer to keep? It's substantive? It's not a requirement but it's about application. Might be considered application instruction? It's not instruction to apply. It's just encouraging. I'd keep it maybe as a p under Qualifications. But we already have Required and Preferred qualifications lists; we could add a p before them: "We encourage candidates with a wide range of lived and professional experience to apply even if you don’t meet every qualification." That's fine. Now check for duplicated lines: "Developing web forms and scripts, and developing