Senior Manager : Tax Technology Implementations
DoorDash · Boston, MA · 1 mo ago
Management$155k–$228k/yrFull-time
We need to output HTML fragment with sections: About the team, About the role, Requirements (maybe combine), Benefits, Pay, etc. Must not repeat job title. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About The Team: paragraph(s) describing team.
- About The Role: description of role responsibilities.
- Requirements and design... Actually there is a big block under "About The Role" that includes many responsibilities: "Requirements and design.", "Scope and sequencing.", "Roadmap influence.", "Launch and operational readiness.", "Risk.", "Running the program." These are subheadings within role description. We could treat them as bullet list under responsibilities. Or we could keep them as separate subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the team, About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content.
We have content for About the team, About the role, Responsibilities (the bullet list of duties), Requirements (the list of qualifications/experience), Benefits, Pay (salary range). Possibly Skills (maybe part of requirements). Qualifications maybe same as requirements. We'll decide.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to extract:
About The Team paragraph(s):
"The Tax Technology team owns the technology behind what happens on our platform. We build and run the systems that calculate indirect tax on every transaction — and we go well beyond that. We build the automations and implementations the direct tax team relies on, we support data operations across the tax function, and we develop the tooling and efficiencies that make the wider Tax Force faster. We are a global team spanning three brands: DoorDash, Wolt, and Deliveroo. That reach also makes us one of the most dependency-heavy systems in the company. More than eight separate billing domains feed into our tax services, each with its own architecture, roadmap, and engineering team — and all of them have to work. Getting this right is not optional. Tax has to be correct on every order, the first time. Getting it wrong means incorrect charges to real customers, restatement risk, and audit exposure. We are looking for someone who can hold the whole picture and make it land."
That's the team description.
About The Role paragraph(s):
"The Senior Manager, Tax Technology Implementations reports to the Director of Tax Technology and owns the technical implementation plan between the various domains and our indirect tax calculation service. You have a deep understanding of the indirect Tax subject matter and also the technical partner to the engineering team. You will translate indirect tax requirements into things engineers can build, and you will own the single consolidated plan that tells Tax and Engineering leadership where the program actually stands. You will influence partner teams with your understanding of the problem and source of truth of a trusted plan. You make it easy for partner teams to do the right thing. This role owns the tax outcome of implementations— the requirements, the design judgment, and the technical calls that determine whether it works."
Then there are sub-responsibilities listed:
- Requirements and design. Author tax requirements and acceptance criteria that engineers build against and that hold up under audit. Review design docs and push back where a design won't scale to the tax rules coming.
- Scope and sequencing. Define what's in and out for each integration, own the critical path, and drive what ships when. When a team slips, know within a day what it means downstream — and bring options.
- Roadmap influence. Get tax work prioritized onto eight other teams' roadmaps and defend it when it's bumped — making this a collaboration between the engineering, product teams and tax.
- Launch and operational readiness. Define testing, monitoring, and rollout, set go/no-go and rollback criteria, and make sure each integration lands with runbooks, alerting, and a clear steady-state owner.
- Risk. Own the risk register and escalate with a recommendation attached. Be the person who saw it coming.
- Running the program. Maintain the integrated plan as the source of truth and keep the decision cadence across Tax, Product, Engineering, and Data — reporting status to senior leadership in a format they trust.
Then bullet list of "You're excited about this opportunity because you will…" with several bullet points.
Then "We're excited about you because…" with bullet list of qualifications.
Then Compensation paragraph about pay range, equity, benefits.
Then Benefits paragraph describing benefits.
Then Paid Time Off details.
Then About DoorDash paragraph(s) (mission etc). This could be considered "About the company" but not required as a section; we could include as part of About the team? Probably not needed. The instruction says include a section only when posting has real specific content. We could include "About DoorDash" as a section but not in the list of headings given; but we could treat as "About the company". However the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About the company. Might be safer to omit that section, as it's not required. But we need to preserve ALL substantive information; we cannot drop substantive info. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid adding other sections beyond the list, but the list is examples. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use other headings if needed, but better to stick to those. The About DoorDash content is substantive; we could incorporate it into About the team or About the role? It's about company mission, not team. Could add a section "About DoorDash" as About DoorDash
. That seems reasonable.
We also need to include Benefits section: they list many benefits: 401(k) with employer matching, 16 weeks paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave, medical/dental/vision, 11 paid holidays, disability and basic life insurance, family-forming assistance, mental health program, etc. Also Paid Time Off details.
We need to include Pay section: salary range $155,000—$228,000 USD, plus equity grants.
We need to include Schedule? Not mentioned. So we should not create Schedule section.
We need to include Skills? Could be part of Requirements. We could have Requirements section listing the qualifications/experience. Skills maybe not separate.
We need to ensure we don't repeat job title as heading.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out the EEO statement, diversity statement, non-discrimination, Fair Chance, accommodations notice, NYC notice, Covey tool, recruitment scam warning, etc. Also remove "About DoorDash" maybe? But we decided to keep it as it's substantive about company mission. However the "About DoorDash" includes mission statement etc. That's substantive. We'll keep.
We also need to remove duplicated lines: there may be duplicate sentences? Not many.
Now produce HTML.
Structure:
About the Team
... (team paragraph)
About the Role
... (role intro paragraph)
Responsibilities
- Requirements and design. Author tax requirements and acceptance criteria that engineers build against and that hold up under audit. Review design docs and push back where a design won't scale to the tax rules coming.
- Scope and sequencing. Define what's in and out for each integration, own the critical path, and drive what ships when. When a team slips, know within a day what it means downstream — and bring options.
- Roadmap influence. Get tax work prioritized onto eight other teams' roadmaps and defend it when it's bumped — making this a collaboration between the engineering, product teams and tax.
- Launch and operational readiness. Define testing, monitoring, and rollout, set go/no-go and rollback criteria, and make sure each integration lands with runbooks, alerting, and a clear steady-state owner.
- Risk. Own the risk register and escalate with a recommendation attached. Be the person who saw it coming.
- Running the program. Maintain the integrated plan as the source of truth and keep the decision cadence across Tax, Product, Engineering, and Data — reporting status to senior leadership in a format they trust.
Maybe also include the "You're excited about this opportunity because you will…" bullet points as part of Responsibilities or maybe as a separate section "What you'll do"? But we already have responsibilities covering core duties. The excitement bullets are more about motivations; could be omitted? But they are substantive. Could include as a under a heading "What you'll enjoy" but not in allowed headings. Could incorporate into Responsibilities as additional bullets. However the instruction: "Use - for any list of duties/requirements/benefits". So we can add those as duties. Let's add them as bullets under Responsibilities as well.
The excitement bullets:
- Have visibility across the entire business, solving genuinely complex problems across many domains with both engineering and non-engineering partners.
- Own an end-to-end program rather than a slice of one, with real consequences and real scope.
- Work closely with engineers to shape design decisions, not just receive them.
- Build the connective tissue for a program that spans three brands and multiple jurisdictions.
- Be supported by Anthropics Claude suite of tooling and an extensive tax data mart to speed up analysis, planning, and daily operations.
- Grow a team and a function that is still being defined.
We'll add those as
- under Responsibilities.
Now Requirements/Qualifications: The "We're excited about you because…" bullet list:
- 8+ years in a corporate tax department, public accounting, or technology consulting
- Global or multi-country indirect tax implementation experience, and familiarity with non-US indirect tax regimes.
- Hands-on experience implementing Marketplace Facilitator laws across jurisdictions.
- Program or project management experience across multiple dependent engineering teams, including building plans, milestones, and dependency maps, and driving them to completion.
- Direct engagement with engineering teams on product development, with working knowledge of software development processes. You can read a technical design document and tell whether it will hold.
- Experience defining testing and monitoring strategies for systems where correctness matters.
- Strong analytical skills, high organization, and real attention to detail, with the ability to hold both the big picture and the specifics.
- Comfort operating without formal authority in a highly collaborative, multi-stakeholder environment. You are not afraid to challenge the status quo, and you do it in a way that keeps partners on your side.
We could put these under a section "Requirements" or "Qualifications". Since we have both, we could combine into Requirements. Let's make a section
Requirements
with .
Now Benefits: We'll create Benefits
with listing benefits.
Benefits list from text:
- 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)
- medical, dental, and vision benefits
- 11 paid holidays
- disability and basic life insurance
- family-forming assistance
- mental health program
- (maybe others) "among others
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Key sections: - About The Team: paragraph(s) describing team. - About The Role: description of role responsibilities. - Requirements and design... Actually there is a big block under "About The Role" that includes many responsibilities: "Requirements and design.", "Scope and sequencing.", "Roadmap influence.", "Launch and operational readiness.", "Risk.", "Running the program." These are subheadings within role description. We could treat them as bullet list under responsibilities. Or we could keep them as separate subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the team, About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content.
We have content for About the team, About the role, Responsibilities (the bullet list of duties), Requirements (the list of qualifications/experience), Benefits, Pay (salary range). Possibly Skills (maybe part of requirements). Qualifications maybe same as requirements. We'll decide.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to extract:
About The Team paragraph(s):
"The Tax Technology team owns the technology behind what happens on our platform. We build and run the systems that calculate indirect tax on every transaction — and we go well beyond that. We build the automations and implementations the direct tax team relies on, we support data operations across the tax function, and we develop the tooling and efficiencies that make the wider Tax Force faster. We are a global team spanning three brands: DoorDash, Wolt, and Deliveroo. That reach also makes us one of the most dependency-heavy systems in the company. More than eight separate billing domains feed into our tax services, each with its own architecture, roadmap, and engineering team — and all of them have to work. Getting this right is not optional. Tax has to be correct on every order, the first time. Getting it wrong means incorrect charges to real customers, restatement risk, and audit exposure. We are looking for someone who can hold the whole picture and make it land."
That's the team description.
About The Role paragraph(s):
"The Senior Manager, Tax Technology Implementations reports to the Director of Tax Technology and owns the technical implementation plan between the various domains and our indirect tax calculation service. You have a deep understanding of the indirect Tax subject matter and also the technical partner to the engineering team. You will translate indirect tax requirements into things engineers can build, and you will own the single consolidated plan that tells Tax and Engineering leadership where the program actually stands. You will influence partner teams with your understanding of the problem and source of truth of a trusted plan. You make it easy for partner teams to do the right thing. This role owns the tax outcome of implementations— the requirements, the design judgment, and the technical calls that determine whether it works."
Then there are sub-responsibilities listed:
- Requirements and design. Author tax requirements and acceptance criteria that engineers build against and that hold up under audit. Review design docs and push back where a design won't scale to the tax rules coming.
- Scope and sequencing. Define what's in and out for each integration, own the critical path, and drive what ships when. When a team slips, know within a day what it means downstream — and bring options.
- Roadmap influence. Get tax work prioritized onto eight other teams' roadmaps and defend it when it's bumped — making this a collaboration between the engineering, product teams and tax.
- Launch and operational readiness. Define testing, monitoring, and rollout, set go/no-go and rollback criteria, and make sure each integration lands with runbooks, alerting, and a clear steady-state owner.
- Risk. Own the risk register and escalate with a recommendation attached. Be the person who saw it coming.
- Running the program. Maintain the integrated plan as the source of truth and keep the decision cadence across Tax, Product, Engineering, and Data — reporting status to senior leadership in a format they trust.
Then bullet list of "You're excited about this opportunity because you will…" with several bullet points.
Then "We're excited about you because…" with bullet list of qualifications.
Then Compensation paragraph about pay range, equity, benefits.
Then Benefits paragraph describing benefits.
Then Paid Time Off details.
Then About DoorDash paragraph(s) (mission etc). This could be considered "About the company" but not required as a section; we could include as part of About the team? Probably not needed. The instruction says include a section only when posting has real specific content. We could include "About DoorDash" as a section but not in the list of headings given; but we could treat as "About the company". However the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About the company. Might be safer to omit that section, as it's not required. But we need to preserve ALL substantive information; we cannot drop substantive info. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid adding other sections beyond the list, but the list is examples. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use other headings if needed, but better to stick to those. The About DoorDash content is substantive; we could incorporate it into About the team or About the role? It's about company mission, not team. Could add a section "About DoorDash" as About DoorDash
. That seems reasonable.
We also need to include Benefits section: they list many benefits: 401(k) with employer matching, 16 weeks paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave, medical/dental/vision, 11 paid holidays, disability and basic life insurance, family-forming assistance, mental health program, etc. Also Paid Time Off details.
We need to include Pay section: salary range $155,000—$228,000 USD, plus equity grants.
We need to include Schedule? Not mentioned. So we should not create Schedule section.
We need to include Skills? Could be part of Requirements. We could have Requirements section listing the qualifications/experience. Skills maybe not separate.
We need to ensure we don't repeat job title as heading.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out the EEO statement, diversity statement, non-discrimination, Fair Chance, accommodations notice, NYC notice, Covey tool, recruitment scam warning, etc. Also remove "About DoorDash" maybe? But we decided to keep it as it's substantive about company mission. However the "About DoorDash" includes mission statement etc. That's substantive. We'll keep.
We also need to remove duplicated lines: there may be duplicate sentences? Not many.
Now produce HTML.
Structure:
About the Team
About DoorDash
. That seems reasonable. We also need to include Benefits section: they list many benefits: 401(k) with employer matching, 16 weeks paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave, medical/dental/vision, 11 paid holidays, disability and basic life insurance, family-forming assistance, mental health program, etc. Also Paid Time Off details. We need to include Pay section: salary range $155,000—$228,000 USD, plus equity grants. We need to include Schedule? Not mentioned. So we should not create Schedule section. We need to include Skills? Could be part of Requirements. We could have Requirements section listing the qualifications/experience. Skills maybe not separate. We need to ensure we don't repeat job title as heading. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out the EEO statement, diversity statement, non-discrimination, Fair Chance, accommodations notice, NYC notice, Covey tool, recruitment scam warning, etc. Also remove "About DoorDash" maybe? But we decided to keep it as it's substantive about company mission. However the "About DoorDash" includes mission statement etc. That's substantive. We'll keep. We also need to remove duplicated lines: there may be duplicate sentences? Not many. Now produce HTML. Structure:About the Team
... (team paragraph)
About the Role
... (role intro paragraph)
Responsibilities
- Requirements and design. Author tax requirements and acceptance criteria that engineers build against and that hold up under audit. Review design docs and push back where a design won't scale to the tax rules coming.
- Scope and sequencing. Define what's in and out for each integration, own the critical path, and drive what ships when. When a team slips, know within a day what it means downstream — and bring options.
- Roadmap influence. Get tax work prioritized onto eight other teams' roadmaps and defend it when it's bumped — making this a collaboration between the engineering, product teams and tax.
- Launch and operational readiness. Define testing, monitoring, and rollout, set go/no-go and rollback criteria, and make sure each integration lands with runbooks, alerting, and a clear steady-state owner.
- Risk. Own the risk register and escalate with a recommendation attached. Be the person who saw it coming.
- Running the program. Maintain the integrated plan as the source of truth and keep the decision cadence across Tax, Product, Engineering, and Data — reporting status to senior leadership in a format they trust.
- under a heading "What you'll enjoy" but not in allowed headings. Could incorporate into Responsibilities as additional bullets. However the instruction: "Use
- for any list of duties/requirements/benefits". So we can add those as duties. Let's add them as bullets under Responsibilities as well. The excitement bullets: - Have visibility across the entire business, solving genuinely complex problems across many domains with both engineering and non-engineering partners. - Own an end-to-end program rather than a slice of one, with real consequences and real scope. - Work closely with engineers to shape design decisions, not just receive them. - Build the connective tissue for a program that spans three brands and multiple jurisdictions. - Be supported by Anthropics Claude suite of tooling and an extensive tax data mart to speed up analysis, planning, and daily operations. - Grow a team and a function that is still being defined. We'll add those as
- under Responsibilities.
Now Requirements/Qualifications: The "We're excited about you because…" bullet list:
- 8+ years in a corporate tax department, public accounting, or technology consulting
- Global or multi-country indirect tax implementation experience, and familiarity with non-US indirect tax regimes.
- Hands-on experience implementing Marketplace Facilitator laws across jurisdictions.
- Program or project management experience across multiple dependent engineering teams, including building plans, milestones, and dependency maps, and driving them to completion.
- Direct engagement with engineering teams on product development, with working knowledge of software development processes. You can read a technical design document and tell whether it will hold.
- Experience defining testing and monitoring strategies for systems where correctness matters.
- Strong analytical skills, high organization, and real attention to detail, with the ability to hold both the big picture and the specifics.
- Comfort operating without formal authority in a highly collaborative, multi-stakeholder environment. You are not afraid to challenge the status quo, and you do it in a way that keeps partners on your side.
We could put these under a section "Requirements" or "Qualifications". Since we have both, we could combine into Requirements. Let's make a section
Requirements
with- .
Now Benefits: We'll create
Benefits
with- listing benefits.
Benefits list from text:
- 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)
- medical, dental, and vision benefits
- 11 paid holidays
- disability and basic life insurance
- family-forming assistance
- mental health program
- (maybe others) "among others