Engineering Manager, Privacy & Identity

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Strava", "About This Role", "What You'll Do", "What You'll Bring to the Team", "Why Join Us?" and compensation range. Also mention hybrid schedule: "We follow a flexible hybrid model that translates to more than half of your time on-site in our San Francisco office - three days per week." That's schedule info. Benefits: "For information on benefits, please click here." No actual benefits listed, just a link. According to rules: do NOT create Benefits section unless posting actually states them. It only says "For information on benefits, please click here." That's not specific benefits, so we should not create a Benefits section. Pay: compensation range given: "$204K - $240K". So we need a Pay section with that. Schedule: we have hybrid model info, so we can create a Schedule section with that description. We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use those exact headings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings where appropriate. We have content for About the role? The posting includes "About This Role". That maps to "About the role". We'll use

About the role

. Then responsibilities: "What You'll Do:" => Responsibilities. Use

Responsibilities

. Then requirements/qualifications: "What You'll Bring to the Team:" => Requirements or Qualifications. Could use Requirements. We'll use

Requirements

. Skills? Not separate; maybe we can combine. But we can also have Skills if we want but we should avoid thin sections. Probably just Requirements. Pay:

Pay

with compensation range. Schedule:

Schedule

with hybrid model description. We should not repeat job title as heading. No Job ID. We need to preserve all substantive information. Remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove "For information on benefits, please click here." (since we aren't making Benefits section). Also remove "Why Join Us?" maybe we can include as a section? The instruction list didn't include "Why Join Us?" but we could include as a section if we want, but headings limited to those examples; but we could still include other headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. ...)". It might be okay to use other headings, but better to stick to those. However "Why Join Us?" is substantive; we could incorporate into About the role or maybe as a separate section but not in list. Safer to include as a paragraph under About the role? But we need to preserve all substantive information. Could add a

About the company

