Human Resources Generalist

We need to output HTML fragment with sections: headings

for sections like 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. 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. We need to parse the description. Key sections: - Description: includes location requirement (Mountain, Arizona, or Pacific time zone; not available to California residents). Also mission statement. - About The Role: description of role. - What You’ll Do: bullet list of duties (Talent Acquisition and Full-Cycle Recruiting, Onboarding and Employee Lifecycle, Employee Relations and People Support, Compliance and Multistate Support, Benefits, Leave, And People Programs, Payroll Backup Support, Process Development and Continuous Improvement). This is a list of duties. - Requirements: bullet list of qualifications. - Nice to Have: bullet list (optional). Could be considered as "Preferred Qualifications" or "Nice to Have". Might be included under Requirements or separate? The instruction says use sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Could treat "Nice to Have" as part of Requirements or maybe as "Qualifications". But we need to avoid thin sections. Could combine Requirements and Nice to Have into a single Requirements section with sub-bullets? However they ask to use

  • for any list of duties/requirements/benefits. So we can have a Requirements section with two sub-lists? But we cannot nest headings inside
    . Could just list all requirements (including nice-to-have) as bullet points, maybe differentiate with text? But they said preserve ALL substantive information; we can keep Nice to Have as a separate subsection but not as a heading? Could embed as a paragraph: "Nice to have: ..." but that would be prose. Better to keep as a separate section titled "Preferred Qualifications" (which maps to Qualifications). The instruction says we can use headings like Qualifications. So we can have a section

    Qualifications

    containing the Required and Nice to Have bullet lists. Or we could have Requirements and Qualifications separate but that may be thin. Better to combine. Benefits: The posting lists benefits under "The Holon Way": Base salary of $75-80k base, Unlimited PTO, Flexible schedules, Remote-first culture, Full suite of benefits (health, dental, vision, life, disability), 401(k) with company match, Space for self-care, Room to grow, Team that celebrates wins, etc. Also mentions base salary range. So we have Pay and Benefits and Schedule info. Pay: Base salary $75-80k base. Schedule: Flexible schedules that work with your life, Remote-first culture. Benefits: Unlimited PTO, Full suite of benefits (health, dental, vision, life, disability), 401(k) with company match, Space for self-care, Room to grow, Team that celebrates wins, etc. We need to include sections only if posting has real specific content. It does have Pay (salary range), Benefits (list), Schedule (flexible schedules, remote-first). So we can include those sections. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, equal opportunity, commitment to DE&I, etc. The posting includes "Our Commitment to DE&I" and "Diversity, equity, and inclusion aren’t buzzwords here..." That's EEO boilerplate; we should remove it. Also "If you’re passionate about our mission but don’t meet every qualification, we still encourage you to apply." That's application encouragement; maybe considered boilerplate? It's not exactly EEO but could be considered generic encouragement. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "If you’re passionate..." is more like encouragement to apply; could be considered application instruction? It's not exactly instruction to apply but encourages. Safer to remove it. Also "Ready to do work that matters, on a team that sees you? Apply now. Let’s build something extraordinary together." That's application instruction; remove. Also "What Success Looks Like" section: could be considered as "Expectations" or maybe "Performance". Not a standard heading but we could incorporate into Responsibilities? It's basically outcomes. Could be a separate section but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "What Success Looks Like" to Responsibilities or maybe to a separate section like "Expectations" but not allowed. Better to incorporate its content into Responsibilities or maybe as a separate section "Expectations" but that would be a heading not in list; instruction says use

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

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but maybe we can also use other headings if needed? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we could still use other headings if needed, but better to stick to those. The "What Success Looks Like" could be considered part of Responsibilities (outcomes). We'll incorporate. Also "The Holon Way" includes benefits and culture; we already captured benefits, pay, schedule. Also includes "Space for self-care, because you can’t pour from an empty cup", "Room to grow in a high-impact, mission-driven startup", "A team that celebrates wins, learns from losses, and has your back". Those are cultural benefits; could be included under Benefits or maybe under a separate "Culture" but not needed. We'll include them under Benefits as bullet points. Now we need to produce HTML fragment only, no /, no markdown fences. We'll structure:

    About the role

    ... (prose summarizing About The Role paragraph)

    Responsibilities

    • ... each duty bullet
    ...

    Requirements

    • ... each required bullet
    ...

    Qualifications

    • ... nice-to-have bullets
    ...

    Benefits

    • ... benefits bullet points
    ...

    Pay

    Base salary range: $75,000–$80,000 per year.

    Schedule

    Flexible schedules that work with your life; remote‑first culture.

    We also need to include location requirement: "Must be based in the Mountain, Arizona, or Pacific time zone. This role is not available to California residents at this time." This is substantive info; could be placed under About the role or maybe a short paragraph after About the role. We'll include in About the role paragraph. We must not repeat job title as heading. The job title is "HR Generalist". Not used. We must not put Job ID/requisition numbers as headings; none present. We must preserve all substantive information; ensure we didn't drop any. Let's extract details. About The Role paragraph: "Holon Health is seeking an experienced HR Generalist with strong recruiting chops to support our growing workforce across the western United States. This role pairs full-cycle talent acquisition with hands-on generalist support, and it exists to give team members in the Mountain, Arizona, and Pacific time zones a responsive People partner in their own workday. You will own recruiting for western roles end to end, guide managers and new hires through onboarding and compliance, and serve as a first point of contact for employee questions and relations matters. You will also help build the People processes and structure needed to support our continued growth. This is a hands-on role for someone who can recruit with skill, exercise sound judgment on people matters, and bring order to a growing, multistate organization." We need to incorporate location requirement: "Must be based in the Mountain, Arizona, or Pacific time zone. This role is not available to California residents at this time." This is also in Description earlier. We'll include in About the role paragraph. Now Responsibilities: The "What You’ll Do" section includes multiple sub-sections each with bullet-like paragraphs. We need to convert each bullet into
    • . Let's list them: Talent Acquisition and Full-Cycle Recruiting: - Own full-cycle recruiting for western roles, including peer support (recovery coaches), case management, FP&A, growth, product and clinical positions. - Partner with hiring managers on role intake, requisition setup, and interview structure so expectations are clear before a search opens. - Source, screen, and assess candidates, and coordinate interviews and scheduling with a smooth, respectful candidate experience. - Build and maintain pipelines for recurring and high-volume roles. - Extend offers, coordinate pre-hire steps, and keep candidates informed throughout the process. Onboarding and Employee Lifecycle: - Guide new western hires through onboarding, including Paylocity setup, documentation, and first-week logistics. - Complete I-9 verification and E-Verify steps in line with federal and state requirements, coordinating authorized representatives for remote hires as needed. - Deliver a clear, welcoming new-hire experience through the first 90 days. - Manage offboarding and exit steps with care and consistency. Employee Relations and People Support: - Serve as a first point of contact for western employees on policies, benefits questions, and day-to-day People needs. - Support employee relations matters with documentation, follow-through, and sound judgment, partnering with People Operations and Operations leadership. - Coach managers on feedback, performance conversations, and corrective action, grounded in a trauma-informed, respectful approach. Compliance and Multistate Support: - Maintain compliance with employment laws across western states, including wage and hour, leave, pay transparency, and required postings. - Support state workforce and program compliance requirements, including in Arizona. - Assist with audits, recordkeeping, and accurate employee data in Paylocity. Benefits, Leave, And People Programs: - Support benefits enrollment, leave of absence (including parental and medical), and accommodation requests with discretion and clarity. - Contribute to engagement, retention, and internal mobility efforts for the western team. Payroll Backup Support: - Serve as a cross-trained backup for payroll continuity when the Payroll Specialist is out, helping keep the biweekly cycle on track. - Monitor the payroll calendar, send pre-processing reminders and review and prepare payroll inputs for accuracy, completeness and appropriate approvals. - Coordinate with Accounting and a designated payroll approver so that processing and submission always include a second reviewer, preserving appropriate separation of duties. - Escalate complex or time-sensitive payroll matters to the Payroll Specialist and Accounting. Process Development and Continuous Improvement: - Develop and maintain