Engineering Manager, Play Expansion
Fetch · United States · 3 wk ago
RemoteRemoteEngineering$168k–$198k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "What we’re building and why we’re building it." (intro), "Meet Fetch Engineering", "About The Role", "What You’ll Do At Fetch (Role Responsibilities)", "In Your Toolbox (Minimum Requirements)", "Compensation", "Benefits". Also maybe "Pay" and "Schedule". The posting includes compensation range and benefits details. No schedule info. So we should include sections: About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly.
We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines. Remove application instructions. Also remove EEO statement at end. Also remove "Fetch is an equal opportunity employer..." etc.
We need sections only when posting has real specific content. So we will have:
- About the role (maybe combine intro and Meet Fetch Engineering? Actually "About The Role" is a heading in posting. We'll use that as About the role.
- Responsibilities (What You’ll Do At Fetch (Role Responsibilities))
- Requirements (In Your Toolbox (Minimum Requirements))
- Benefits (Compensation and Benefits combined? Could separate Pay and Benefits. The posting includes compensation range and benefits details. We'll create Pay section with salary range, and Benefits section with list of benefits.
- Possibly Skills? Not needed.
- Schedule? Not present.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /. Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly.
We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines. Remove application instructions. Also remove EEO statement at end. Also remove "Fetch is an equal opportunity employer..." etc.
We need sections only when posting has real specific content. So we will have:
- About the role (maybe combine intro and Meet Fetch Engineering? Actually "About The Role" is a heading in posting. We'll use that as About the role.
- Responsibilities (What You’ll Do At Fetch (Role Responsibilities))
- Requirements (In Your Toolbox (Minimum Requirements))
- Benefits (Compensation and Benefits combined? Could separate Pay and Benefits. The posting includes compensation range and benefits details. We'll create Pay section with salary range, and Benefits section with list of benefits.
- Possibly Skills? Not needed.
- Schedule? Not present.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /. Use headings, - for lists,
for prose.
We need to preserve all substantive info. Let's extract content.
Intro: "What we’re building and why we’re building it. Fetch helps people live rewarded every day, with a vision to become the rewards destination for everyone. We turn everyday activities into meaningful rewards, whether it’s grocery shopping, grabbing a quick meal, or playing a favorite mobile game. To date, we’ve awarded more than $1 billion in Fetch Points to our users. Each day, more than 13 million receipts are submitted on Fetch, providing visibility into over $212 billion in gross merchandise value. This creates the largest retail-agnostic, SKU-level view of household spending, powering Fetch as an outcomes-based advertising platform that helps brands acquire and retain lifelong consumers. The Fetch app is available on the App Store and Google Play, with more than 6 million five-star reviews from a highly engaged and loyal user base. It’s not just our users who believe in Fetch: with investments from Softbank, ICONIQ, DST, Greycroft, and partnerships ranging from challenger brands to Fortune 500 companies, Fetch is reshaping how brands and consumers connect in the marketplace. When you work at Fetch, you play a vital role in a platform that drives brand loyalty and creates lifelong consumers with the power of Fetch points. User and partner success are at the heart of everything we do, and we extend that same commitment to our employees. At Fetch, we value curiosity, adaptability, and the confidence to explore new tools, especially AI, to drive smarter, faster work. You don’t need to be an expert, but you should be ready to learn quickly and think critically. We welcome learners who move fast, challenge the status quo, and shape what’s next, with us. Ranked as one of America’s Best Startup Employers by Forbes for two years in a row, Fetch fosters a people-first culture rooted in trust, accountability, and innovation. We encourage our employees to challenge ideas, think bigger, and always bring the fun to Fetch."
That's a lot of prose. Could be placed under About the role? Actually About the role section should contain description of role. The intro is more about company. But we need to preserve all substantive info; we could put it under About the role as a preamble, but maybe better to have a separate "About Fetch" section? Not in allowed headings list. 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? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we need to map content to those headings. The intro could go under About the role (maybe as part of role description). But About the role heading should contain role specifics. However we also have a separate "About The Role" heading in the posting. So we can put the company overview under About the role as well, but maybe we should split: About the role includes both company overview and role specifics? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role, Responsibilities, Requirements, Benefits, Pay. We'll not include Qualifications, Skills, Schedule if no content.
We need to avoid duplication. Let's extract role specifics from "About The Role" section:
"Fetch is scaling the systems and experiences that help tens of millions of users discover new ways to engage, earn, and return. We are hiring an Engineering Manager, Play Expansion to lead the team responsible for extending Play beyond the Play hub and making games and rewarding gameplay more discoverable throughout Fetch. The Play Expansion team builds the capabilities that bring Play into the surfaces and journeys where users already engage, including Discover, Nexus, and the broader Fetch information architecture. The team standardizes how Play games, milestones, and rewards are merchandised and awarded across the app, connecting with common patterns such as offerization today and Earning Opportunities in the future. As an Engineering Manager on Play Expansion, you will lead a team of engineers building backend and mobile components and capabilities that support ranking and placing Play content, including games and milestones, across multiple app surfaces, for improved discoverability and outcomes. You will partner with engineers and peer teams across Play and other Fetch pillars to translate defined product requirements into clear team plans, unblock execution, and make pragmatic technical tradeoffs. This role is accountable for the measurable outcomes, health, and technical quality of the single team, and requires enough hands-on technical depth to guide design discussions, review tradeoffs, and help the team build sustainably. This is a full-time role that can be held from one of our US offices or remotely in the United States."
That's the role description.
Now Responsibilities: list from "What You’ll Do At Fetch (Role Responsibilities)" bullet points.
We need to convert each bullet to
- .
Responsibilities list:
- Lead, coach, and develop a team of software engineers across multiple experience levels
- Set clear expectations, provide regular feedback, and support career growth and performance management
- Own delivery for the Play Expansion roadmap, ensuring predictable execution and high-quality outcomes
- Translate product and business goals into clear technical plans and milestones
- Help the team prioritize, sequence, and unblock multiple workstreams while clarifying tradeoffs around scope, quality, and timing
- Partner with senior and staff engineers to guide system design, architecture, code quality, and technical decision-making within the team
- Collaborate with Product, Design, Data, Support, and engineering teams across Play and other Fetch pillars to align dependencies and deliver cohesive user experiences
- Ensure systems are scalable, reliable, observable, and resilient under high traffic and transaction volume
- Balance delivery velocity with long-term technical health and operational excellence
- Improve team processes, reduce operational overhead, and drive continuous improvement
- Communicate progress, risks, and tradeoffs clearly to stakeholders and leadership
- Foster a culture of ownership, quality, and accountability
- Support engineers in using AI-assisted tools such as GitHub Copilot or Claude Code to improve development velocity, documentation, and code quality
Now Requirements: from "In Your Toolbox (Minimum Requirements)" bullet points.
List:
- Experience leading software engineers as an Engineering Manager or technical lead, with readiness to own people management for a small team
- 8+ years of experience in software engineering, technical leadership, or closely related work
- Strong technical background in backend systems and/or native mobile applications, with the ability to guide engineers across both
- Ability to stay close to technical execution through design reviews, code reviews, architectural discussions, and tradeoff analysis
- Experience delivering high-quality, customer-facing consumer products at meaningful scale
- Ability to translate product and business goals into clear technical plans, team priorities, and measurable outcomes
- Sound technical judgment for balancing delivery speed, scalability, reliability, maintainability, and operational health
- Experience collaborating across engineering teams and navigating dependencies in a cross-functional product environment
- Strong communication skills, including the ability to navigate differing viewpoints and advocate for realistic scope and technical constraints
- Commitment to engineering best practices including testing, observability, incident response, and active management of technical debt
- Ability to work effectively with remote teammates across US time zones
Now Benefits: from benefits section.
List:
- Equity: We offer full-time employees equity in Fetch, so that everyone can benefit from Fetch’s growth.
- 401k Match: Dollar-for-dollar match up to 4%.
- Benefits for humans and pets: We offer comprehensive medical, dental and vision plans for everyone including your pets.
- Continuing Education: Fetch provides ten thousand per year in education reimbursement.
- Employee Resource Groups: Take part in employee-led groups that are centered around fostering a diverse and inclusive workplace through events, dialogue and advocacy. The ERGs participate in our Inclusion Council with members of executive leadership.
- Paid Time Off: On top of our flexible PTO, Fetch observes 9 paid holidays, as well as our year-end week-long break.
- Robust Leave Policies: 20 weeks of paid parental leave for primary caregivers, 14 weeks for secondary caregivers, and a flexible return to work schedule.
- Calvin Care Cash: Employees who are welcoming new family members will also receive a one time $2,000 incentive to assist employees with covering the cost of childcare, clothing, diapers and much more!
- Flexible Work Environment: Collaborate with your team in one of our stunning offices, or you can work fully remotely from anywhere in the US. We’ll ensure you are equally equipped with the hardware and software you need to get your job done in the comfort of your home. (applicable for most roles)
Now Pay: compensation range.
- The base salary range for this position is $167,875 - $197,500.
We could also mention equity etc but that's in Benefits.
Now About the role: Should we include company overview plus role description? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview and role description under About the role. But we already have Responsibilities separate. So About the role could contain the company overview (the first big paragraph) plus the role description from "About The Role". That would be substantive.
Let's craft About the role prose: combine the introductory paragraph (What we’re building...) and the role description paragraph(s). Ensure we don't repeat.
We need to avoid boilerplate like "Fetch is an equal opportunity employer". Already removed.
Now produce HTML:
About the role
...combined text...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
The base salary range for this position is $167,875 - $197,500.
We should not include Schedule.
Check for any duplicated lines: ensure we didn't repeat any bullet.
Now craft the combined About the role text.
First paragraph: "What we’re building and why we’re building it
- for lists,
for prose. We need to preserve all substantive info. Let's extract content. Intro: "What we’re building and why we’re building it. Fetch helps people live rewarded every day, with a vision to become the rewards destination for everyone. We turn everyday activities into meaningful rewards, whether it’s grocery shopping, grabbing a quick meal, or playing a favorite mobile game. To date, we’ve awarded more than $1 billion in Fetch Points to our users. Each day, more than 13 million receipts are submitted on Fetch, providing visibility into over $212 billion in gross merchandise value. This creates the largest retail-agnostic, SKU-level view of household spending, powering Fetch as an outcomes-based advertising platform that helps brands acquire and retain lifelong consumers. The Fetch app is available on the App Store and Google Play, with more than 6 million five-star reviews from a highly engaged and loyal user base. It’s not just our users who believe in Fetch: with investments from Softbank, ICONIQ, DST, Greycroft, and partnerships ranging from challenger brands to Fortune 500 companies, Fetch is reshaping how brands and consumers connect in the marketplace. When you work at Fetch, you play a vital role in a platform that drives brand loyalty and creates lifelong consumers with the power of Fetch points. User and partner success are at the heart of everything we do, and we extend that same commitment to our employees. At Fetch, we value curiosity, adaptability, and the confidence to explore new tools, especially AI, to drive smarter, faster work. You don’t need to be an expert, but you should be ready to learn quickly and think critically. We welcome learners who move fast, challenge the status quo, and shape what’s next, with us. Ranked as one of America’s Best Startup Employers by Forbes for two years in a row, Fetch fosters a people-first culture rooted in trust, accountability, and innovation. We encourage our employees to challenge ideas, think bigger, and always bring the fun to Fetch." That's a lot of prose. Could be placed under About the role? Actually About the role section should contain description of role. The intro is more about company. But we need to preserve all substantive info; we could put it under About the role as a preamble, but maybe better to have a separate "About Fetch" section? Not in allowed headings list. 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? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we need to map content to those headings. The intro could go under About the role (maybe as part of role description). But About the role heading should contain role specifics. However we also have a separate "About The Role" heading in the posting. So we can put the company overview under About the role as well, but maybe we should split: About the role includes both company overview and role specifics? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role, Responsibilities, Requirements, Benefits, Pay. We'll not include Qualifications, Skills, Schedule if no content. We need to avoid duplication. Let's extract role specifics from "About The Role" section: "Fetch is scaling the systems and experiences that help tens of millions of users discover new ways to engage, earn, and return. We are hiring an Engineering Manager, Play Expansion to lead the team responsible for extending Play beyond the Play hub and making games and rewarding gameplay more discoverable throughout Fetch. The Play Expansion team builds the capabilities that bring Play into the surfaces and journeys where users already engage, including Discover, Nexus, and the broader Fetch information architecture. The team standardizes how Play games, milestones, and rewards are merchandised and awarded across the app, connecting with common patterns such as offerization today and Earning Opportunities in the future. As an Engineering Manager on Play Expansion, you will lead a team of engineers building backend and mobile components and capabilities that support ranking and placing Play content, including games and milestones, across multiple app surfaces, for improved discoverability and outcomes. You will partner with engineers and peer teams across Play and other Fetch pillars to translate defined product requirements into clear team plans, unblock execution, and make pragmatic technical tradeoffs. This role is accountable for the measurable outcomes, health, and technical quality of the single team, and requires enough hands-on technical depth to guide design discussions, review tradeoffs, and help the team build sustainably. This is a full-time role that can be held from one of our US offices or remotely in the United States." That's the role description. Now Responsibilities: list from "What You’ll Do At Fetch (Role Responsibilities)" bullet points. We need to convert each bullet to
- .
Responsibilities list:
- Lead, coach, and develop a team of software engineers across multiple experience levels
- Set clear expectations, provide regular feedback, and support career growth and performance management
- Own delivery for the Play Expansion roadmap, ensuring predictable execution and high-quality outcomes
- Translate product and business goals into clear technical plans and milestones
- Help the team prioritize, sequence, and unblock multiple workstreams while clarifying tradeoffs around scope, quality, and timing
- Partner with senior and staff engineers to guide system design, architecture, code quality, and technical decision-making within the team
- Collaborate with Product, Design, Data, Support, and engineering teams across Play and other Fetch pillars to align dependencies and deliver cohesive user experiences
- Ensure systems are scalable, reliable, observable, and resilient under high traffic and transaction volume
- Balance delivery velocity with long-term technical health and operational excellence
- Improve team processes, reduce operational overhead, and drive continuous improvement
- Communicate progress, risks, and tradeoffs clearly to stakeholders and leadership
- Foster a culture of ownership, quality, and accountability
- Support engineers in using AI-assisted tools such as GitHub Copilot or Claude Code to improve development velocity, documentation, and code quality
Now Requirements: from "In Your Toolbox (Minimum Requirements)" bullet points.
List:
- Experience leading software engineers as an Engineering Manager or technical lead, with readiness to own people management for a small team
- 8+ years of experience in software engineering, technical leadership, or closely related work
- Strong technical background in backend systems and/or native mobile applications, with the ability to guide engineers across both
- Ability to stay close to technical execution through design reviews, code reviews, architectural discussions, and tradeoff analysis
- Experience delivering high-quality, customer-facing consumer products at meaningful scale
- Ability to translate product and business goals into clear technical plans, team priorities, and measurable outcomes
- Sound technical judgment for balancing delivery speed, scalability, reliability, maintainability, and operational health
- Experience collaborating across engineering teams and navigating dependencies in a cross-functional product environment
- Strong communication skills, including the ability to navigate differing viewpoints and advocate for realistic scope and technical constraints
- Commitment to engineering best practices including testing, observability, incident response, and active management of technical debt
- Ability to work effectively with remote teammates across US time zones
Now Benefits: from benefits section.
List:
- Equity: We offer full-time employees equity in Fetch, so that everyone can benefit from Fetch’s growth.
- 401k Match: Dollar-for-dollar match up to 4%.
- Benefits for humans and pets: We offer comprehensive medical, dental and vision plans for everyone including your pets.
- Continuing Education: Fetch provides ten thousand per year in education reimbursement.
- Employee Resource Groups: Take part in employee-led groups that are centered around fostering a diverse and inclusive workplace through events, dialogue and advocacy. The ERGs participate in our Inclusion Council with members of executive leadership.
- Paid Time Off: On top of our flexible PTO, Fetch observes 9 paid holidays, as well as our year-end week-long break.
- Robust Leave Policies: 20 weeks of paid parental leave for primary caregivers, 14 weeks for secondary caregivers, and a flexible return to work schedule.
- Calvin Care Cash: Employees who are welcoming new family members will also receive a one time $2,000 incentive to assist employees with covering the cost of childcare, clothing, diapers and much more!
- Flexible Work Environment: Collaborate with your team in one of our stunning offices, or you can work fully remotely from anywhere in the US. We’ll ensure you are equally equipped with the hardware and software you need to get your job done in the comfort of your home. (applicable for most roles)
Now Pay: compensation range.
- The base salary range for this position is $167,875 - $197,500.
We could also mention equity etc but that's in Benefits.
Now About the role: Should we include company overview plus role description? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview and role description under About the role. But we already have Responsibilities separate. So About the role could contain the company overview (the first big paragraph) plus the role description from "About The Role". That would be substantive.
Let's craft About the role prose: combine the introductory paragraph (What we’re building...) and the role description paragraph(s). Ensure we don't repeat.
We need to avoid boilerplate like "Fetch is an equal opportunity employer". Already removed.
Now produce HTML:
About the role
...combined text...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
The base salary range for this position is $167,875 - $197,500.
We should not include Schedule. Check for any duplicated lines: ensure we didn't repeat any bullet. Now craft the combined About the role text. First paragraph: "What we’re building and why we’re building it