Sr Engineering Manager – API & Auth Platform

We need to output HTML fragment with sections: About the role (already present), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Use

for each section heading. We need to extract content from the posting. Let's parse: - About Betterment: description of company. Could be considered "About the role"? Actually there is "About Betterment" then "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 heading "About the role". The content under that heading should be the description of the role (the "About The Role" paragraph). Also maybe include "About Betterment" as part of that? Probably not; "About the role" should contain the role description. The "About Betterment" is company overview; could be omitted? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep company overview somewhere. Could be placed under "About the role" or maybe a separate section? The allowed headings list does not include "About the company". But we could incorporate it into "About the role" as preamble. However we must not create sections with filler. We could put company overview in a

before the first heading? The instruction says output ONLY the HTML fragment; we can have

elements not under headings? Probably yes. But they said use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other

outside sections. Safer to include company overview as a

before the first heading. Now responsibilities: The "A Day in the Life" bullet list (actually sentences). Those are responsibilities. We'll put under

Responsibilities

with

• each bullet. Requirements/Qualifications/Skills: The "What We're Looking For" list includes experience managing senior ICs, etc. Could be split into Requirements and Qualifications and Skills. But we need to decide based on content. The list includes experience, capability, proven track record, experience leading projects, experience managing shared API platforms, hands-on experience with modern auth patterns, experience partnering with IT/security/business leaders, principled approach. These are more like requirements/qualifications. Skills could be subset like hands-on experience with modern authentication/authorization patterns, etc. But we can combine into one section maybe "Requirements". However instruction: prefer a few substantive sections over many thin ones. So we could have one section "Requirements" containing all those bullet points. Or we could split into Requirements and Skills if distinct. But to avoid thin sections, maybe combine. Benefits: The "Our Commitment To Your Total Well-being" lists benefits: medical, dental, vision coverage; life and AD&D insurance; short- and long-term disability; infertility support and WPATH-aligned transgender health benefits; an Employee Assistance Program (EAP); transit benefits and FSA and HSA options; Ownership: Equity for all employees, including new hire and refresher grants; Time: Flexible paid time off, paid parental leave, and a fully paid four-week sabbatical in your sixth year; Growth: Company-paid professional coaching for all employees; Wealth: Day-one 401(k) match plus matching on qualified student loan payments. That's substantive. So we create

  Benefits

  with
  • each. Pay: The posting includes base salary range: New York City: $200,000 - $230,000. Also mentions variable compensation in form of company incentive bonus. So we have pay info. So we create

    Pay

    with

    containing that. Schedule: The posting mentions hybrid NY-based positions (four days/week in-office, with no required office days during the summer and winter holidays). That's schedule info. So we create

    Schedule

    with

    . We must not include sections like "About the role" if we already have content. We'll have that. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a lot of boilerplate at the end: "We’ll take a few weeks..." etc. That's application instructions and hiring process; we should remove. Also the EEO statement at the end; remove. Also the "Come join us!" etc maybe considered boilerplate? It's more cultural but could be considered part of "We change lives" etc. The section "Join a team built on these core values" includes values; that could be considered substantive? It's about company values. Might be considered part of "About Betterment" or separate. But we already have About Betterment paragraph. The values list could be considered part of company culture; we could keep under "About the role" or maybe a separate section "Culture". But not in allowed headings. Could incorporate into About Betterment paragraph. However we must preserve ALL substantive information; we cannot discard values unless they are boilerplate. They are substantive but not fitting headings. We could add them as a

    under About the role or after. Better to keep them as a

    after About Betterment but before responsibilities. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. Structure:

    About Betterment: ...

    About the role: ... maybe combine with role description.

    But we need heading "About the role". So:

    About the role

    ... role description ...

    We could also include company overview before that as a

    . Let's extract role description paragraph: "As Sr Engineering Manager, you will lead a team of senior/staff engineers stewarding our shared GraphQL API frameworks, authentication and access control systems, and internal tooling platform. You will work directly with engineering and product leadership to drive the technical direction of the GraphQL API frameworks powering our customer-facing web and mobile applications. You will also collaborate closely with operations, customer support, and compliance partners to ensure our internal APIs let teams operate Betterment systems with the rigor our customers and regulators expect. As AI tooling reshapes how we build and operate our systems, you will have significant influence over how Betterment's APIs support AI agents and tooling safely in a regulated financial services environment. This role is based out of our NYC office." That's the role description. Now responsibilities: list from "A Day in the Life". Each sentence ends with a period. We'll split into bullet points. List: - Lead and grow a team of senior/staff engineers building the API, authentication, and internal tooling platform that every Betterment team relies on. - Drive technical strategy for the GraphQL API frameworks powering our customer-facing and internal apps, including agentic tooling for AI-native API development workflows. - Ensure Betterment's authentication and authorization systems remain current with industry best practices. - Sequence your team roadmap to balance reliability, security, developer experience, and platform capabilities — e.g. secure, first-party MCP access to Betterment APIs. - Work alongside the product teams who build on your platform every day. Develop broad Betterment domain expertise in the process. - Hold the line on the standards that keep shared systems healthy. Make them visible and easy to meet, and ensure teams understand the "why" behind them. - Partner with IT and security on platform governance so engineering teams can build on the API platform and ops teams can operate through it with confidence — as new AI identity and access patterns take shape. - Partner with department leaders on a permission model that fits evolving team workflows and incorporates new AI tooling, including MCP servers and connectors. - Cultivate efficient, blameless incident response across your team and the teams building on the API platform. Invest in observability that serves both developers and internal tool users. - Translate Betterment's strong culture of accountability into platform operating procedures — clear ownership, security, and iteration. We'll put each as

  • . Now Requirements/Qualifications/Skills: list from "What We're Looking For". We'll bullet each. List: - Experience managing senior and staff ICs; ability to coach engineers through technically complex challenges while maintaining team momentum. - Capable of meaningful architectural direction, code review, and hands-on work in our codebase. - Proven track record leading a team that owns a shared platform used by engineering, operations, and customer support teams. - Experience leading projects that affect multiple teams' software systems, tooling, and development workflows. - Experience managing shared API platforms — ideally GraphQL. - An appreciation for the frameworks, conventions, and developer tooling that let product teams introduce new capabilities, support existing usage, and gracefully retire legacy functionality. - Hands-on experience with modern authentication/authorization patterns (OAuth 2.0, OIDC, passkeys), with an understanding of the importance of adoption, long-term support, and security testing. - Experience partnering with IT, security, and business leaders on governance, access, and permission models. - Ability to build trust across disciplines and adapt as AI tools introduce new identity and access patterns. - Principled approach to balancing the need to move quickly today with the need to move quickly tomorrow, with an appreciation of how to meet high standards for customer quality and regulatory requirements. We'll put under

    Requirements

    (or maybe Qualifications). Choose Requirements. Now Benefits: list each item. We need to split the benefits paragraph into distinct items. Paragraph: "We offer a competitive suite of benefits, including medical, dental, and vision coverage; life and AD&D insurance; short- and long-term disability; infertility support and WPATH-aligned transgender health benefits; an Employee Assistance Program (EAP); transit benefits and FSA and HSA optionsOwnership: Equity for all employees, including new hire and refresher grants.Time: Flexible paid time off, paid parental leave, and a fully paid four-week sabbatical in your sixth year.Growth: Company-paid professional coaching for all employees.Wealth: Day-one 401(k) match plus matching on qualified student loan payments." Note there are missing spaces after some semicolons. We'll parse. Items: - medical, dental, and vision coverage - life and AD&D insurance - short- and long-term disability - infertility support and WPATH-aligned transgender health benefits - an Employee Assistance Program (EAP) - transit benefits and FSA and HSA options - Ownership: Equity for all employees, including new hire and refresher grants - Time: Flexible paid time off, paid parental leave, and a fully paid four-week sabbatical in your sixth year - Growth: Company-paid professional coaching for all employees - Wealth: Day-one 401(k) match plus matching on qualified student loan payments We'll bullet each. Now Pay: base salary range NYC: $200,000 - $230,000. Also variable compensation: company incentive bonus. We'll include.

    Base salary range for New York City: $200,000 – $230,000. This role may also be eligible for variable compensation in the form of a company incentive bonus.

    Now Schedule: hybrid NY-based positions (four days/week in-office, with no required office days during the summer and winter holidays).

    Hybrid New York City–based position: four days per week in‑office, with no required office days during summer and winter holidays.

    Now About Betterment paragraph: we need to include. Paragraph: "Betterment is a leading, technology-driven financial services company that offers investing, savings and retirement solutions for retail investors and investment advisors as well as financial wellness solutions, including a 401(k) for small and medium-sized businesses. Our team is passionate about our mission, to empower people to build wealth with confidence and ease. We're headquartered in NYC and offer hybrid NY-based positions (four days/week in-office, with no required office days