Retirement Compliance Specialist
Gusto · Scottsdale, AZ · 1 mo ago
Finance$62k–$78k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Pay, Schedule. Use for each heading. Use
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. Do not include Job ID. Remove boilerplate. Preserve all substantive info. Include sections only when posting has real specific content.
We need to parse the posting.
Content:
- About Gusto (intro) – maybe not needed as a section? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The intro about Gusto could be considered "About the role"? Actually there is an "About The Role" heading in posting. So we should create
About the role
and include the prose from that section.
- About The Team – maybe not a required heading; we could incorporate into About the role or maybe not needed. The instruction says only include sections when posting has real specific content for it. There's no explicit "About the team" heading in the list; we could either omit or incorporate into About the role. Probably better to include as part of About the role prose.
- Here’s What You’ll Do Day-to-day – that is Responsibilities. So Responsibilities
with list of duties.
- Here’s What We're Looking For – that is Requirements/Qualifications/Skills. We need to split into appropriate sections. The posting lists experience, knowledge, etc. Could be Requirements (experience), Qualifications (maybe professional designations), Skills (communication, AI literacy, attention to detail). We'll decide.
- Our cash compensation range ... – that is Pay. Provide Pay
with prose.
- Gusto has physical office spaces ... – that is Schedule (office expectations). Provide Schedule
with prose.
- Benefits: The posting mentions "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also earlier: "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also "Learn more about our Total Rewards philosophy." No specific benefits listed. There's no explicit benefits list (health insurance, 401k, etc.) but the intro mentions they handle payroll, health insurance, 401(k)s, HR. However that's about Gusto's product, not employee benefits. The posting does not list specific benefits like health, dental, etc. So we should not create a Benefits section unless there is real specific content. The phrase "competitive base pay, benefits, and equity (RSUs)" is vague; but it's a mention of benefits. However the instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we have a statement that they receive benefits, but not specific. Is that enough? It's somewhat vague but it's a statement that benefits are provided. Could be considered real content. However we need to decide if we should include Benefits section. The instruction: "Prefer a few substantive sections over many thin ones." If we include Benefits with just a sentence, maybe it's thin. But we could incorporate that sentence into About the role or Pay section. Probably better to omit Benefits section and mention benefits within About the role or Pay. Since they said "All full-time employees receive competitive base pay, benefits, and equity (RSUs)" we could put that in About the role or Pay. But Pay section already about cash compensation range; we could add benefits note there.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule.
Now we need to extract content.
About the role: The posting has "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". Also there is "About The Team" paragraph after that. We could combine.
Thus About the role prose: combine both paragraphs.
Responsibilities: bullet list from "Here’s What You’ll Do Day-to-day". Items:
- 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.
We'll put each as - .
Requirements: maybe "3–5 years of experience in 401(k)/defined contribution plan administration, compliance, or ERISA". Also "Strong working knowledge of IRS and ERISA regulations governing retirement plans, including eligibility, testing, and corrections." Also "Experience reviewing plan documents (Adoption Agreements, plan provisions) and translating them into operational guidance." Also "Comfort partnering cross-functionally with Sales, Conversion Ops, and Legal & Compliance on ambiguous, escalated issues." Also "Strong written and verbal communication skills — able to distill complex ERISA concepts for audiences without a compliance background." Also "Experience building training materials or documentation for non-specialist teams." Also "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." Also "Exceptional attention to detail and organizational skills, even under deadline pressure." Also "Professional designations such as QKA, QPA, CRPS, or C(k)P are a plus, but not required."
We need to split into Requirements, Qualifications, Skills. Let's define:
- Requirements: experience (3-5 years), knowledge of IRS/ERISA, experience reviewing plan documents, comfort partnering cross-functionally, experience building training materials, AI literacy, attention to detail.
- Qualifications: professional designations (QKA, QPA, CRPS, or C(k)P) are a plus.
- Skills: strong written and verbal communication skills, ability to distill complex ERISA concepts, maybe also communication.
But we could also put communication under Skills. Let's decide:
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.
- 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.
Qualifications:
- Professional designations such as QKA, QPA, CRPS, or C(k)P are a plus, but not required.
Skills:
- Strong written and verbal communication skills — able to distill complex ERISA concepts for audiences without a compliance background.
Alternatively, we could combine communication into Requirements. But we need to follow instruction: Prefer a few substantive sections over many thin ones. Having three sections (Requirements, Qualifications, Skills) each with some content is okay.
Now Pay: The posting includes 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. 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.
Also mention that all full-time employees receive competitive base pay, benefits, and equity (RSUs). We could incorporate benefits note here.
Thus Pay section prose: include the ranges and note about benefits and equity.
Schedule: The posting includes: 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.
Thus Schedule section prose.
Now we need to output HTML fragment only, no markdown.
We'll structure:
About the role
...combined paragraphs...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- Professional designations such as QKA, QPA, CRPS, or C(k)P are a plus, but not required.
Skills
- Strong written and verbal communication skills — able to distill complex ERISA concepts for audiences without a compliance background.
Pay
...compensation ranges... All full-time employees receive competitive base pay, benefits, and equity (RSUs).
Schedule
...office expectations...
Make sure not to include any boilerplate like EEO, etc.
Check that we didn't repeat job title. Good.
Now ensure we preserve all substantive information. Did we miss any? Let's verify.
From About Gusto intro: "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 omitted this intro. Is that substantive? It's about Gusto company overview. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Should we include this? It's not under any of the prescribed head
for prose. Do not repeat job title. Do not include Job ID. Remove boilerplate. Preserve all substantive info. Include sections only when posting has real specific content. We need to parse the posting. Content: - About Gusto (intro) – maybe not needed as a section? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The intro about Gusto could be considered "About the role"? Actually there is an "About The Role" heading in posting. So we should create
About the role
and include the prose from that section. - About The Team – maybe not a required heading; we could incorporate into About the role or maybe not needed. The instruction says only include sections when posting has real specific content for it. There's no explicit "About the team" heading in the list; we could either omit or incorporate into About the role. Probably better to include as part of About the role prose. - Here’s What You’ll Do Day-to-day – that is Responsibilities. SoResponsibilities
with list of duties. - Here’s What We're Looking For – that is Requirements/Qualifications/Skills. We need to split into appropriate sections. The posting lists experience, knowledge, etc. Could be Requirements (experience), Qualifications (maybe professional designations), Skills (communication, AI literacy, attention to detail). We'll decide. - Our cash compensation range ... – that is Pay. ProvidePay
with prose. - Gusto has physical office spaces ... – that is Schedule (office expectations). ProvideSchedule
with prose. - Benefits: The posting mentions "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also earlier: "All full-time employees receive competitive base pay, benefits, and equity (RSUs)". Also "Learn more about our Total Rewards philosophy." No specific benefits listed. There's no explicit benefits list (health insurance, 401k, etc.) but the intro mentions they handle payroll, health insurance, 401(k)s, HR. However that's about Gusto's product, not employee benefits. The posting does not list specific benefits like health, dental, etc. So we should not create a Benefits section unless there is real specific content. The phrase "competitive base pay, benefits, and equity (RSUs)" is vague; but it's a mention of benefits. However the instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we have a statement that they receive benefits, but not specific. Is that enough? It's somewhat vague but it's a statement that benefits are provided. Could be considered real content. However we need to decide if we should include Benefits section. The instruction: "Prefer a few substantive sections over many thin ones." If we include Benefits with just a sentence, maybe it's thin. But we could incorporate that sentence into About the role or Pay section. Probably better to omit Benefits section and mention benefits within About the role or Pay. Since they said "All full-time employees receive competitive base pay, benefits, and equity (RSUs)" we could put that in About the role or Pay. But Pay section already about cash compensation range; we could add benefits note there. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. Now we need to extract content. About the role: The posting has "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". Also there is "About The Team" paragraph after that. We could combine. Thus About the role prose: combine both paragraphs. Responsibilities: bullet list from "Here’s What You’ll Do Day-to-day". Items: - 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. We'll put each asAbout the role
...combined paragraphs...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- Professional designations such as QKA, QPA, CRPS, or C(k)P are a plus, but not required.
Skills
- Strong written and verbal communication skills — able to distill complex ERISA concepts for audiences without a compliance background.
Pay
...compensation ranges... All full-time employees receive competitive base pay, benefits, and equity (RSUs).
Schedule
...office expectations...
Make sure not to include any boilerplate like EEO, etc. Check that we didn't repeat job title. Good. Now ensure we preserve all substantive information. Did we miss any? Let's verify. From About Gusto intro: "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 omitted this intro. Is that substantive? It's about Gusto company overview. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Should we include this? It's not under any of the prescribed head