Future Opportunities: Early Career Sales Talent

We need to output HTML fragment with sections for headings that have content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Keep substantive info. We need to parse the posting. Key sections: - About Gusto (intro) maybe not needed as heading? Could be part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings only if there is real specific content. We have content: - About Gusto: description of mission, teams, etc. Could be placed under a heading "About Gusto"? Not in list but could be considered "About the role"? Actually "About the role" is separate. The intro about Gusto could be considered "About Gusto" but not in list; but we could still include as a

without heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those for those sections. Probably we should include a heading "About Gusto" as

if we want to separate. But they gave examples; not strict. Safer to follow examples: use those headings only. So we may not need a separate About Gusto heading; we can incorporate that info into a

under maybe "About the role" or just as a leading paragraph before headings. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can start with a

containing the Gusto intro, then headings. We need sections: - About the role: we have description: "Gusto is seeking motivated, customer-centric professionals interested in being considered for future sales and onboarding opportunities in 2026..." etc. Also includes "Here’s What You’ll Do Day-to-day" bullet list. - Responsibilities: could be the bullet list under "Here’s What You’ll Do Day-to-day". Could also be separate. - Requirements / Qualifications: we have "Here’s what we're looking for:" list with 1-3 years experience etc. Also "Experience working in high-volume environments..." etc. Also "Comfortable using Salesforce..." etc. Also maybe "Final compensation will be determined..." but that's compensation. - Skills: maybe mention Salesforce, consultative selling, etc. - Benefits: The posting mentions "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also "Offer amounts are determined by role, level, and location." Also "Learn more about our Total Rewards philosophy." Also "AI is a fundamental part..." Not exactly benefits. There's mention of equity (RSUs). Also maybe "competitive base pay, benefits, and equity". So we can include Benefits section with that. - Pay: "The estimated compensation range for these roles is $20.00–$28.00 per hour." Also "Final compensation will be determined based on the specific role, level, and experience alignment." So we can include Pay. - Schedule: "Employees who are based in those locations will be expected to work from the office on designated days approximately 2-3 days per week (or more depending on role)." Also note about hybrid. So we can include Schedule. We must not include sections with filler like "commensurate with experience". We have actual numbers. We must not include boilerplate like EEO, legal, etc. Remove those paragraphs. We must not include application instructions like "Submit your interest..." etc. Remove. We must not include duplicated lines. We need to preserve all substantive information. Let's extract substantive content: Intro about Gusto: "At Gusto, we're on a mission to grow the small business economy. We handle the hard stuff — payroll, health insurance, 401(k)s, and HR — so owners can focus on their craft and their customers. With teams in Denver, San Francisco, and New York, we support more than 500,000 small businesses nationwide and are building a workplace that reflects the people we serve. All full-time employees receive competitive base pay, benefits, and equity (RSUs) — because everyone who helps build Gusto should share in its success. Offer amounts are determined by role, level, and location. Learn more about our Total Rewards philosophy. AI is a fundamental part of how work gets done at Gusto. We expect all team members to actively engage with AI tools relevant to their role and grow their fluency as the technology evolves. AI experience requirements vary by role and will be assessed during the interview process." That's substantive; we can keep as a leading

maybe under a heading "About Gusto"? But not in list. Could just be a

