Project Lead, Payroll

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. No filler. Must not repeat job title. No Job ID. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - Intro: "Hi, Future Homie! At Homebase, you’ll join a team..." This is about company culture. Could be "About the role" or maybe "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - "Your Impact Starts Here We’re looking for a Project Lead who will own the process of ensuring that our customers are up and running with Homebase Payroll. You will work with small businesses to understand their payroll needs and work closely with sales to gather required information to ensure an accurate and compliant implementation. You will own the onboarding process. You will own this process from start to finish, including helping the customer run their first payroll with Homebase. You will work in tandem with an Onboarding Implementation Specialist who will be responsible for the technical tasks, along with YTD and Demographic loads. These are the key ways you’ll contribute and create impact in this role:" Then bullet list of responsibilities. Thus Responsibilities section: list of duties. Then "Role 🚀 The Foundation for Success - These are the experiences and strengths that will set you up for success in this role:" Then list of qualifications/experience. Could be Requirements or Qualifications. The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Probably combine into Requirements (or Qualifications). Since they list experiences and strengths, that's qualifications. Could use "Qualifications". Also there is a separate "🤖 AI Fluency Expectations (Required)" which is also a requirement. Could be part of Requirements. Then "🤝 The Homie Way - These principles guide everything we do..." That's about company values/culture. Could be "About the role" or maybe "Skills"? Not exactly. Might be "Skills"? But it's more about values. Could be omitted if not matching headings? But we need to preserve substantive info. Could put under "About the role" as description of culture. Then "What We Offer" with bullet list of benefits: Ownership & Financial Security, Healthcare, Flexible Time, AI access, Family Support, Protection Plans, Work Your Way, Hybrid Rhythm, Workspace Perks. That's Benefits section. Pay: Not mentioned explicitly (no salary). So we should NOT create Pay section. Schedule: They mention "Collaborate in-office Monday through Thursday" and later "Our Hybrid Rhythm: Monday-Thursday are required in-office days; Fridays flexible." That's schedule info. So we can have a Schedule section. Also there is "What To Expect During The Interview Process" which is application instructions; we must remove. Also "Belonging at Homebase" EEO boilerplate; remove. Also "Hey, We’re Homebase" description of company; could be part of About the role. Thus sections: - About the role (maybe include intro and company description, Homie Way values) - Responsibilities (list) - Qualifications (or Requirements) (list of experiences, AI fluency) - Benefits (list) - Schedule (in-office Monday-Thursday, Friday flexible) We must not create Pay section. We must not create Skills section unless we have specific skills list; we have some skills mentioned in qualifications (Excel, CRM, communication, problem-solver, etc.) Could be Skills section. But we already have Qualifications covering experiences; maybe better to split: Requirements (hard requirements) and Skills (soft skills). However instruction says prefer few substantive sections over many thin ones. So we could combine qualifications and skills into one section called "Requirements" or "Qualifications". Let's choose "Qualifications". Include all: experience, AI fluency, technical skills, communication, problem solving, etc. Now we need to format lists with

