Senior Analyst, Sales Analytics

We need to output only HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - About The Team (maybe not needed as heading? Could be part of About the role? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role (maybe combine About The Team and About The Role). But we must not repeat job title. - About The Role: description of responsibilities, cross-functional role, etc. - "You’re Excited About This Opportunity Because You Will…" bullet list: Strategize, Experiment, Optimize, Analyze, Influence. Those are responsibilities/duties. - "We’re Excited About You Because…" bullet list: qualifications/experience: 2+ years experience, bachelors degree, highly technical with advanced SQL, basic Python/R, AI, data modeling, analytical thinker, Salesforce experience strongly preferred, proven track record leading cross-functional initiatives, hitting goals by tracking OKRs, succeed in complex fast moving environment, want to dive into company wide training programs. - Compensation: base salary range $88,400—$130,000 USD, plus equity grants. Also mention base salary localized, market-dependent, may be modified. Also mention benefits: comprehensive benefits package includes 401(k) with employer matching, 16 weeks paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave per applicable laws, medical/dental/vision, 11 paid holidays, disability and basic life insurance, family-forming assistance, mental health program, etc. Also mention PTO details: flexible PTO/vacation plus 80 hours paid sick time per year for salaried roles; for hourly roles accrual rates. - Also mention "We expect this position to be filled by 11/3/26." That's a date; maybe include as metadata but not heading. Could be in a short paragraph. - Also mention "Talk to your recruiter for more information." That's application instruction? Might be considered boilerplate; we should remove application instructions. The instruction says remove application instructions. So we should drop "Talk to your recruiter for more information." Also "To learn more about our benefits, visit our careers page here." That's also application instruction? Might be considered boilerplate; we can drop. - Also mention "See Below For Paid Time Off Details" - we have that content; we can keep details. - Also mention "About DoorDash" mission etc. That's company description; could be considered boilerplate? Might be considered not required but could be kept as prose? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About DoorDash" is not exactly those; it's company overview. Might be okay to keep as prose under maybe a section? But we don't have a heading for company overview; we could include as a

  under maybe no heading? But we need to output only HTML fragment; we can include

  paragraphs without heading if they are substantive. 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 we should follow that pattern. Probably we should include sections: About the role (combining About The Team and About The Role), Responsibilities (the "You Will…" list), Requirements/Qualifications/Skills (the "We’re Excited About You Because…" list), Benefits, Pay, Schedule (maybe PTO details). We could combine Requirements, Qualifications, Skills into one section if content overlaps. But we need to avoid thin sections. Let's decide: -

  About the role

  : include description of team and role (About The Team + About The Role paragraphs). Use

  for prose. -

  Responsibilities

  : list of Strategize, Experiment, Optimize, Analyze, Influence. Each as
• . -

  Qualifications

  : list of experience, degree, technical skills, analytical thinker, Salesforce preferred, track record leading cross-functional initiatives, hitting goals via OKRs, succeed in fast moving environment, desire to participate in training programs. Could also include "We expect this position to be filled by 11/3/26." maybe as a short

  after list? That's metadata but not a heading; we can include as a

  . -

  Benefits

  : list of benefits: 401(k) with employer matching, 16 weeks paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave per applicable laws, medical/dental/vision, 11 paid holidays, disability and basic life insurance, family-forming assistance, mental health program. Also maybe mention equity grants? That's compensation; but could be under Pay. -

  Pay

  : base salary range $88,400—$130,000 USD, plus equity grants, base salary localized, market-dependent, may be modified. Also mention compensation includes opportunities for equity grants. -

  Schedule

  : PTO details: flexible paid time off/vacation plus 80 hours paid sick time per year for salaried roles; for hourly roles accrual rates. Could also mention that it's for salaried roles; but we can keep. We must not include filler like "commensurate with experience". Not present. We must not repeat job title. We must not include application instructions like "Talk to your recruiter for more information", "To learn more about our benefits, visit our careers page here", "See Below For Paid Time Off Details" (maybe we can keep the heading but we already have Schedule section; the phrase "See Below For Paid Time Off Details" is just a reference; we can drop it). Also remove duplicated lines. We must preserve all substantive information: ensure we didn't drop any important details. Let's extract details: About The Team paragraph: "The Sales Analytics team at DoorDash is responsible for getting the right information and insights out to drive our business goals. As DoorDash grows both in scale and breadth of offering, the strength of our sales engine and organizational structure must grow with it." About The Role paragraph: "You will be focused on partnering with our sales & strategy teams, who help solve pain points for small business (SMB) merchants on the Doordash platform through various methods such as new product adoption. You will lead analyses to guide our sales team with data-driven insights to unlock growth opportunities within their accounts. This cross-functional role will partner with sales, operations, product, and strategy teams. You will report into a Senior Manager on our Sales Analytics team, which is part of our Sales Operations organization." We can combine these into About the role section. Responsibilities bullet list: The "You’re Excited About This Opportunity Because You Will…" includes: - Strategize – Devise and execute initiatives against the overall sales org strategy for “winning the merchant” while managing stakeholders across multiple lines of business - Experiment – Use data-driven decision-making and sound business judgment to run sales tests and lead market intelligence efforts - Optimize – Build the best merchant acquisition engine so DoorDash continues to offer the highest quality selection for its customers - Analyze – Build models to evaluate the economics, value, and opportunity costs of strategic initiatives to improve sales performance - Influence – Manage cross-functional projects with our sales, partner management, operations, product, engineering, business operations and BD teams to improve the merchant experience and achieve targets We can phrase as list items. Qualifications bullet list: "We’re Excited About You Because…" includes: - You have 2+ years of experience in Analytics, Consulting, or Strategy - You have a bachelors degree or higher - You are highly technical with advanced SQL, basic Python/R, AI, and data modeling experience. - You are an excellent analytical thinker who can deliver actionable recommendations out of complex datasets; Salesforce experience strongly preferred - You have a proven track record of leading cross-functional initiatives, hitting goals by tracking OKRs, and succeeding in a complex and fast moving environment - You’ll want to dive into and participate in company wide training programs (WeDash, etc.) Also "We expect this position to be filled by 11/3/26." That's a separate statement. Compensation: "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." We drop the last sentence. Pay range: "The national base pay range for this position within the United States, including Illinois and Colorado. $88,400—$130,000 USD" 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." Drop the last sentence. PTO details: "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 keep that. We also have "About DoorDash" mission etc. Might be considered boilerplate? It's not exactly legal/EEO etc. It's company overview. Could be kept as prose maybe under no heading? But we might decide to omit to keep sections thin? The instruction says prefer a few substantive sections over many thin ones. Including About DoorDash might be extra but still substantive. However we already have About the role section; we could incorporate a brief company overview into that? But the instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid other headings but we can stick to those. The About DoorDash paragraph is not about the role; it's about the company. Could be considered boilerplate? Not exactly. But to be safe, we could omit it because it's not required for the job posting; but the instruction says preserve ALL substantive information; do NOT invent or summarize away detail