People and Culture Generalist

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only sections that have real specific content. The posting includes: About Jambalaya Group (maybe "About the role"? Actually "About Jambalaya Group" is about company, not role. But we can treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting includes: Position purpose, Primary Responsibilities, How You Will Work, How Success Will Be Measured, Requirements, Preferred experience includes..., Initial role expectations, Performance expectations. Also Benefits: "Full benefits package, including health, dental, and vision insurance; a 401(k) with an employer match; paid time off; and paid holidays." Also Work arrangement: Full time, remote within the United States. That could be Schedule? Actually schedule maybe remote, full time. Pay not mentioned. So we should not create Pay section. Benefits we have. Schedule maybe we can include work arrangement? The instruction: include a section ONLY when posting has real, specific content for it. Work arrangement is given: Full time, remote within the United States. That's schedule info. So we can create Schedule section with that. Benefits we have. Pay not present, so omit. Qualifications maybe same as Requirements? Could combine? But we have Requirements section. Qualifications maybe not separate; we could omit if no distinct content. Skills maybe part of Requirements. But we can still include Skills if we have specific skill list. The posting includes many skill-like items: consulting mindset, strong judgment, relationship-building, business acumen, comfort with ambiguity, clear communication, organization, initiative, ability to take feedback, discretion, experience with MS 365, enthusiasm for AI, etc. Those could go under Skills. However we must not duplicate content. We could put those under Requirements (which already lists many). The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one Requirements section. But we need to follow headings list; we can still include Requirements and maybe Skills if we have distinct content. However the posting already has a "Requirements" bullet list. It also includes "Preferred experience includes:" which could be Qualifications? Actually Qualifications could be the preferred experience. But we can treat "Requirements" as mandatory, and "Preferred experience" as Qualifications. That seems reasonable. Thus sections: - About the role: could include Position purpose and maybe About Jambalaya Group? The instruction: About the role heading for section about role. We'll put Position purpose and maybe brief description. - Responsibilities: Primary Responsibilities list. - Requirements: mandatory requirements list (3-5 years experience, consulting mindset, etc.) - Qualifications: Preferred experience (Salesforce, small business experience, HR certifications welcome but not required, etc.) - Skills: maybe we could extract skill items from Requirements but to avoid duplication, maybe we skip Skills. - Benefits: benefits package. - Schedule: Work arrangement: Full time, remote within the United States. We should not repeat job title. No metadata like Department, Reports to, Classification maybe we can fold into a short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph at top maybe with Department, Reports to, Work arrangement? But we already have Schedule section for work arrangement. Department and Reports to could be minor metadata; we could include them in a short p before sections. But we must not repeat job title. It's okay to include a short p with that info. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can reformat into HTML. Must not lose any detail. That's a lot. We need to ensure we include all bullet points etc. Let's extract content: Department: People and Culture (HR) Reports to: Head of People and Culture Work arrangement: Full time, remote within the United States Classification: Exempt Benefits: Full benefits package, including health, dental, and vision insurance; a 401(k) with an employer match; paid time off; and paid holidays. Benefits are subject to eligibility requirements and applicable plan terms. Position scope: HR service delivery, recruiting backup, and progressive support for smaller fractional HR engagements About Jambalaya Group: (paragraphs) Position purpose: (paragraph) Primary Responsibilities: list of items (Compensation support, Benefits support, Role descriptions..., Employee handbooks..., Career development, Performance management, Reactive HR support, Employee relations support, Process improvement, HR implementation, Client and project coordination, Recruiting backup, Fractional HR support) How You Will Work: paragraph How Success Will Be Measured: list of items (Consulting & Judgment, Client Relationships, Work Quality, Execution, Responsiveness, Managing Complexity, Initiative & Ownership, Relationships & Communication, Growth) Requirements: list (3-5 years HR experience..., consulting mindset..., strong judgment..., relationship-building..., business acumen..., comfort with ambiguity..., clear communication..., strong organization..., initiative..., ability to take feedback..., discretion..., experience with MS 365..., genuine enthusiasm for using AI..., energy, adaptability, curiosity..., genuine interest in people) Preferred experience includes: Experience with Salesforce; experience supporting small businesses, professional services organizations, or financial advisory practices; experience working directly with business owners or leaders in an advisory or consultative capacity. HR certifications are welcome but not required. Experience supporting small businesses, professional services firms, or financial advisory practices is helpful. HR certifications are not required. Initial role expectations: (paragraphs for first 90 days, months three to six, as readiness develops) Performance expectations: list (Work quality, Responsiveness, Execution, Relationships, Judgment, Increasing ownership) (the last seems cut off but we have enough). We need to include all that. We must not create Pay section. We need to output only HTML fragment. Let's structure:

Department: People and Culture (HR) | Reports to: Head of People and Culture | Classification: Exempt

Then sections:

About the role

Position purpose: ... (the paragraph). Also maybe include Position scope? Could include there. Better: About the role includes Position purpose and Position scope. We'll put the Position purpose paragraph and then maybe a short sentence about scope. Then Responsibilities:

Responsibilities

with each responsibility as
• . Then Requirements:

  Requirements

  with each requirement. Then Qualifications:

  Qualifications

  with preferred experience items. Then Skills: maybe we could include skill items from Requirements but to avoid duplication we could omit. However we might miss some skill details like "Clear, confident written and verbal communication", "Strong organization and attention to detail", etc. Those are already in Requirements list. So we can keep them there. Then Benefits:

  Benefits

  with each benefit. Then Schedule:

  Schedule

  Full time, remote within the United States.

  We also need to include How You Will Work and How Success Will Be Measured and Initial role expectations and Performance expectations. Where to put those? They are substantive. Could be part of About the role or separate sections like "How you will work" and "How success will be measured". But the instruction only gave example headings; we can add other headings if needed? It 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 those sections. It might be okay to add other headings like "How you will work" etc. However to be safe, we could incorporate those details into existing sections: How you will work could go under About the role or Responsibilities? How success will be measured could be under About the role as well. Initial role expectations and Performance expectations could be under About the role or maybe a separate section "Expectations". But we risk missing details if we just summarize. We must preserve all substantive information; we can include them as paragraphs under appropriate headings without losing detail. Thus we can have sections: - About the role (includes Position purpose, Position scope, How you will work, How success will be measured, Initial role expectations, Performance expectations). That's a lot but okay. But we need to avoid too thin sections; one big About the role is fine. Let's craft About the role section with multiple paragraphs. We'll include: Paragraph 1: Position purpose (the paragraph). Paragraph 2: Position scope. Paragraph 3: How you will work (the paragraph). Paragraph 4: How success will be measured (list? we can keep as

  inside About the role). But we might want to keep as list for clarity. Paragraph 5: Initial role expectations (three bullet points). Paragraph 6: Performance expectations (list). That preserves details. Now Responsibilities: list. Requirements: list. Qualifications: list (preferred experience). Benefits: list. Schedule: paragraph. Now we need to ensure we don't miss any detail like "Benefits are subject to eligibility requirements and applicable plan terms." include that. Also "Work arrangement: Full time, remote within the United States | Classification: Exempt" we already have classification in metadata p. Now let's extract exact text. I'll copy relevant sections. About Jambalaya Group: we may not need to include as it's company info; but it's substantive about the company. Could be included under About the role? Might be okay but not required. The instruction: preserve ALL substantive information. So we should include it. Where? Could be a separate section "About the company" but not in allowed headings. Could fold into About the role as a paragraph. We'll include a paragraph about Jambalaya Group. Thus About the role will have: - About Jambalaya Group (description) - Position purpose - Position scope - How you will work - How success will be measured - Initial role expectations - Performance expectations Now let's extract each piece exactly. About Jambalaya Group paragraph(s): "Jambalaya Group is not your typical consulting firm—and we like it that way. For more than 25 years, we have helped financial advisory practices build stronger businesses through consulting, coaching, training, and hands-on implementation. We recently transitioned to new ownership and are in a significant growth phase, building on a strong foundation while continuing to evolve how we serve our clients, develop our team, and grow our business. We are a highly collaborative team that believes great consulting requires both strategy and a willingness to roll up your sleeves and get the work done. We think deeply, move quickly, care about the details, and build meaningful relationships with our clients. Excellence matters to us, but we also believe doing great work should be fun. Our values shape how we work: Act with Intention. Start with insight. Lead with purposeCare Deeply. Build meaningful relationships and cultivate genuine connectionsMake It Fun or Make It Stop. Energy, humor, and joy are part of how we winBe Bold. Build bridges. Be resilient. ReinventBe Aggressively Authentic. Be real. Speak real. We are what we consistently do We are looking for people who connect with those values—not just people who can recite them. Jambalaya is growing quickly. That creates tremendous opportunity—and it also means things move fast. We collaborate constantly. We change course when new information tells us we should. We expect people to bring ideas forward, challenge thinking respectfully, help one another, and jump in when something needs to get done. We're