but not in list. Might be okay. However instruction says "Prefer a few substantive sections over many thin ones." So we could merge "Why Join Us?" into About the role or maybe into a separate section called "About Strava". But we already have About Strava paragraph at top. That is substantive. We could create a section "About the company" but not in list. Might be okay but risk. Better to follow the examples: we have About the role, Responsibilities, Requirements, Pay, Schedule. We can incorporate the "Why Join Us?" and "About Strava" into About the role section as prose. Thus About the role section will contain the description of Strava and the role. Let's extract substantive content: About Strava: "Strava is the app for active people. With over 200 million athletes in more than 185 countries, it’s more than tracking workouts—it’s where people make progress together, from new habits to new personal bests. No matter your sport or how you track it, Strava’s got you covered. Find your crew, crush your goals, and make every effort count. Start your journey with Strava today. Our mission is simple: to motivate people to live their best active lives. We believe in the power of movement to connect and drive people forward." About This Role: "Strava is seeking an Engineering Manager for the Privacy and Login team — operating 60/40 as hands-on engineer and technical leader, with a consumer product focus. You'll own how athletes sign up, log in, and understand and manage their privacy on Strava, from account security to giving people clear visibility and control over their data across iOS, Android, and web. This is a platform engineering role, not a security or IAM specialist position. No prior identity or authentication experience is required. We're looking for strong product engineering fundamentals (fullstack skills prioritized) and the ability to learn quickly in a high-trust domain. We follow a flexible hybrid model that translates to more than half of your time on-site in our San Francisco office - three days per week." What You'll Do: list of bullet points (we need to turn into

• ). Let's capture each: - Give athletes clear, intuitive ways to understand and manage their privacy settings, and make sure that information is easy to find and act on in the product - Own the technical roadmap for account sign-up, login, password management, and account recovery - Build reliable, predictable login experiences so athletes can get into their accounts quickly and securely, across a unified foundation spanning Strava Group's app portfolio - Partner with Product, Security, Trust & Safety, and Legal to ensure compliance and platform integrity - Drive consistency across iOS, Android, and web login, privacy, and account experiences - Monitor and improve login success rates, recovery flows, and how well users engage with privacy controls - Lead with strong technical judgment, balancing hands-on contribution with clear technical leadership - Establish best practices, operational excellence, and a culture of inclusion and mentorship What You'll Bring to the Team: list: - 1-2 years of management/people leadership experience — we welcome early-career managers who are ready to grow into the role - 5+ years experience of strong fullstack or product engineering background — comfort across backend systems and consumer-facing UI is welcome, with the ability to quickly ramp up on systems that keep user accounts secure and easy to access - Comfort learning on the job how to build predictable, secure login experiences and clear, user-friendly privacy controls — no prior identity-specific experience required - Ability to lead a team through ambiguous, high-stakes technical problems and drive consistency across platforms - A product mindset: ability to balance user experience with robust data protection and abuse prevention - A holistic view of platform engineering as a foundation for trust, safety, privacy, and growth Pay: Compensation Range: $204K - $240K Schedule: "We follow a flexible hybrid model that translates to more than half of your time on-site in our San Francisco office - three days per week." We should not duplicate that sentence; it's already in About This Role. But we can still include in Schedule section. However we need to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original; but we might want to avoid repeating same sentence twice. Could keep it only in Schedule section and not repeat in About the role. But About the role currently includes that sentence. We could move it to Schedule and remove from About the role to avoid duplication. However we must preserve all substantive information; moving is fine as long as it's present somewhere. So we can omit that sentence from About the role and put it under Schedule. Thus About the role will not include hybrid model sentence. Now we need to strip boilerplate: "For information on benefits, please click here." (skip). "Why Join Us?" and following paragraphs: we need to incorporate that substantive info. Let's capture "Why Join Us?" paragraph: "Movement brings us together. At Strava, we’re building the world’s largest community of active people, helping them stay motivated and achieve their goals. Our global team is passionate about making movement fun, meaningful, and accessible to everyone. Whether you’re shaping the technology, growing our community, or driving innovation, your work at Strava makes an impact. When you join Strava, you’re not just joining a company—you’re joining a movement. If you’re ready to bring your energy, ideas, and drive, let’s build something incredible together. Strava builds software that makes the best part of our athletes’ days even better. Just as we’re deeply committed to unlocking their potential, we’re dedicated to providing a world-class, inclusive workplace where our employees can grow and thrive, too. We’re backed by Sequoia Capital, TCV, Madrone Partners and Jackson Square Ventures, and we’re expanding in order to exceed the needs of our growing community of global athletes. Our culture reflects our community. We are continuously striving to hire and engage teammates from all backgrounds, experiences and perspectives because we know we are a stronger team together." That's substantive. We can include this as part of About the role or maybe a separate section "About the company". Since we have About the role heading, we could incorporate this after the role description. That would be okay. We also need to include EEO statement? That's boilerplate; remove. Now construct HTML:

  About the role

  Strava is the app for active people. With over 200 million athletes in more than 185 countries, it’s more than tracking workouts—it’s where people make progress together, from new habits to new personal bests. No matter your sport or how you track it, Strava’s got you covered. Find your crew, crush your goals, and make every effort count. Start your journey with Strava today. Our mission is simple: to motivate people to live their best active lives. We believe in the power of movement to connect and drive people forward.

  Strava is seeking an Engineering Manager for the Privacy and Login team — operating 60/40 as hands-on engineer and technical leader, with a consumer product focus. You'll own how athletes sign up, log in, and understand and manage their privacy on Strava, from account security to giving people clear visibility and control over their data across iOS, Android, and web. This is a platform engineering role, not a security or IAM specialist position. No prior identity or authentication experience is required. We're looking for strong product engineering fundamentals (fullstack skills prioritized) and the ability to learn quickly in a high-trust domain.

  Movement brings us together. At Strava, we’re building the world’s largest community of active people, helping them stay motivated and achieve their goals. Our global team is passionate about making movement fun, meaningful, and accessible to everyone. Whether you’re shaping the technology, growing our community, or driving innovation, your work at Strava makes an impact. When you join Strava, you’re not just joining a company—you’re joining a movement. If you’re ready to bring your energy, ideas, and drive, let’s build something incredible together. Strava builds software that makes the best part of our athletes’ days even better. Just as we’re deeply committed to unlocking their potential, we’re dedicated to providing a world-class, inclusive workplace where our employees can grow and thrive, too. We’re backed by Sequoia Capital, TCV, Madrone Partners and Jackson Square Ventures, and we’re expanding in order to exceed the needs of our growing community of global athletes. Our culture reflects our community. We are continuously striving to hire and engage teammates from all backgrounds, experiences and perspectives because we know we are a stronger team together.

  Then Responsibilities:

  Responsibilities