Senior Analyst, Sales Analytics

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove "About The Team" maybe? It's not a required heading; but we can include as a 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 we should follow that list. However we can include "About The Team" as maybe not needed. But we can keep it as a

maybe. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings; we should only use those. So we should map content to those headings. We need to extract: - About the role: The paragraph(s) describing role: "About The Role 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. You’re Excited About This Opportunity Because You Will… Strategize – Devise and execute initiatives against the overall sales org strategy for “winning the merchant” while managing stakeholders across multiple lines of businessExperiment – Use data-driven decision-making and sound business judgment to run sales tests and lead market intelligence effortsOptimize – Build the best merchant acquisition engine so DoorDash continues to offer the highest quality selection for its customersAnalyze – Build models to evaluate the economics, value, and opportunity costs of strategic initiatives to improve sales performanceInfluence – 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 format as

prose and maybe

• for bullet points (the bullet list after "You’re Excited About This Opportunity Because You Will…"). - Responsibilities: Could be derived from role description? The posting didn't have a separate "Responsibilities" heading, but we can extract responsibilities from the role description. However instruction: include a section ONLY when the posting has real, specific content for it. There's no explicit "Responsibilities" heading, but we could treat the role description as responsibilities. But we already have About the role. Might be redundant. Safer to not create a Responsibilities section if not explicitly present. However the role description includes responsibilities; but we already used that for About the role. The instruction says prefer a few substantive sections over many thin ones. So we could combine About the role and Responsibilities into one? But they said use headings e.g. About the role, Responsibilities... So we could have both if content exists. Since there is no separate Responsibilities block, maybe we skip Responsibilities. - Requirements: The posting includes "We’re Excited About You Because… You have 2+ years of experience in Analytics, Consulting, or StrategyYou 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 preferredYou have a proven track record of leading cross-functional initiatives, hitting goals by tracking OKRs, and succeeding in a complex and fast moving environmentYou’ll want to dive into and participate in company wide training programs (WeDash, etc.)" We can format as
  • . - Qualifications: Might overlap with Requirements. Could treat Requirements as qualifications. But we have both headings; we need to decide. The posting doesn't have separate Qualifications section; we could skip Qualifications or combine. Since we must not create empty sections, we should not include Qualifications if no specific content distinct from Requirements. However we could treat the bullet list as Qualifications. But we already used Requirements. Might be better to have Requirements and Qualifications combined? But instruction: prefer few substantive sections over many thin ones. So maybe we just have About the role, Requirements, Benefits, Pay. Also maybe Skills? The bullet list includes technical skills; could be Skills section. But we already have Requirements covering experience and skills. Could split: Requirements (experience, education) and Skills (technical). However the posting lumps them together. To avoid thin sections, we could keep one Requirements section that includes both experience and skills. - Benefits: The posting has a paragraph about 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 that content. Could also separate Pay and Schedule sections. - Pay: The posting includes: "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. $88,400—$130,000 USD" We can include Pay section with that info. - Schedule: Not explicitly mentioned. No schedule info. So we should not create Schedule section. - Also maybe "About The Team" could be a section but not in allowed headings; we could omit or treat as part of About the role? Probably omit. We must remove boilerplate: navigation, legal, EEO, scam warning, duplicated lines, application instructions. So we need to cut out sections like "About DoorDash", "Our Commitment to Diversity and Inclusion", "Statement of Non-Discrimination", "Pursuant to the San Francisco Fair Chance Ordinance", "Notice to Applicants for Jobs Located in NYC...", "Beware of recruitment scams", etc. We must preserve all substantive information: that includes the role description, excitement bullets, requirements, benefits, pay range, equity grants, etc. We must not repeat job title. Not present. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Thus final HTML:

    About the role

    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.

    You’re excited about this opportunity because you will:

    • 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

    Requirements

    • 2+ years of experience in Analytics, Consulting, or Strategy
    • Bachelor’s degree or higher
    • Highly technical with advanced SQL, basic Python/R, AI, and data modeling experience
    • Excellent analytical thinker who can deliver actionable recommendations out of complex datasets; Salesforce experience strongly preferred
    • Proven track record of leading cross-functional initiatives, hitting goals by tracking OKRs, and succeeding in a complex and fast‑moving environment
    • Interest in participating in company‑wide training programs (WeDash, etc.)

    Benefits

    DoorDash offers a comprehensive benefits package to all regular employees, including 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). Additionally, employees receive medical, dental, and vision benefits, 11 paid holidays, disability and basic life insurance, family‑forming assistance, and a mental health program.

    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 accrues at about 1 hour for every 25.97 hours worked (≈6.7 hours/month at 40 hrs/week; ≈3.4 hours/month at 20 hrs/week) and paid sick time accrues at 1 hour for every 30 hours worked (≈5.8 hours/month at 40 hrs/week; ≈2.9 hours/month at 20 hrs/week).

    Pay

    The successful candidate’s starting pay will fall within the listed range and is determined based on job‑related factors such as skills, experience, qualifications, work location, and market conditions. Base salary is localized to the employee’s work location; ranges are market‑dependent and may be adjusted in the future. In addition to base salary, the role includes opportunities for equity grants.

    The national base pay range for this position within the United States (including Illinois and Colorado) is $88,400—$130,000 USD.

    We should ensure no extra blank lines? It's fine. Check for any leftover boilerplate: we removed About DoorDash, Diversity, etc. Good. Check for any duplicated lines: we didn't duplicate. Check for any