Manager, Operations
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details.
We need to decide which sections to include. The instruction says: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could map content to those standard headings. But we can also use other headings if they match content? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are examples; we can use those headings where appropriate. Probably we should use those standard headings for sections we have. Let's map:
- About the role: corresponds to "About The Role" section.
- About the team: maybe "About The Team" could be under "About the role"? But we could make a separate section "About the team" (not in examples but okay). However instruction says prefer a few substantive sections over many thin ones. Could combine About the role and About the team into one? But they are distinct. Might be okay to have both.
- What you get to do every day: could be "Responsibilities". That's a standard heading.
- What you bring to the role: could be "Requirements" or "Qualifications". We'll use "Requirements".
- Nice to have: could be "Qualifications" or "Skills". We'll use "Qualifications" for required, and maybe "Skills" for nice to have? But we have both required and nice to have. Could make "Requirements" for required, and "Preferred Qualifications" for nice to have. But instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate. Let's assign:
- Requirements: mandatory qualifications (3+ years people-management, understanding transaction lifecycle, etc.)
- Qualifications: nice to have (Bachelor's degree, direct experience with 401(k) platforms, etc.)
- Why you will love working at Human Interest: could be "Skills"? Not exactly. Could be "Benefits"? No. Could be a custom heading but we might avoid. However we could put that under "Benefits"? Not correct. Maybe we can treat it as "About the company" but not in list. The instruction says we should include a section only when posting has real, specific content. It didn't forbid custom headings beyond the examples, but gave examples. Safer to stick to examples; we could map that section to "Skills"? Not really. Could map to "Benefits"? Not exactly. Could map to "Pay"? No. Could map to "Schedule"? No.
Maybe we can combine "Why you will love working at Human Interest" with "Benefits" as part of benefits? But it's more about mission and culture. Could be a separate section "About the company" but not in examples. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list; we can use other headings if needed. But to be safe, we could create a section "Why you will love working at Human Interest" as an . That seems fine.
- Compensation: we have pay range. Use heading "Pay". Or "Compensation". The example includes Pay. We'll use Pay
.
- Benefits: we have benefits list. Use Benefits
.
- Awards and accolades: could be a section "Awards". Not in examples but okay.
We also have introductory mission paragraph before About The Role. We'll put that as a
before first heading.
We must not include boilerplate: EEO statement, accommodation statement, "Protect yourself agains". Remove.
We must preserve all substantive information: include details like investor names, mission, etc.
We need to use
- for any list of duties/requirements/benefits. So for responsibilities list (What you get to do every day) we need to turn each bullet into
- . For requirements list (What you bring to the role) also list. For nice to have list also list. For benefits list also list. For awards list also list.
We need to keep the prose paragraphs as
.
We must not repeat job title as heading. The job title is "Operations Manager within Customer Success & Operations". Not used as heading.
We must not put Job ID/requisition numbers as headings.
Now let's extract content.
Intro paragraph: "Human Interest is on a mission to ensure that people in all lines of work have access to retirement benefits. More than half of all working Americans are not saving enough for their future. Too often, it’s because they are employed by a company that doesn’t offer a retirement plan. Human Interest is changing that by making it affordable and accessible for small and medium-sized businesses to offer employees a path to financial independence through retirement savings. We’re a high-growth fintech company changing the retirement industry. We are backed by a number of investors. This includes funding from Marshall Wace and Baillie Gifford, as well as top investors such as BlackRock, TPG (The Rise Fund), SoftBank, Glynn Capital, NewView Capital, USVP, Wing, Uncork, and more."
That's the intro.
About The Role: paragraph: "As an Operations Manager within Customer Success & Operations, you will lead a team responsible for the accurate and timely execution of financial transactions and money movements on behalf of our clients and their participants. Operations at Human Interest serves as a critical connection point between our Customer Success Team—which partners with both the employers who offer 401(k) plans and the employees who participate in them—and our Product and Engineering teams. In this role you will act as a translator, turning frontline customer experience insights from CS into actionable input for Product, while ensuring that product and process changes are operationalized effectively for the people your team serves. You will bring a strong understanding of the transaction lifecycle within a 401(k) or similar regulated financial product, and you will pair that knowledge with an unstoppable drive to improve, automate, and scale operations—always with the discipline to stay lean. Above all, you will never lose sight of the fact that there is a real person behind every name and number on the screen."
About The Team: paragraph: "The CS Operations organization sits at the heart of Human Interest's mission to make retirement savings accessible. Our teams ensure high-value financial transactions for thousands of participants every day are handled seamlessly—ensuring every dollar lands in the right place, on time, and in full compliance with regulatory requirements. We operate in a highly regulated environment where errors carry real and substantial financial risk, so precision is non-negotiable. We maintain data integrity through rigorous review, quality control, and escalation protocols, and we collaborate closely with Customer Success, Engineering, Product, and Compliance to optimize workflows, surface operational insights, and continuously improve the customer experience. We partner tightly with peer teams across Operations to share best practices, understand shared challenges, and strengthen Operations as a whole. We are an organization that values accuracy, innovation, and a deep sense of responsibility to the people whose financial futures depend on what we do."
What You Get To Do Every Day: list of bullet points (starting with Coach, develop, and performance-manage...). We'll turn each bullet into
- .
What you bring to the role: list of bullet points (starting with 3+ years of people-management experience...). We'll turn each bullet into
- .
Nice to have: list of bullet points (starting with Bachelor's degree in Business...). We'll turn each bullet into
- .
Why you will love working at Human Interest: paragraph(s). There are multiple paragraphs: first paragraph about tackling retirement gap, etc. Second paragraph about hard work, etc. Third paragraph about operating principles list. We'll keep as
paragraphs.
Compensation: paragraph about base salary range $75,000 - $90,000 annually, etc. Also mention total rewards, bonuses, commissions, equity, etc. We'll keep as
.
Benefits: list of benefits: "A great 401(k) plan: Our own! Our 401(k) includes a dollar-for-dollar employer match up to 4% of compensation (immediately vested) and $0 plan fees", "Top-of-the-line health plans, as well as dental and vision insurance", "Competitive time off and parental leave", "Addition Wealth: Unlimited access to digital tools, financial professionals, and a knowledge center to help you understand your equity and support your financial wellness", "Lyra: Enhanced Mental Health Support for Employees and dependents", "Carrot: Fertility healthcare and family forming benefits", "Candidly: Student loan resource to help you and your family plan, borrow, and repay student debt", "Monthly work-from-home stipend; quarterly lifestyle stipend", "Engaging team-building experiences, ranging from virtual social events to team offsites, promoting collaboration and camaraderie." We'll turn each into
- .
Awards and accolades: list: "Certified as a Great Place To Work® (2023-2025)", "Fortune Best Place to Work in the Bay Area (2024)", "Best Places to Work by Built In (2023-2024)", "America’s Best Startup Employers by Forbes (2020-2022, 2024)", "A Top Company by Y Combinator (2020-2023)", "Inc. Fastest Growing Companies (2021)". We'll turn each into
- .
We must remove EEO statement and accommodation statement and "Protect yourself agains". Also remove any duplicated lines (none seen). Also remove any application instructions (none seen). Also remove any cookie/navigation/legal boilerplate (none seen besides the EEO). Also remove "We are committed to making every stage of our application process fully accessible..." that's accommodation statement; remove.
Now produce HTML fragment.
Structure:
Intro...
About the role
About The Role paragraph...
About the team
About The Team paragraph...
Responsibilities
- Coach, develop, and performance-manage a team of Associates and, where applicable, Team Leads—
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details. We need to decide which sections to include. The instruction says: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could map content to those standard headings. But we can also use other headings if they match content? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are examples; we can use those headings where appropriate. Probably we should use those standard headings for sections we have. Let's map:
- About the role: corresponds to "About The Role" section.
- About the team: maybe "About The Team" could be under "About the role"? But we could make a separate section "About the team" (not in examples but okay). However instruction says prefer a few substantive sections over many thin ones. Could combine About the role and About the team into one? But they are distinct. Might be okay to have both.
- What you get to do every day: could be "Responsibilities". That's a standard heading.
- What you bring to the role: could be "Requirements" or "Qualifications". We'll use "Requirements".
- Nice to have: could be "Qualifications" or "Skills". We'll use "Qualifications" for required, and maybe "Skills" for nice to have? But we have both required and nice to have. Could make "Requirements" for required, and "Preferred Qualifications" for nice to have. But instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate. Let's assign:
- Requirements: mandatory qualifications (3+ years people-management, understanding transaction lifecycle, etc.)
- Qualifications: nice to have (Bachelor's degree, direct experience with 401(k) platforms, etc.)
- Why you will love working at Human Interest: could be "Skills"? Not exactly. Could be "Benefits"? No. Could be a custom heading but we might avoid. However we could put that under "Benefits"? Not correct. Maybe we can treat it as "About the company" but not in list. The instruction says we should include a section only when posting has real, specific content. It didn't forbid custom headings beyond the examples, but gave examples. Safer to stick to examples; we could map that section to "Skills"? Not really. Could map to "Benefits"? Not exactly. Could map to "Pay"? No. Could map to "Schedule"? No.
Maybe we can combine "Why you will love working at Human Interest" with "Benefits" as part of benefits? But it's more about mission and culture. Could be a separate section "About the company" but not in examples. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list; we can use other headings if needed. But to be safe, we could create a section "Why you will love working at Human Interest" as an . That seems fine.
- Compensation: we have pay range. Use heading "Pay". Or "Compensation". The example includes Pay. We'll use Pay
.
- Benefits: we have benefits list. Use Benefits
.
- Awards and accolades: could be a section "Awards". Not in examples but okay.
We also have introductory mission paragraph before About The Role. We'll put that as a
. That seems fine.
- Compensation: we have pay range. Use heading "Pay". Or "Compensation". The example includes Pay. We'll use Pay
.
- Benefits: we have benefits list. Use Benefits
.
- Awards and accolades: could be a section "Awards". Not in examples but okay.
We also have introductory mission paragraph before About The Role. We'll put that as a
before first heading. We must not include boilerplate: EEO statement, accommodation statement, "Protect yourself agains". Remove. We must preserve all substantive information: include details like investor names, mission, etc. We need to use
- for any list of duties/requirements/benefits. So for responsibilities list (What you get to do every day) we need to turn each bullet into
- . For requirements list (What you bring to the role) also list. For nice to have list also list. For benefits list also list. For awards list also list.
We need to keep the prose paragraphs as
. We must not repeat job title as heading. The job title is "Operations Manager within Customer Success & Operations". Not used as heading. We must not put Job ID/requisition numbers as headings. Now let's extract content. Intro paragraph: "Human Interest is on a mission to ensure that people in all lines of work have access to retirement benefits. More than half of all working Americans are not saving enough for their future. Too often, it’s because they are employed by a company that doesn’t offer a retirement plan. Human Interest is changing that by making it affordable and accessible for small and medium-sized businesses to offer employees a path to financial independence through retirement savings. We’re a high-growth fintech company changing the retirement industry. We are backed by a number of investors. This includes funding from Marshall Wace and Baillie Gifford, as well as top investors such as BlackRock, TPG (The Rise Fund), SoftBank, Glynn Capital, NewView Capital, USVP, Wing, Uncork, and more." That's the intro. About The Role: paragraph: "As an Operations Manager within Customer Success & Operations, you will lead a team responsible for the accurate and timely execution of financial transactions and money movements on behalf of our clients and their participants. Operations at Human Interest serves as a critical connection point between our Customer Success Team—which partners with both the employers who offer 401(k) plans and the employees who participate in them—and our Product and Engineering teams. In this role you will act as a translator, turning frontline customer experience insights from CS into actionable input for Product, while ensuring that product and process changes are operationalized effectively for the people your team serves. You will bring a strong understanding of the transaction lifecycle within a 401(k) or similar regulated financial product, and you will pair that knowledge with an unstoppable drive to improve, automate, and scale operations—always with the discipline to stay lean. Above all, you will never lose sight of the fact that there is a real person behind every name and number on the screen." About The Team: paragraph: "The CS Operations organization sits at the heart of Human Interest's mission to make retirement savings accessible. Our teams ensure high-value financial transactions for thousands of participants every day are handled seamlessly—ensuring every dollar lands in the right place, on time, and in full compliance with regulatory requirements. We operate in a highly regulated environment where errors carry real and substantial financial risk, so precision is non-negotiable. We maintain data integrity through rigorous review, quality control, and escalation protocols, and we collaborate closely with Customer Success, Engineering, Product, and Compliance to optimize workflows, surface operational insights, and continuously improve the customer experience. We partner tightly with peer teams across Operations to share best practices, understand shared challenges, and strengthen Operations as a whole. We are an organization that values accuracy, innovation, and a deep sense of responsibility to the people whose financial futures depend on what we do." What You Get To Do Every Day: list of bullet points (starting with Coach, develop, and performance-manage...). We'll turn each bullet into
- . What you bring to the role: list of bullet points (starting with 3+ years of people-management experience...). We'll turn each bullet into
- . Nice to have: list of bullet points (starting with Bachelor's degree in Business...). We'll turn each bullet into
- .
Why you will love working at Human Interest: paragraph(s). There are multiple paragraphs: first paragraph about tackling retirement gap, etc. Second paragraph about hard work, etc. Third paragraph about operating principles list. We'll keep as
paragraphs. Compensation: paragraph about base salary range $75,000 - $90,000 annually, etc. Also mention total rewards, bonuses, commissions, equity, etc. We'll keep as
. Benefits: list of benefits: "A great 401(k) plan: Our own! Our 401(k) includes a dollar-for-dollar employer match up to 4% of compensation (immediately vested) and $0 plan fees", "Top-of-the-line health plans, as well as dental and vision insurance", "Competitive time off and parental leave", "Addition Wealth: Unlimited access to digital tools, financial professionals, and a knowledge center to help you understand your equity and support your financial wellness", "Lyra: Enhanced Mental Health Support for Employees and dependents", "Carrot: Fertility healthcare and family forming benefits", "Candidly: Student loan resource to help you and your family plan, borrow, and repay student debt", "Monthly work-from-home stipend; quarterly lifestyle stipend", "Engaging team-building experiences, ranging from virtual social events to team offsites, promoting collaboration and camaraderie." We'll turn each into
- . Awards and accolades: list: "Certified as a Great Place To Work® (2023-2025)", "Fortune Best Place to Work in the Bay Area (2024)", "Best Places to Work by Built In (2023-2024)", "America’s Best Startup Employers by Forbes (2020-2022, 2024)", "A Top Company by Y Combinator (2020-2023)", "Inc. Fastest Growing Companies (2021)". We'll turn each into
- .
We must remove EEO statement and accommodation statement and "Protect yourself agains". Also remove any duplicated lines (none seen). Also remove any application instructions (none seen). Also remove any cookie/navigation/legal boilerplate (none seen besides the EEO). Also remove "We are committed to making every stage of our application process fully accessible..." that's accommodation statement; remove.
Now produce HTML fragment.
Structure:
Intro...
About the role
About The Role paragraph...
About the team
About The Team paragraph...
Responsibilities
- Coach, develop, and performance-manage a team of Associates and, where applicable, Team Leads—