Engineering Manager, DoorDash for Business
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include: About The Team, About The Role, maybe "What You'll Do" (the bullet list under "You're Excited About This Opportunity Because You Will…") could be Responsibilities. "We're Excited About You Because You…" could be Requirements/Qualifications. Compensation: they gave base salary range and mention equity grants. Benefits: they described benefits package. Pay: they gave salary range; we could put Pay section. Schedule: they mention hybrid position, location requirement, but not schedule details like full-time etc. Might not need Schedule.
We must not include filler like "commensurate with experience". The compensation section includes base salary range and equity grants. That's specific. Benefits: they list many benefits. So we can include Benefits section.
We need to remove legal boilerplate: EEO, diversity statement, non-discrimination, Fair Chance, Covey, scam warnings, etc. Also remove "About DoorDash" mission statement? That might be considered boilerplate? It's not exactly legal but could be considered generic company description. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About DoorDash" paragraph is not legal but maybe considered generic fluff; but it's substantive? It's about mission. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About DoorDash" is substantive about company. However it's somewhat generic but still part of posting. I'd keep it maybe as a section? But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company" heading. Could we include it as a
without heading? Possibly we can just include it as a paragraph after the sections? The instruction says output ONLY the HTML fragment, no /. We can include multiple sections with headings and paragraphs. If we don't have a heading for About DoorDash, we could just put a
after the sections. That's acceptable.
We must not repeat the job title as a heading. The job title is Engineering Manager. Not used.
We must not put Job ID/requisition numbers as headings; none present.
We need to decide on sections: About The Team (maybe as About the team heading). About The Role (maybe as About the role). Then Responsibilities (the bullet list under "You're Excited About This Opportunity Because You Will…"). Then Requirements/Qualifications (the bullet list under "We're Excited About You Because You…"). Then Benefits. Then Pay. Possibly also Skills? Not needed.
We must not create sections with filler. Ensure each heading has real content.
Let's extract content.
About The Team:
"DoorDash for Business is how companies feed their people. We build the products that let a company run a recurring team lunch, give every employee a meal budget, cater an event or meeting and manage all of it through a single corporate account - across every brand and every market DoorDash operates in."
That's substantive.
About The Role:
"We're looking for an Engineering Manager to lead a team in DoorDash for Business. Our domain runs from the moment an order is placed to everything a company needs to administer it: high-complexity ordering for catering, recurring team meals, and group orders; the admin portal, identity, and member management that companies run their account on; budgets and policy enforcement; and the expense and travel integrations that connect us to our customers' finance systems. You'll own a pod of 8-10 engineers with a critical charter inside that domain, real revenue attached to it, and close partnership with Product, Design, and Sales Strategy & Operations. You must be located in the Seattle, San Francisco, Sunnyvale, or New York Metro Area for this hybrid position."
That's substantive.
Now "You're Excited About This Opportunity Because You Will…" bullet points:
- Own a business-critical charter end to end - set technical direction, define the roadmap with your PM and Business counterparts, and be accountable for what ships and how well it runs.
- Build and grow a team - Hire, level up, and retain engineers; set the bar for what good looks like on your pod; give people work that stretches them.
- Work on a genuinely global product - Your charter serves the US alongside EMEA, LATAM, and APAC, with partner pods in India, Helsinki, and Brazil. You'll help decide what's built once globally versus what needs regional variation and build the partnerships across time zones to make that stick.
- Take on real architectural weight - Consolidating onto one global stack means untangling parallel implementations, drawing clean service-ownership lines, and making migration calls with production traffic on them.
- Raise the operational bar - Corporate orders happen at lunch, in every time zone, with no room for a bad day. You'll own on-call health, incident response, and the reliability investments that make both sustainable.
- Partner directly with the go-to-market side - Sales and business partners bring you enterprise customer needs constantly; you'll help decide what's a platform capability versus a one-off, and you'll be in the room for it.
These are responsibilities/duties.
Now "We're Excited About You Because You…" bullet points:
- Have 2+ years managing engineers (including hiring and performance management) on top of a strong track record as a senior individual contributor.
- Have shipped and operated production systems at scale - you're comfortable in the architecture conversation and can hold your own with your most senior engineer.
- Have led work spanning multiple teams or geographies, and you know how to build trust with a pod you don't sit next to.
- Set direction under ambiguity. You can take a broad charter, decompose it into a roadmap, and say no to the things that don't matter this half.
- Own outcomes, not output - you measure your team by customer and business impact, and you're fluent talking about both.
- Care about craft and operational excellence: testing, observability, on-call load, and paying down the debt that slows a team.
- Communicate clearly with non-engineering partners - Product, Design, Sales, Operations, Finance.
These are qualifications/requirements.
Compensation:
"The successful candidate’s starting pay will fall within the pay range listed below and is determined based on job-related factors including, but not limited to, skills, experience, qualifications, work location, and market conditions. Base salary is localized according to an employee’s work location. Ranges are market-dependent and may be modified in the future. In addition to base salary, the compensation for this role includes opportunities for equity grants. Talk to your recruiter for more information."
Then later: "The national base pay range for this position within the United States, including Illinois and Colorado. $193,800—$285,000 USD"
Thus Pay section: include that range and note equity grants.
Benefits:
"DoorDash cares about you and your overall well-being. That’s why we offer a comprehensive benefits package to all regular employees, which includes a 401(k) plan with employer matching, 16 weeks of paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave in compliance with applicable laws (e.g. Colorado Healthy Families and Workplaces Act). DoorDash also offers medical, dental, and vision benefits, 11 paid holidays, disability and basic life insurance, family-forming assistance, and a mental health program, among others. To learn more about our benefits, visit our careers page here. See Below For Paid Time Off Details For salaried roles: flexible paid time off/vacation, plus 80 hours of paid sick time per year. For hourly roles: vacation accrued at about 1 hour for every 25.97 hours worked (e.g. about 6.7 hours/month if working 40 hours/week; about 3.4 hours/month if working 20 hours/week), and paid sick time accrued at 1 hour for every 30 hours worked (e.g. about 5.8 hours/month if working 40 hours/week; about 2.9 hours/month if working 20 hours/week)."
We can include Benefits section with bullet list of benefits.
We must not include the "See Below For Paid Time Off Details" as heading; we can incorporate into benefits list.
We must not include duplicated lines.
We must not include legal EEO etc.
We must not include "About DoorDash" mission statement? It's not legal but maybe considered generic; but we can keep as a paragraph after sections if we want. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About DoorDash paragraph is substantive about company mission. I'd include it as a
without heading, maybe at the end.
But we need to ensure we don't create sections with filler. The About DoorDash paragraph is not a heading; it's just a paragraph. That's fine.
Now produce HTML fragment.
Structure:
About the Team
DoorDash for Business is how companies feed their people. We build the products that let a company run a recurring team lunch, give every employee a meal budget, cater an event or meeting and manage all of it through a single corporate account - across every brand and every market DoorDash operates in.
About the Role
We're looking for an Engineering Manager to lead a team in DoorDash for Business. Our domain runs from the moment an order is placed to everything a company needs to administer it: high-complexity ordering for catering, recurring team meals, and group orders; the admin portal, identity, and member management that companies run their account on; budgets and policy enforcement; and the expense and travel integrations that connect us to our customers' finance systems. You'll own a pod of 8-10 engineers with a critical charter inside that domain, real revenue attached to it, and close partnership with Product, Design, and Sales Strategy & Operations. You must be located in the Seattle, San Francisco, Sunnyvale, or New York Metro Area for this hybrid position.
Responsibilities
- Own a business-critical charter end to end - set technical direction, define the roadmap with your PM and Business counterparts, and be accountable for what ships and how well it runs.
- Build and grow a team - Hire, level up, and retain engineers; set the bar for what good looks like on your pod; give people work that stretches them.
- Work on a genuinely global product - Your charter serves the US alongside EMEA, LATAM, and APAC, with partner pods in India, Helsinki, and Brazil. You
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About The Team, About The Role, maybe "What You'll Do" (the bullet list under "You're Excited About This Opportunity Because You Will…") could be Responsibilities. "We're Excited About You Because You…" could be Requirements/Qualifications. Compensation: they gave base salary range and mention equity grants. Benefits: they described benefits package. Pay: they gave salary range; we could put Pay section. Schedule: they mention hybrid position, location requirement, but not schedule details like full-time etc. Might not need Schedule. We must not include filler like "commensurate with experience". The compensation section includes base salary range and equity grants. That's specific. Benefits: they list many benefits. So we can include Benefits section. We need to remove legal boilerplate: EEO, diversity statement, non-discrimination, Fair Chance, Covey, scam warnings, etc. Also remove "About DoorDash" mission statement? That might be considered boilerplate? It's not exactly legal but could be considered generic company description. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About DoorDash" paragraph is not legal but maybe considered generic fluff; but it's substantive? It's about mission. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About DoorDash" is substantive about company. However it's somewhat generic but still part of posting. I'd keep it maybe as a section? But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company" heading. Could we include it as a
without heading? Possibly we can just include it as a paragraph after the sections? The instruction says output ONLY the HTML fragment, no /. We can include multiple sections with headings and paragraphs. If we don't have a heading for About DoorDash, we could just put a
after the sections. That's acceptable. We must not repeat the job title as a heading. The job title is Engineering Manager. Not used. We must not put Job ID/requisition numbers as headings; none present. We need to decide on sections: About The Team (maybe as About the team heading). About The Role (maybe as About the role). Then Responsibilities (the bullet list under "You're Excited About This Opportunity Because You Will…"). Then Requirements/Qualifications (the bullet list under "We're Excited About You Because You…"). Then Benefits. Then Pay. Possibly also Skills? Not needed. We must not create sections with filler. Ensure each heading has real content. Let's extract content. About The Team: "DoorDash for Business is how companies feed their people. We build the products that let a company run a recurring team lunch, give every employee a meal budget, cater an event or meeting and manage all of it through a single corporate account - across every brand and every market DoorDash operates in." That's substantive. About The Role: "We're looking for an Engineering Manager to lead a team in DoorDash for Business. Our domain runs from the moment an order is placed to everything a company needs to administer it: high-complexity ordering for catering, recurring team meals, and group orders; the admin portal, identity, and member management that companies run their account on; budgets and policy enforcement; and the expense and travel integrations that connect us to our customers' finance systems. You'll own a pod of 8-10 engineers with a critical charter inside that domain, real revenue attached to it, and close partnership with Product, Design, and Sales Strategy & Operations. You must be located in the Seattle, San Francisco, Sunnyvale, or New York Metro Area for this hybrid position." That's substantive. Now "You're Excited About This Opportunity Because You Will…" bullet points: - Own a business-critical charter end to end - set technical direction, define the roadmap with your PM and Business counterparts, and be accountable for what ships and how well it runs. - Build and grow a team - Hire, level up, and retain engineers; set the bar for what good looks like on your pod; give people work that stretches them. - Work on a genuinely global product - Your charter serves the US alongside EMEA, LATAM, and APAC, with partner pods in India, Helsinki, and Brazil. You'll help decide what's built once globally versus what needs regional variation and build the partnerships across time zones to make that stick. - Take on real architectural weight - Consolidating onto one global stack means untangling parallel implementations, drawing clean service-ownership lines, and making migration calls with production traffic on them. - Raise the operational bar - Corporate orders happen at lunch, in every time zone, with no room for a bad day. You'll own on-call health, incident response, and the reliability investments that make both sustainable. - Partner directly with the go-to-market side - Sales and business partners bring you enterprise customer needs constantly; you'll help decide what's a platform capability versus a one-off, and you'll be in the room for it. These are responsibilities/duties. Now "We're Excited About You Because You…" bullet points: - Have 2+ years managing engineers (including hiring and performance management) on top of a strong track record as a senior individual contributor. - Have shipped and operated production systems at scale - you're comfortable in the architecture conversation and can hold your own with your most senior engineer. - Have led work spanning multiple teams or geographies, and you know how to build trust with a pod you don't sit next to. - Set direction under ambiguity. You can take a broad charter, decompose it into a roadmap, and say no to the things that don't matter this half. - Own outcomes, not output - you measure your team by customer and business impact, and you're fluent talking about both. - Care about craft and operational excellence: testing, observability, on-call load, and paying down the debt that slows a team. - Communicate clearly with non-engineering partners - Product, Design, Sales, Operations, Finance. These are qualifications/requirements. Compensation: "The successful candidate’s starting pay will fall within the pay range listed below and is determined based on job-related factors including, but not limited to, skills, experience, qualifications, work location, and market conditions. Base salary is localized according to an employee’s work location. Ranges are market-dependent and may be modified in the future. In addition to base salary, the compensation for this role includes opportunities for equity grants. Talk to your recruiter for more information." Then later: "The national base pay range for this position within the United States, including Illinois and Colorado. $193,800—$285,000 USD" Thus Pay section: include that range and note equity grants. Benefits: "DoorDash cares about you and your overall well-being. That’s why we offer a comprehensive benefits package to all regular employees, which includes a 401(k) plan with employer matching, 16 weeks of paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave in compliance with applicable laws (e.g. Colorado Healthy Families and Workplaces Act). DoorDash also offers medical, dental, and vision benefits, 11 paid holidays, disability and basic life insurance, family-forming assistance, and a mental health program, among others. To learn more about our benefits, visit our careers page here. See Below For Paid Time Off Details For salaried roles: flexible paid time off/vacation, plus 80 hours of paid sick time per year. For hourly roles: vacation accrued at about 1 hour for every 25.97 hours worked (e.g. about 6.7 hours/month if working 40 hours/week; about 3.4 hours/month if working 20 hours/week), and paid sick time accrued at 1 hour for every 30 hours worked (e.g. about 5.8 hours/month if working 40 hours/week; about 2.9 hours/month if working 20 hours/week)." We can include Benefits section with bullet list of benefits. We must not include the "See Below For Paid Time Off Details" as heading; we can incorporate into benefits list. We must not include duplicated lines. We must not include legal EEO etc. We must not include "About DoorDash" mission statement? It's not legal but maybe considered generic; but we can keep as a paragraph after sections if we want. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About DoorDash paragraph is substantive about company mission. I'd include it as a
without heading, maybe at the end. But we need to ensure we don't create sections with filler. The About DoorDash paragraph is not a heading; it's just a paragraph. That's fine. Now produce HTML fragment. Structure:
About the Team
DoorDash for Business is how companies feed their people. We build the products that let a company run a recurring team lunch, give every employee a meal budget, cater an event or meeting and manage all of it through a single corporate account - across every brand and every market DoorDash operates in.
About the Role
We're looking for an Engineering Manager to lead a team in DoorDash for Business. Our domain runs from the moment an order is placed to everything a company needs to administer it: high-complexity ordering for catering, recurring team meals, and group orders; the admin portal, identity, and member management that companies run their account on; budgets and policy enforcement; and the expense and travel integrations that connect us to our customers' finance systems. You'll own a pod of 8-10 engineers with a critical charter inside that domain, real revenue attached to it, and close partnership with Product, Design, and Sales Strategy & Operations. You must be located in the Seattle, San Francisco, Sunnyvale, or New York Metro Area for this hybrid position.
Responsibilities
- Own a business-critical charter end to end - set technical direction, define the roadmap with your PM and Business counterparts, and be accountable for what ships and how well it runs.
- Build and grow a team - Hire, level up, and retain engineers; set the bar for what good looks like on your pod; give people work that stretches them.
- Work on a genuinely global product - Your charter serves the US alongside EMEA, LATAM, and APAC, with partner pods in India, Helsinki, and Brazil. You