Technical Sourcer, Engineering
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 (the page already shows it) and 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.
Content:
- About The Team: paragraph describing team.
- About The Role: description of role, remote location, responsibilities.
- You’re Excited About This Opportunity Because You Will…: list of duties/responsibilities.
- We’re Excited About You Because…: list of qualifications/requirements.
- Compensation: includes pay range and equity, benefits description.
- Benefits: described in detail (401(k), parental leave, wellness, commuter, PTO, sick leave, medical/dental/vision, holidays, disability, life insurance, family-forming assistance, mental health program, etc.) Also PTO details.
- About DoorDash: mission statement etc. Could be considered "About the Company" but not required heading; maybe we can include as a paragraph under a generic section? The instruction only lists certain headings; we can still use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we could also use other headings if needed? Probably stick to those.
Thus we can have sections:
About the Team
...
About the Role
...
Responsibilities
- ...
(list from "You’re Excited About This Opportunity Because You Will…")
Requirements
- ...
(list from "We’re Excited About You Because…")
Benefits
- ...
(list benefits)
Pay
... pay range ...
We should not include Schedule because not specified.
We need to preserve all substantive information. Let's extract.
About The Team paragraph:
"The DoorDash Technical Recruiting team supports the Engineering, Design, Analytics, and Product Management organizations, and is made up of recruiters, sourcers, and coordinators who partner with our technical leaders to hire the best talent at DoorDash. Our Technical Sourcing team owns the earliest, highest-leverage part of the hiring funnel for Engineering. We build market maps, identify talent, and drive outreach for some of DoorDash's most senior and hardest-to-fill technical roles — with real influence over how DoorDash builds its engineering bench."
That's it.
About The Role paragraph:
"This is a remote role that can be located in a US central or east coast time zone. As a Technical Sourcer, you will be a strategic sourcing partner to global Engineering hiring managers and Technical Recruiters, responsible for building and executing sourcing strategies for senior and staff+ software engineering and infrastructure roles. You'll own market mapping, competitive intelligence, and outreach for a portfolio of some of our most critical and hardest-to-fill technical reqs. This is a high-impact role for someone who thrives with a high degree of autonomy, has deep fluency in technical talent markets, and can build trusted partnerships with engineering leaders."
That's the prose.
Now responsibilities list (You’re Excited About This Opportunity Because You Will…):
- Partner directly with Technical Recruiters and Engineering Hiring Managers to build and execute sourcing strategies for engineering roles across all levels.
- Own market mapping and competitive intelligence to identify where the best technical talent lives and how to reach it.
- Drive outreach and initial candidate engagement for a portfolio of concurrent, hard-to-fill technical reqs.
- Consult with hiring managers on role scoping, leveling, and sourcing strategy.
- Present sourcing strategy and market insights to cross-functional recruiting and engineering partners.
- Calibrate candidate profiles with recruiters and hiring managers using funnel data — submittals, conversion, and time-to-fill.
- Deliver an exceptional, high-touch candidate experience from first outreach through handoff to the interview process.
- Contribute to sourcing process improvements, tooling, and market-intel sharing across the Technical Sourcing team.
Now requirements list (We’re Excited About You Because…):
- You have 3+ years of technical sourcing/recruiting experience, ideally sourcing for senior/staff+ software engineering or infrastructure roles.
- You have expert-level boolean/x-ray search skills, and fluency with sourcing tools (LinkedIn Recruiter, Gem, GitHub, etc.), plus strong market-mapping and competitive-intelligence ability.
- You have a proven track record of consulting with hiring managers on role scoping, leveling, and sourcing strategy.
- You have excellent written outreach and candidate engagement skills, with a track record of delivering a great candidate experience.
- You are self-motivated and intellectually curious, and comfortable owning a portfolio of concurrent reqs with a high degree of autonomy.
- You are comfortable leveraging AI tools and emerging sourcing techniques from AI-assisted search and market research to LLM-based outreach drafting to source faster and more effectively.
Now benefits: The paragraph after compensation includes many benefits. Let's extract:
"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 at https://careers.doordash.com/. 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)."
Also later there is duplicate but we can include once.
Thus benefits list items:
- 401(k) plan with employer matching
- 16 weeks of paid parental leave
- Wellness benefits
- Commuter benefits match
- Paid time off and paid sick leave (compliant with applicable laws)
- Medical, dental, and vision benefits
- 11 paid holidays
- Disability and basic life insurance
- Family-forming assistance
- Mental health program
- Paid time off details: flexible PTO/vacation + 80 hours paid sick time per year (for salaried)
- Vacation accrual details for hourly roles (maybe not needed as role is salaried? but we can include)
- Paid sick time accrual details for hourly roles
We could combine into bullet list.
Now Pay section: The posting includes: "The national base pay range for this position within the United States, including Illinois and Colorado. $85,000—$125,000 USD". Also earlier there is a placeholder line with [$XXX,XXX – $XXX,XXX USD — confirm exact range with Compensation/Finance] but then later they give actual range. We should include the actual range.
Thus Pay paragraph: "The national base pay range for this position within the United States, including Illinois and Colorado, is $85,000—$125,000 USD."
We could also mention that compensation includes equity grants, base salary localized, etc. But we already have that in compensation paragraph earlier. However we should not duplicate. The instruction says preserve ALL substantive information; we can include compensation details in Pay section, maybe also mention equity. Let's include:
Pay: base salary range $85,000—$125,000 USD, plus equity opportunities, base salary localized per work location.
Now we need to remove boilerplate: EEO, diversity statement, non-discrimination, scam warning, etc. Also remove duplicated lines (the compensation and benefits paragraphs appear twice). We'll keep one copy.
Also remove "About DoorDash" mission etc? That's not required heading but could be considered "About the Company". Not in list of headings but we could still include as a paragraph under maybe a generic section? 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 to be safe we could omit About DoorDash section, as it's not required and might be considered boilerplate? It's substantive about mission, but maybe we can include as a paragraph under a generic section like
but no heading. However the instruction says "Prefer a few substantive sections over many thin ones." Including a mission paragraph without heading might be okay as a
after sections. But we need to decide.
Given the instruction to preserve ALL substantive information, we should include the mission statement somewhere. Could add a section
About DoorDash
though not in the example list but seems reasonable. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. So we can use other headings like About DoorDash. Let's include.
Thus final HTML:
About the Team
...
About the Role
...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
The national base pay range for this position within the United States, including Illinois and Colorado, is $85,000—$125,000 USD. Base salary is localized according to work location; the role also includes equity grant opportunities.
About DoorDash
At DoorDash, our mission to empower local economies shapes how our team members move quickly, learn, and reiterate in order to make impactful decisions that display empathy
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. Content: - About The Team: paragraph describing team. - About The Role: description of role, remote location, responsibilities. - You’re Excited About This Opportunity Because You Will…: list of duties/responsibilities. - We’re Excited About You Because…: list of qualifications/requirements. - Compensation: includes pay range and equity, benefits description. - Benefits: described in detail (401(k), parental leave, wellness, commuter, PTO, sick leave, medical/dental/vision, holidays, disability, life insurance, family-forming assistance, mental health program, etc.) Also PTO details. - About DoorDash: mission statement etc. Could be considered "About the Company" but not required heading; maybe we can include as a paragraph under a generic section? The instruction only lists certain headings; we can still use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we could also use other headings if needed? Probably stick to those.
Thus we can have sections:
About the Team
...
About the Role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Pay
... pay range ...
We should not include Schedule because not specified. We need to preserve all substantive information. Let's extract. About The Team paragraph: "The DoorDash Technical Recruiting team supports the Engineering, Design, Analytics, and Product Management organizations, and is made up of recruiters, sourcers, and coordinators who partner with our technical leaders to hire the best talent at DoorDash. Our Technical Sourcing team owns the earliest, highest-leverage part of the hiring funnel for Engineering. We build market maps, identify talent, and drive outreach for some of DoorDash's most senior and hardest-to-fill technical roles — with real influence over how DoorDash builds its engineering bench." That's it. About The Role paragraph: "This is a remote role that can be located in a US central or east coast time zone. As a Technical Sourcer, you will be a strategic sourcing partner to global Engineering hiring managers and Technical Recruiters, responsible for building and executing sourcing strategies for senior and staff+ software engineering and infrastructure roles. You'll own market mapping, competitive intelligence, and outreach for a portfolio of some of our most critical and hardest-to-fill technical reqs. This is a high-impact role for someone who thrives with a high degree of autonomy, has deep fluency in technical talent markets, and can build trusted partnerships with engineering leaders." That's the prose. Now responsibilities list (You’re Excited About This Opportunity Because You Will…): - Partner directly with Technical Recruiters and Engineering Hiring Managers to build and execute sourcing strategies for engineering roles across all levels. - Own market mapping and competitive intelligence to identify where the best technical talent lives and how to reach it. - Drive outreach and initial candidate engagement for a portfolio of concurrent, hard-to-fill technical reqs. - Consult with hiring managers on role scoping, leveling, and sourcing strategy. - Present sourcing strategy and market insights to cross-functional recruiting and engineering partners. - Calibrate candidate profiles with recruiters and hiring managers using funnel data — submittals, conversion, and time-to-fill. - Deliver an exceptional, high-touch candidate experience from first outreach through handoff to the interview process. - Contribute to sourcing process improvements, tooling, and market-intel sharing across the Technical Sourcing team. Now requirements list (We’re Excited About You Because…): - You have 3+ years of technical sourcing/recruiting experience, ideally sourcing for senior/staff+ software engineering or infrastructure roles. - You have expert-level boolean/x-ray search skills, and fluency with sourcing tools (LinkedIn Recruiter, Gem, GitHub, etc.), plus strong market-mapping and competitive-intelligence ability. - You have a proven track record of consulting with hiring managers on role scoping, leveling, and sourcing strategy. - You have excellent written outreach and candidate engagement skills, with a track record of delivering a great candidate experience. - You are self-motivated and intellectually curious, and comfortable owning a portfolio of concurrent reqs with a high degree of autonomy. - You are comfortable leveraging AI tools and emerging sourcing techniques from AI-assisted search and market research to LLM-based outreach drafting to source faster and more effectively. Now benefits: The paragraph after compensation includes many benefits. Let's extract: "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 at https://careers.doordash.com/. 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)." Also later there is duplicate but we can include once. Thus benefits list items: - 401(k) plan with employer matching - 16 weeks of paid parental leave - Wellness benefits - Commuter benefits match - Paid time off and paid sick leave (compliant with applicable laws) - Medical, dental, and vision benefits - 11 paid holidays - Disability and basic life insurance - Family-forming assistance - Mental health program - Paid time off details: flexible PTO/vacation + 80 hours paid sick time per year (for salaried) - Vacation accrual details for hourly roles (maybe not needed as role is salaried? but we can include) - Paid sick time accrual details for hourly roles We could combine into bullet list. Now Pay section: The posting includes: "The national base pay range for this position within the United States, including Illinois and Colorado. $85,000—$125,000 USD". Also earlier there is a placeholder line with [$XXX,XXX – $XXX,XXX USD — confirm exact range with Compensation/Finance] but then later they give actual range. We should include the actual range. Thus Pay paragraph: "The national base pay range for this position within the United States, including Illinois and Colorado, is $85,000—$125,000 USD." We could also mention that compensation includes equity grants, base salary localized, etc. But we already have that in compensation paragraph earlier. However we should not duplicate. The instruction says preserve ALL substantive information; we can include compensation details in Pay section, maybe also mention equity. Let's include: Pay: base salary range $85,000—$125,000 USD, plus equity opportunities, base salary localized per work location. Now we need to remove boilerplate: EEO, diversity statement, non-discrimination, scam warning, etc. Also remove duplicated lines (the compensation and benefits paragraphs appear twice). We'll keep one copy. Also remove "About DoorDash" mission etc? That's not required heading but could be considered "About the Company". Not in list of headings but we could still include as a paragraph under maybe a generic section? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could omit About DoorDash section, as it's not required and might be considered boilerplate? It's substantive about mission, but maybe we can include as a paragraph under a generic section like
but no heading. However the instruction says "Prefer a few substantive sections over many thin ones." Including a mission paragraph without heading might be okay as a
after sections. But we need to decide. Given the instruction to preserve ALL substantive information, we should include the mission statement somewhere. Could add a section
About DoorDash
though not in the example list but seems reasonable. The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. So we can use other headings like About DoorDash. Let's include.
Thus final HTML:
About the Team
...
About the Role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
The national base pay range for this position within the United States, including Illinois and Colorado, is $85,000—$125,000 USD. Base salary is localized according to work location; the role also includes equity grant opportunities.
About DoorDash
At DoorDash, our mission to empower local economies shapes how our team members move quickly, learn, and reiterate in order to make impactful decisions that display empathy