• . For prose, use

  . We must not include any filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's draft:

  About the role

  Hi, Future Homie! At Homebase, you’ll join a team that’s bold, fast-moving, and obsessed with helping small businesses thrive. We build with empathy, act with urgency, and take big swings that drive real-world impact. Here, every Homie shows up to raise the bar, support one another, and celebrate wins as a team. We’re not just building an app—we’re building unstoppable teams.

  Homebase is the everything app for hourly teams—built to simplify the day-to-day and superpower local businesses. With tools for scheduling, time clocks, payroll, communication, HR, and more, we help teams stay connected and in control. Today, over 150,000 small (but mighty) businesses rely on us to make work radically easier. Together, we’ve tracked over a billion hours for 2M+ workers—and we’re just getting started.

  The Homie Way guides everything we do: Be Customer Obsessed – Solve problems with empathy and creativity. Move Fast, Learn Fast – Experiment, take action, and grow every day. Own Your Impact – Think big, focus on what matters, and make decisions you stand behind. Master Your Craft – Excellence fuels impact—show up, step up, and make your mark. Win Together – Put goals over roles, lead with trust, and connect to our mission and each other.

  Then Responsibilities:

  Responsibilities

  • Own the end-to-end payroll implementation experience — you're the customer's primary point of contact from kickoff through first payroll run, keeping projects on track and on timeline
  • Collect and reconcile complex customer data including business entity details, employee demographics, and YTD payroll records from prior providers
  • Train customers on Homebase Payroll, ensuring they leave onboarding confident and self-sufficient
  • Investigate and resolve customer payroll questions by researching regulations, troubleshooting system issues, and partnering cross-functionally when needed
  • Collaborate with Sales to address implementation blockers that require customer follow-up
  • Surface product feedback and partner with Product and Engineering to improve customer-facing functionality and internal tooling
  • Maintain clean, accurate records in Salesforce throughout every implementation
  • Collaborate in-office Monday through Thursday
  Note: The last bullet about collaborating in-office Monday through Thursday could also go to Schedule, but it's also a responsibility. We'll keep it there; but we also have Schedule section later. Qualifications:

  Qualifications

  • 3+ years in an Implementation, Onboarding, Payroll, or Project Management role at a SaaS company; payroll implementation experience strongly preferred
  • Proven project management experience managing multiple client engagements simultaneously
  • Advanced in Excel or Google Sheets — you're comfortable cleaning, reconciling, and working through large data sets
  • Hands-on experience with CRMs (e.g., Salesforce), phone systems, and basic technical troubleshooting
  • A clear, confident communicator who can translate complex payroll concepts for customers and internal stakeholders alike
  • A strong problem-solver who can navigate ambiguity, research state-by-state regulations, and find answers independently
  • Energized by complex systems with rules that vary by state, county, and municipality
  • Metrics-driven with a track record of hitting individual and team goals
  • Highly organized with a strong sense of ownership — you drive work to completion and flag risks early
  • AI Fluency Expectations (Required): Actively use AI tools to improve implementation workflows and operational efficiency; partner with others to test, measure, and refine AI-driven solutions; use data to evaluate AI performance and recommend improvements; continuously learn and adapt as AI capabilities evolve
  Benefits:

  Benefits

  • Ownership & Financial Security: Stock options + 401(k) with 4% match
  • Comprehensive Healthcare: Medical, dental, and vision coverage + FSA options
  • Flexible Time: Unlimited PTO (salaried) + company holidays
  • AI access, for real: Paid AI tools with minimal restrictions
  • Family Support: Up to 12 weeks of paid parental leave (after 6 months of service)
  • Protection Plans: Life insurance + short/long-term disability coverage
  • Work Your Way: Work From Anywhere Month + meeting-free weeks yearly
  • Workspace Perks: Meals provided, commuter benefits, team offsites, and Customer Days
  • Hybrid Rhythm: Monday‑Thursday are required in‑office days; Fridays are flexible — work from home or come in, your call
  Schedule: Actually we already included schedule in Benefits (Hybrid Rhythm). But we could separate Schedule section. However we already have schedule info in Benefits; maybe better to have a Schedule section separate to avoid duplication. The instruction says prefer few substantive sections over many thin ones. So we could incorporate schedule into Benefits or Responsibilities. But we already have schedule bullet in Responsibilities (Collaborate in-office Monday through Thursday). And we have Hybrid Rhythm in Benefits. To avoid duplication, we could keep schedule info only in Benefits (Hybrid Rhythm) and remove the Monday-Thursday bullet from Responsibilities. However the responsibility bullet is about collaborating in-office Monday through Thursday; it's a duty. Could keep it there; but then schedule info appears twice. Might be okay but could be considered duplication. The instruction says remove duplicated lines. So we should avoid duplicating same info. Let's decide: Keep schedule info in Benefits (Hybrid Rhythm) and remove the Monday-Thursday bullet from Responsibilities. However the responsibility bullet also mentions collaborating in-office Monday through Thursday as part of role; but we can keep a more generic responsibility about collaborating with team etc. But the bullet is specific. Perhaps we keep it as part of responsibilities but then we don't need separate schedule section. The instruction 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 having schedule info also in responsibilities. But we should avoid duplicate lines. The bullet about collaborating in-office Monday through Thursday is a responsibility; the Hybrid Rhythm is a benefit/work arrangement. They are related but not identical. Could keep both. But to avoid duplication, we could keep schedule info only in Benefits and adjust responsibility bullet to not mention Monday-Thursday. Let's rephrase responsibility bullet: maybe "Collaborate with cross-functional teams to drive implementation success". However we must not invent or summarize away detail; we must preserve ALL substantive information. Changing the bullet would alter the content. So we cannot remove the Monday-Thursday detail if it's substantive. So we need to keep that detail somewhere. If we put it in Responsibilities, we still need to convey schedule info somewhere else? The Hybrid Rhythm is also substantive. It's not duplicate exactly; one is a responsibility (you must collaborate in-office Monday-Thursday), the other is a benefit (Hybrid Rhythm: Monday-Thursday required in-office days; Fridays flexible). They are complementary but not identical. It's okay to have both. Thus we will have both sections: Responsibilities includes that bullet; Benefits includes Hybrid Rhythm. That's fine. Now we need to ensure we didn't include any boilerplate like EEO, application instructions, etc. We removed those. Check for any leftover boilerplate: The "What To Expect During The Interview Process" we removed. The "Belonging at Homebase - We're committed to fostering