Retirement Compliance Specialist

We need to output HTML fragment with sections: About the role, Responsibilities (Here’s What You’ll Do Day-to-day), Requirements/Qualifications (Here’s What We're Looking For), Benefits? There's mention of benefits: "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also mention "Offer amounts are determined by role, level, and location." Also "Our cash compensation range for this role is $62,400 to $78,000/year in Phoenix, $67,755 to $83,000/year in Denver and $74,285 to $91,000 in LA." Also "Additional locations will vary based on our geographical pay approach." Also "Final offer amounts are determined by multiple factors..." Also "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)." Also "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." Also "This includes non-office days for hybrid employees." We need sections: About the role (we have "About The Role" paragraph). Responsibilities (Here’s What You’ll Do Day-to-day). Requirements/Qualifications (Here’s What We're Looking For). Benefits? There's mention of benefits: "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also maybe "Learn more about our Total Rewards philosophy." Could include Benefits section with that sentence. Pay section: we have cash compensation ranges. Schedule: we have office expectations (2-3 days per week). So we can include Pay and Schedule sections. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate: EEO, equal opportunity, fraudulent activity disclaimer, applicant privacy notice, etc. Also remove "All full-time employees receive competitive base pay, benefits, and equity (RSUs)"? That's substantive benefit info, keep. Also "Learn more about our Total Rewards philosophy." maybe keep as part of Benefits. We must not create sections with filler like "commensurate with experience". We have actual ranges, so Pay section is valid. We must not include duplicated lines. We need to output only HTML fragment, using

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what to list as lists: Responsibilities bullet points, Requirements bullet points, Benefits maybe bullet points? Benefits: "competitive base pay, benefits, and equity (RSUs)" plus maybe "Learn more about our Total Rewards philosophy." Could be a list but it's short; we could put in

  . The instruction: Use

  • for any list of duties/requirements/benefits. So if we have a list, we should use ul/li. For Benefits we have maybe a short list: competitive base pay, benefits, equity (RSUs). Could be a list. Pay: we have ranges per location; could be a list. Schedule: we have office expectations: 2-3 days per week in Denver, SF, NY; note about SF includes SJ; remote work requires secure internet; etc. Could be a list. We need to preserve all substantive information. Let's extract. First, About Gusto paragraph: "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." We need to keep that as About Gusto? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't list About Gusto as a heading, but we could include it as a heading? The list includes About the role, not About Gusto. However we could treat the introductory paragraph as part of About the role? Actually there is a separate "About Gusto" section at top. The instruction says use those headings for sections; we can include other headings if needed? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings but better to stick to those. The About Gusto could be considered part of About the role? But there is also an "About The Role" heading later. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. However to be safe, we could include a heading "About Gusto" as

    . It's not in the examples but seems reasonable. However they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; we could still include About Gusto as a heading but maybe they'd consider it extra. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should combine About Gusto into About the role? But there is already an About The Role section later. The About Gusto is generic company info; could be placed before About the role as a paragraph without heading? The instruction says use

    for section headings; doesn't forbid having prose without heading. So we could output a

    for About Gusto, then

    About the role

    etc. Thus structure:

    About Gusto paragraph...

    About the role

    As a Retirement Compliance Specialist, you'll serve as a subject-matter expert on ERISA compliance and 401(k) plan administration within Gusto's Retirement Services organization. This role will be part of the Retirement Compliance team that focuses on the work that needs specialist judgment: independent quality assurance, training, complex corrections, and consultation on ambiguous or high-risk plan provisions. You'll be a trusted resource across the business, translating dense legal plan documents and ERISA requirements into guidance that Sales, Conversion Ops, and Customer Experience teams can act on confidently

    Responsibilities

    • Serve as the ERISA/compliance escalation point for Conversion Ops and Sales on complex plan provisions, eligibility questions, and Adoption Agreement interpretation.
    • Own end-to-end quality assurance for the plan review process — validating each build against the signed Adoption Agreement, and developing the internal tooling and business rules that support the review process at scale.
    • Conduct plan reviews for new and converting 401(k) plans, translating complex legal plan documents into clear, accurate guidance for internal teams and customers.
    • Build and deliver internal training and reference materials so Conversion Ops, Sales, and Customer Experience teams can handle routine plan questions independently.
    • Partner with Legal & Compliance on regulatory interpretation and sign-off for higher-risk plan changes.
    • Identify and champion opportunities to use AI tools and automation to reduce manual review time while strengthening accuracy across plan setup and compliance workflows.

    Requirements

    • 3–5 years of experience in 401(k)/defined contribution plan administration, compliance, or ERISA
    • Strong working knowledge of IRS and ERISA regulations governing retirement plans, including eligibility, testing, and corrections.
    • Experience reviewing plan documents (Adoption Agreements, plan provisions) and translating them into operational guidance.
    • Comfort partnering cross-functionally with Sales, Conversion Ops, and Legal & Compliance on ambiguous, escalated issues.
    • Strong written and verbal communication skills — able to distill complex ERISA concepts for audiences without a compliance background.
    • Experience building training materials or documentation for non-specialist teams.
    • AI literacy: comfortable using and helping refine AI-assisted tools for plan review and setup, and identifying where automation can responsibly take on routine work.
    • Exceptional attention to detail and organizational skills, even under deadline pressure.
    • Professional designations such as QKA, QPA, CRPS, or C(k)P are a plus, but not required.

    Benefits

    • Competitive base pay
    • Benefits
    • Equity (RSUs)

    Learn more about our Total Rewards philosophy.

    Pay

    • Cash compensation range: $62,400 to $78,000/year in Phoenix
    • $67,755 to $83,000/year in Denver
    • $74,285 to $91,000 in LA
    • Additional locations will vary based on our geographical pay approach.
    • Final offer amounts are determined by multiple factors, including candidate location, experience, and expertise, and may vary from the amounts listed above.

    Schedule

    • Gusto has physical office spaces in Denver, San Francisco, and New York City.
    • Employees based in those locations are expected to work from the office on designated days approximately 2-3 days per week (or more depending on role).
    • 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 (including non-office days for hybrid employees).
    We should also include the AI statement from About Gusto? Already included in About Gusto paragraph. We need to ensure we didn't include boilerplate: EEO, equal opportunity, fraudulent activity disclaimer, applicant privacy notice, etc. We removed those. Check for any duplicated lines: we didn't repeat. Check for any placeholder text like "commensurate with experience": none. Check for any missing substantive info: The About Gusto paragraph includes mission, handling hard stuff, teams locations, support 500k businesses, full-time employees receive competitive base pay, benefits, equity (RSUs), offer amounts determined by role, level, location, learn more about Total Rewards philosophy, AI fundamental, expect team members to engage with AI tools, AI experience requirements vary by role and assessed in interview. All kept. About the role paragraph kept. Responsibilities list kept. Requirements list kept. Benefits: we listed competitive base pay, benefits, equity (RSUs). Also added Learn more about our Total Rewards philosophy as a p. Pay: we included ranges and notes. Schedule: we included office expectations. We also might want to include the note about "The same office expectations apply to all Symmetry roles, Gusto's subsidiary, whose physical office is in Scottsdale." That's substantive about schedule. Should we include?