People & Culture Generalist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: - About The Role (paragraph) - YOU WILL (list of duties) - YOU HAVE (list of qualifications/experience) - WORK PERKS (list of benefits) - Compensation Range (pay) - About Us (maybe not needed? It's about company, but not a required heading; we could include as About the company? Not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map: About the role: the paragraph "At Dig Inn, taking care..." etc. Responsibilities: the "YOU WILL" list. Requirements: maybe combine "YOU HAVE" (experience, qualifications). Could treat as Requirements. Qualifications: maybe same as Requirements? But we should not duplicate. Could treat "YOU HAVE" as Requirements/Qualifications combined. However we need to decide: The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can include multiple if content exists. We have content for About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. No explicit Skills section separate; but we could extract skills from YOU HAVE (communication, organizational, etc.) but that's more qualifications. Could create a Skills section listing those. But we must not invent filler. If we create Skills, we need actual content. We could pull out skills: "Strong organizational and time-management skills", "Clear and engaging written and verbal communication skills", "Ability to build effective relationships", "Sound judgment", "Proactive working style", "Comfort working in a fast-moving environment". Those are skills. So we could make a Skills section. But we must not create sections with placeholder text. So we need to ensure each heading has substantive content. We also have Schedule? Not mentioned explicitly; maybe hybrid work environment indicates schedule? Not explicit. So we should not create Schedule. We have Pay: Compensation Range $70,000-80,000 per year, plus bonus potential. Benefits: WORK PERKS list. We also have location requirement: must be based in one of core markets. That could be part of About the role or Requirements. Could include in Requirements. We need to strip boilerplate: EEO, legal, etc. Also remove "Additional Role Note" etc. Also remove "About Us" maybe not needed but could be considered About the role? It's about company; but we could keep as a paragraph under About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep About Us content as it's substantive about the company. But we don't have a heading for About Us; we could put it under About the role? Might be okay to add a paragraph after About the role heading. However the heading "About the role" is already used for the role description; we could add another heading "About Dig Inn" but not in allowed list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but they'd deviate from examples. Safer to stick to allowed headings and place About Us content under About the role or maybe as a separate paragraph without heading? But we need to use

for prose. So we can include About Us as a

after the About the role heading, maybe under same heading? Could be considered part of About the role? Might be okay. We must not repeat the job title as a heading. The job title is "PEOPLE & CULTURE GENERALIST". Already not used as heading. We must not put Job ID/requisition numbers as headings. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip: - "About Us Dig Inn is a growing fast-casual restaurant group..." (we keep) - "All of this adds up..." etc (keep) - "Dig Inn believes in the power of a shared table..." (keep) - "Candidates from all backgrounds are encouraged to apply." (EEO) -> remove. - "Additional Role Note ..." (maybe keep? It's about duties may change; it's substantive but maybe considered boilerplate? It's a note about job description flexibility. Could keep as it's substantive about role. But it's somewhat generic; but it's not EEO. Might keep. - "Dig Inn is proud to be an Equal Opportunity Employer..." remove. - Also remove "The duties of this position may change from time to time." Actually that's part of Additional Role Note; we could keep the note but maybe it's boilerplate. I'd keep it as it's about the role. We need to output only HTML fragment. Let's structure:

About the role

At Dig Inn, taking care of our people starts by staying close to our restaurants and the teams inside them. As a People + Culture Generalist, you’ll be a highly visible and trusted member of the People Team, supporting team members and leaders throughout the employee experience. This is a dynamic role for someone who enjoys variety, builds strong relationships, and is excited to take meaningful ownership across multiple areas of People + Culture. You may move from leading a search from kickoff through offer, to answering a team member’s question, helping a restaurant leader navigate a workplace concern, or improving a People process behind the scenes. You’ll work closely with restaurant leaders, Support Team members, and the broader People Team to provide thoughtful, practical, and people-first support. You can expect to spend multiple days each week in our restaurants, staying connected to our teams and understanding what they need firsthand. Because the best People support starts with being present, this role must be based in one of our core markets: New York City, Boston, Philadelphia, or DMV.

Then maybe a paragraph about About Us? Could add another

after that. But we might want to keep About Us as separate

without heading. Then

Responsibilities

• Serve as an approachable and trusted point of contact for team members and restaurant leaders.
• Support recruiting and hiring across restaurant and Support Team roles.
• Assist with employee relations matters, including documentation, investigations, and manager support.
• Coordinate key moments throughout the employee lifecycle, from onboarding and orientation through offboarding.
• Provide administrative support across payroll, benefits, leaves, and employee records.
• Help maintain compliance with employment practices, policies, and required documentation.
• Maintain accurate and confidential information across People systems.
• Support People Team programs, projects, and company-wide initiatives.
• Build strong relationships by spending time in our restaurants and staying connected to the needs of our teams.
• Bring flexibility, sound judgment, and a team-first mindset as business priorities and People needs evolve.

Then

Requirements

maybe combine qualifications and skills? But we have separate sections for Qualifications and Skills. Let's do:

Qualifications

• 2-3 years of experience in Human Resources, People Operations, recruiting, or another people-focused role.
• A genuine interest in growing within the People + Culture field and developing experience across multiple areas of HR.
• A people-first approach and a strong desire to help others.
• Strong organizational and time-management skills, with the ability to balance multiple priorities.
• Clear and engaging written and verbal communication skills.
• The ability to build effective relationships with team members and leaders at every level of the organization.
• Sound judgment and the ability to handle sensitive and confidential information with care.
• A proactive working style and the ability to think independently while solving problems collaboratively.
• Comfort working in a fast-moving environment where priorities may evolve.
• Experience working with Paycom HRIS or Greenhouse ATS is a plus.
• Experience supporting hourly or restaurant teams is a plus.
• Spanish-language skills are a plus.
• The ability to travel regularly between Dig restaurants and work onsite multiple days each week.

But we also have Skills section maybe separate: we could extract skills from qualifications: organizational, time-management, communication, relationship building, judgment, proactive, fast-moving. However those are already in qualifications. To avoid duplication, we could keep Qualifications only and not have Skills. But the instruction allows Skills heading if we have content. We could create Skills section listing specific skills: "Strong organizational and time-management skills", "Clear and engaging written and verbal communication skills", "Ability to build effective relationships", "Sound judgment", "Proactive working style", "Comfort working in a fast-moving environment". However those are already in qualifications; duplication might be considered repeating detail but not summarizing away. It's okay to repeat? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Repeating is not summarizing away; it's preserving but could be considered duplication but not prohibited. However better to avoid duplication to keep concise. But we need to decide if we want Skills section. The posting does not have a separate "Skills" heading; it's embedded in qualifications. So maybe we should not create a Skills section because there is no explicit Skills section in the posting. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Since there is no explicit Skills section, we should not create one. So we will omit Skills. Thus we have About the role, Responsibilities, Qualifications (or Requirements), Benefits, Pay. We need to decide heading for qualifications: Could be "Requirements" or "Qualifications". The posting uses "YOU HAVE" which is qualifications/experience. We'll use

Qualifications

. Now Benefits: WORK PERKS list. We need to output as

• for each. Pay: Compensation Range $70,000-80,000 per year, plus bonus potential. We should put that in a

  under

  Pay

  . Now we need to ensure we removed boilerplate: EEO, Additional Role Note? Let's see if we should keep Additional Role Note. It says: "Additional Role Note The duties of this position may change from time to time. Dig Inn reserves the right to add or modify duties and responsibilities based on the evolving needs of the business. This job description is intended to describe the general nature and level of work being performed and is not intended to be all-inclusive." This is somewhat generic but still substantive about the role's nature. Could be considered boilerplate but it's about the job description. I'd keep it as a paragraph under About the role maybe? But it's not about the role specifics; it's a disclaimer. The instruction says remove duplicated lines, and application instructions. This is not application instructions. It's a note about job description. Might be considered boilerplate but not explicitly listed to remove. However it's generic; but it's still substantive info about the role's flexibility. I'd keep it as a

  under About the role after the initial paragraph. Also "About Us" paragraph we keep. Now we need to ensure we didn't include any navigation/footer etc. Now produce HTML. Let's craft:

  About the role

  At Dig Inn, taking care of our people starts by staying close to our restaurants and the teams inside them. As a People + Culture Generalist, you’ll be a highly visible and trusted member of the People Team, supporting team members and leaders throughout the