before sections. Then "About The Role": "Gusto is seeking motivated, customer-centric professionals interested in being considered for future sales and onboarding opportunities in 2026. These roles are ideal for early-career sales talent who thrive in a fast-paced, consultative environment and are passionate about helping small businesses succeed. As a member of our Sales or Onboarding teams, you’ll own customer experience from first conversation through successful adoption—helping small businesses select Gusto and navigate their first steps with us. You’ll handle inbound calls and chats while potentially engaging in some outbound outreach to prospective or current customers. Through empathy, problem-solving, and advisory selling, you’ll make an immediate impact on how our customers experience Gusto from day one." Then "Here’s What You’ll Do Day-to-day": bullet list: - Handle high-volume inbound calls, chats, and emails from customers or partners at various stages of their journey—from discovery to onboarding. - Serve as a trusted advisor, helping small businesses or accounting partners select the right Gusto solutions for their needs. - Support customers through the onboarding process to ensure a smooth and successful start. - Demonstrate strong product knowledge and a commitment to ethical, customer-first selling. - Maintain accurate notes and pipeline details in Salesforce to ensure excellent follow-through. Then "Here’s what we're looking for:" list: - 1–3 years of experience in a sales or customer service role. - Experience working in high-volume environments that include inbound and outbound calling. - Proven success achieving or exceeding goals and maintaining strong customer relationships. - A passion for consultative, solution-oriented selling and helping small businesses succeed. - Comfortable using Salesforce or similar CRM systems. Then "This posting represents a general talent pipeline that spans multiple levels within our Sales team. Final compensation will be determined based on the specific role, level, and experience alignment. The estimated compensation range for these roles is $20.00–$28.00 per hour." Then "Gusto has physical office spaces in Denver, San Francisco, and New York City. Employees who are based in those locations will be expected to work from the office on designated days approximately 2-3 days per week (or more depending on role). The same office expectations apply to all Symmetry roles, Gusto's subsidiary, whose physical office is in Scottsdale. Note: The San Francisco office expectations encompass both the San Francisco and San Jose metro areas. When approved to work from a location other than a Gusto office, a secure, reliable, and consistent internet connection is required. This includes non-office days for hybrid employees." Then "Our customers come from all walks of life and so do we. We hire great people from a wide variety of backgrounds, not just because it's the right thing to do, but because it makes our company stronger. If you share our values and our enthusiasm for small businesses, you will find a home at Gusto." Then EEO etc to remove. We need to decide headings. Possible sections: - About Gusto (intro) maybe as

About Gusto

then

... but not in examples. Could still be okay. But instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for those sections. Safer to stick to those. So we could treat the intro as part of "About the role" or just a leading

without heading. Probably better to have a

for Gusto intro then

About the role

etc. Thus:

At Gusto, we're on a mission ... AI experience requirements vary by role and will be assessed during the interview process.

Then

About the role

with paragraph. Then

Responsibilities

with

• ... from day-to-day list. Then

  Requirements

  with
  • ... from "Here’s what we're looking for:" list. Optionally also

    Qualifications

    but we already have Requirements; could combine. But we could split: Requirements (experience) and Qualifications (skills). However the list includes both experience and skills. Could make Requirements for experience, Qualifications for skills like Salesforce, consultative selling. But we have only one list; we could put all under Requirements. Then

    Benefits

    with paragraph about competitive base pay, benefits, equity (RSUs), Total Rewards philosophy. Then

    Pay

    with paragraph about compensation range $20-$28 per hour, final compensation determined by role, level, experience. Then

    Schedule

    with paragraph about office expectations 2-3 days per week, hybrid, internet requirement, etc. We should also include the note about Symmetry and Scottsdale office, San Francisco metro area, etc. That's part of Schedule. Also include the statement about wide variety of backgrounds etc. Could be part of About Gusto or maybe a separate section like "Culture". Not in list; we could add as a

    under About Gusto or after Benefits. Probably incorporate into About Gusto paragraph. We must not include EEO etc. Let's craft HTML. We need to ensure no extra whitespace? It's fine. We'll output:

    At Gusto, we're on a mission to grow the small business economy. We handle the hard stuff — payroll, health insurance, 401(k)s, and HR — so owners can focus on their craft and their customers. With teams in Denver, San Francisco, and New York, we support more than 500,000 small businesses nationwide and are building a workplace that reflects the people we serve. All full-time employees receive competitive base pay, benefits, and equity (RSUs) — because everyone who helps build Gusto should share in its success. Offer amounts are determined by role, level, and location. Learn more about our Total Rewards philosophy. AI is a fundamental part of how work gets done at Gusto. We expect all team members to actively engage with AI tools relevant to their role and grow their fluency as the technology evolves. AI experience requirements vary by role and will be assessed during the interview process. Our customers come from all walks of life and so do we. We hire great people from a wide variety of backgrounds, not just because it's the right thing to do, but because it makes our company stronger. If you share our values and our enthusiasm for small businesses, you will find a home at Gusto.

    About the role

    Gusto is seeking motivated, customer-centric professionals interested in being considered for future sales and onboarding opportunities in 2026. These roles are ideal for early-career sales talent who thrive in a fast-paced, consultative environment and are passionate about helping small businesses succeed. As a member of our Sales or Onboarding teams, you’ll own customer experience from first conversation through successful adoption—helping small businesses select Gusto and navigate their first steps with us. You’ll handle in