Future Opportunities: Early Career Sales Talent

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key content: - About Gusto: mission, etc. Might be considered "About the role"? Actually "About Gusto" is company description; 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 have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those sections that have real content. We have: - About the role: The posting includes "About The Role" heading with description: "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." That's content for About the role. - Responsibilities: "Here’s What You’ll Do Day-to-day" list: bullet points: 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. We can put these as

• . - Requirements: The posting includes "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. These could be Requirements. - Qualifications: Might be similar to Requirements; but we can treat them as Qualifications if we want. However we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they ask to use headings like Requirements, Qualifications, Skills. We need to decide what content fits each. We have "Skills": maybe "Comfortable using Salesforce or similar CRM systems." Could be skill. Also "Proven success achieving or exceeding goals" maybe skill. But we can treat the list as Requirements. Qualifications could be empty; we should not create empty sections. So we should only include sections with real content. Thus we can have: - About the role (content) - Responsibilities (content) - Requirements (content) - Skills (maybe we can extract skill-specific items: "Comfortable using Salesforce or similar CRM systems." Could also include "Experience working in high-volume environments that include inbound and outbound calling." but that's more experience. We'll keep Skills as maybe "Comfortable using Salesforce or similar CRM systems." and maybe "Strong product knowledge" etc. But we already have product knowledge in responsibilities. Might be redundant. Better: Use Requirements for the list of experience/qualifications, and Skills for specific abilities like "Comfortable using Salesforce or similar CRM systems." and maybe "Strong product knowledge" (though that's more knowledge). But we can keep Skills minimal. - Benefits: The posting mentions "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also "Learn more about our Total Rewards philosophy." Also "Offer amounts are determined by role, level, and location." Also "Gusto has physical office spaces...". Benefits: maybe we can list "competitive base pay, benefits, and equity (RSUs)". Also "Total Rewards philosophy". But we need to avoid vague like "competitive base pay". It's still substantive. We'll include Benefits section with that sentence. - Pay: The posting includes "The estimated compensation range for these roles is $20.00–$28.00 per hour." That's pay. Also "Offer amounts are determined by role, level, and location." That's also pay. So we can include Pay section with that range. - Schedule: The posting includes office expectations: "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, internet connection. So we can include Schedule section with that. We must not include boilerplate like EEO, legal, fraud disclaimer, etc. Remove those. We must not include duplicated lines. Ensure we preserve all substantive info. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • Comfortable using Salesforce or similar CRM systems.

  Benefits

  All full-time employees receive competitive base pay, benefits, and equity (RSUs). Gusto’s Total Rewards philosophy outlines additional compensation and rewards.

  Pay

  The estimated compensation range for these roles is $20.00–$28.00 per hour, with final amounts determined by role, level, and location.

  Schedule

  Employees based in Denver, San Francisco, or New York City are expected to work from the office on designated days approximately 2–3 days per week (or more depending on role). Hybrid employees must maintain a secure, reliable, and consistent internet connection for remote work days.

  Check that we didn't repeat job title. Good. We must not include any markdown code fences. Just raw HTML. Check for any leftover boilerplate: we removed EEO, legal, etc. Check for any mention of "AI is a fundamental part..." That's in the intro about Gusto; maybe we could include in About the role? But it's not directly about role; it's about company. Could be omitted as not specific to role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The AI statement is substantive about Gusto expectations. Should we include it? It's under "About Gusto" section earlier. It says: "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. Should we include it somewhere? Could be part of About the role or maybe a separate section like "Expectations". But we only have predefined headings. Could we add it under About the role? It's about the company but relevant to role expectations. Probably we can include it in About the role paragraph. Thus modify About the role paragraph to include that AI expectation. Also the intro includes "Submit your interest to join our Sales team! Gusto is seeking sales professionals who thrive in a fast-paced, consultative environment and are interested in being considered for future start dates in 2026. If you’d like to be considered for future opportunities with our team, please complete the form below and upload your resume. While start dates are still being determined for 2026, we’d love to connect! Does this sound like you? Apply below!" That's basically application instructions and boilerplate; we should remove application instructions. So we discard that. Also "About Gusto At Gusto, we're on a mission to grow the small business economy..." That's company description; could be part of About the role? Might be considered "About the role" but it's more about company. However we can include it in About the role as context. The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include company description in About the role. Thus About the role paragraph: combine company description, mission, AI expectation, role description. Let's craft:

  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. 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.

  That seems comprehensive. Now Responsibilities: we have list. Requirements: list. Skills: maybe we can include "Comfortable using Salesforce or similar CRM systems." and also "Strong product knowledge" (though that's more knowledge). But we already have product knowledge in responsibilities. Could add "Strong product knowledge and a commitment to ethical, customer-first selling." but that's also responsibility. Might be duplication. Better to keep Skills minimal: maybe just "Comfortable using Salesforce or similar CRM systems." and "Strong communication and advisory selling skills." But we don't have that explicit. Let's stick to the explicit skill: "Comfortable using Salesforce or similar CRM systems." Benefits: we have sentence about competitive base pay, benefits, equity (RSUs). Also Total Rewards philosophy. We'll include. Pay: we have range. Schedule: we have office expectations. Now ensure we didn't include any boilerplate like "Note: The San Francisco office expectations encompass both the San Francisco and San Jose metro areas." That's part of schedule; we can include that detail. Thus schedule paragraph: "Employees based in Denver, San Francisco, or New York City are 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