Staff Data Scientist
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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- About Taskrabbit: description of company. Could be considered "About the role"? Actually "About the role" is a heading we could use for description of role. The posting includes "About the Role" heading with description: "Data Science plays a crucial role...". So we should have an
About the role
with that prose.
- Then "What you will work on" is responsibilities. So we can have Responsibilities
with list items.
- Then "Who you are" includes qualifications, requirements, skills. Could split into Requirements, Qualifications, Skills. But we need to decide based on content. The posting includes: BS, MS or Ph.D. in a quantitative field; A minimum of 7 years industry experience in data science; Strong and relevant experience with advanced experimentation and statistical modeling; Excellent analytical and problem-solving skills; Excellent business acumen and strategic thinking skills, especially in a commerce/risk domain; Expert in SQL, experienced in Python, and familiar with data pipeline tooling (e.g. dbt) and git; Bonus points for experience in productionizing ML models and familiarity with ML Ops; A self-starter with the ability to work independently and drive your own projects end-to-end with a track record of landing strong business impact; Ability to communicate complex data findings in a clear and concise manner to an executive audience.
Thus we can categorize: Requirements (education, experience), Skills (technical: SQL, Python, dbt, git, ML Ops), Qualifications maybe overlapping. But we can combine into sections: Requirements (education + experience), Qualifications (maybe business acumen, analytical skills), Skills (technical). However we must avoid thin sections. Perhaps better to have two sections: Requirements (education + experience + core skills) and Responsibilities. But we also have Benefits and Pay and Schedule sections with specific content.
Compensation & Benefits: includes base pay range $170,000 - $225,000. Also mentions bonus, benefits, perks. Then "You’ll love working here because:" includes bullet-like prose about hybrid, people, diverse culture, perks (employer-paid health insurance, 401k match, time off, product stipends, wellness stipends, education stipends, IKEA discounts, reproductive health support). Benefits vary by country. So we have Pay (base pay range) and Benefits (list of perks). Also Schedule: hybrid requiring 2 days in office at SF hub every Tuesday & Wednesday. That's schedule info.
Thus we need sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly Qualifications not needed if covered.
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO, diversity statement, AI-Assisted Prescreening Notice, visa sponsorship note? The visa sponsorship note is substantive? It says "Prior to applying please note: We are currently unable to provide visa sponsorship for this position (including H-1B, OPT, F1, CPT or other employment-based visas). Candidates must be legally authorized to work in the United States without employer sponsorship now or in the future." That's a requirement about work authorization. Should we keep? It's substantive info about eligibility. It's not boilerplate? It's a requirement. Could be placed under Requirements or a separate note. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Visa sponsorship note is not exactly those categories; it's a requirement about work authorization. I'd keep it as part of Requirements.
Also "This role is hybrid requiring 2 days in office at our San Francisco hub every Tuesday & Wednesday (located at 130 Sutter St, San Francisco, CA)." That's schedule.
Now we need to format.
We'll produce:
About the role
Data Science plays a crucial role in driving impact at Taskrabbit. We are seeking a highly skilled and motivated Staff Data Scientist to join us, working closely with cross-functional teams from Product teams and occasionally Commercial Operations to provide data-driven insights and solutions that enhance our products and accelerate growth while minimizing marketplace losses.
Responsibilities
- Be a strategic thought partner with stakeholders in Product and occasionally Commercial Operations to define high-impact analytical problems, and solve them using different analytical and statistical approaches.
- Present actionable insights in a clear and compelling manner.
- Proactively perform analytical deep dives to identify strategic growth opportunities in key business levers with a focus on Product
- Collaborate with stakeholders to define and measure success metrics for new features and products, conduct advanced experimentation and causal inference to optimize product features and user experiences
- Lead central Data Science initiatives, e.g. experimentation system, building data agents, influencing eventing systems, etc.
- Foster a data-driven culture within the organization by advocating for best practices in data analysis and interpretation.
Requirements
- BS, MS or Ph.D. in a quantitative field (e.g., Statistics, Econometrics, Computer Science, Engineering, Mathematics, Data Science, Operations Research, or related field).
- A minimum of 7 years industry experience in data science.
- Strong and relevant experience with advanced experimentation and statistical modeling.
- Excellent analytical and problem-solving skills.
- Excellent business acumen and strategic thinking skills, especially in a commerce/risk domain.
- Ability to communicate complex data findings in a clear and concise manner to an executive audience.
- Must be legally authorized to work in the United States without employer sponsorship now or in the future (no visa sponsorship available).
Skills
- Expert in SQL.
- Experienced in Python.
- Familiar with data pipeline tooling (e.g., dbt) and git.
- Bonus: experience in productionizing ML models and familiarity with ML Ops.
- A self‑starter with the ability to work independently and drive projects end‑to‑end with a track record of landing strong business impact.
Benefits
- Employer‑paid health insurance.
- 401k match with immediate vesting for US‑based employees.
- Generous and flexible time off with 2 company‑wide closure weeks.
- Taskrabbit product stipends.
- Wellness, productivity, and education stipends.
- IKEA discounts.
- Reproductive health support.
- Benefits vary by country of employment.
Pay
The base pay range for this position is $170,000 - $225,000.
Schedule
Hybrid role requiring 2 days in office at the San Francisco hub every Tuesday & Wednesday (located at 130 Sutter St, San Francisco, CA).
We must ensure we didn't include any filler like "commensurate with experience". Not present.
Check for duplication: We included "Ability to communicate complex data findings..." both in Requirements and maybe also in Skills? We placed it only in Requirements. Good.
Check that we didn't include "You’ll love working here because:" prose; we turned that into Benefits list. Good.
Check that we didn't include "Taskrabbit is a hybrid company..." etc. We used schedule.
Check that we didn't include "At Taskrabbit, our approach to compensation is designed to be competitive, transparent, and equitable. Total compensation consists of base pay + bonus + benefits + perks." That's generic; we could include but it's somewhat filler. Might be considered boilerplate? It's not exactly boilerplate but it's generic statement. The instruction: prefer a few substantive sections over many thin ones. Could we include a short paragraph under Pay about total compensation? Might be okay but we already have base pay range. The generic statement could be omitted as not specific. We'll omit.
Check that we didn't include "Prior to applying please note:" we incorporated visa note into Requirements.
Check that we didn't include "Taskrabbit is a hybrid company with employees distributed across the US and EU and a Built In — Best Places to Work (2022, 2023, 2024, 2025) continually ranked across multiple national and regional categories." That's fluff; could be omitted as not specific to role. It's not required. We'll omit.
Check that we didn't include "Join us at Taskrabbit, where your work will be meaningful, your ideas valued, and your potential unleashed!" That's fluff; omit.
Check that we didn't include "About Taskrabbit:" description at top; we omitted because not a section heading; but maybe we could include as part of About the role? The About the role section already has description of role; we could keep the company description as a separate paragraph before sections? The instruction says 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. It doesn't forbid having an introductory paragraph before sections. However they want sections only for specific headings. The intro could be a
before first heading. But they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other
outside sections. However they said "Output ONLY the HTML fragment — no /, no markdown code fences." So we could include a brief intro paragraph about Taskrabbit before the first heading. But is that considered substantive? It's description of company; could be considered relevant. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that description. However they also said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". That's about sections. Intro paragraph is fine
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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About Taskrabbit: description of company. Could be considered "About the role"? Actually "About the role" is a heading we could use for description of role. The posting includes "About the Role" heading with description: "Data Science plays a crucial role...". So we should have an
About the role
with that prose. - Then "What you will work on" is responsibilities. So we can haveResponsibilities
with list items. - Then "Who you are" includes qualifications, requirements, skills. Could split into Requirements, Qualifications, Skills. But we need to decide based on content. The posting includes: BS, MS or Ph.D. in a quantitative field; A minimum of 7 years industry experience in data science; Strong and relevant experience with advanced experimentation and statistical modeling; Excellent analytical and problem-solving skills; Excellent business acumen and strategic thinking skills, especially in a commerce/risk domain; Expert in SQL, experienced in Python, and familiar with data pipeline tooling (e.g. dbt) and git; Bonus points for experience in productionizing ML models and familiarity with ML Ops; A self-starter with the ability to work independently and drive your own projects end-to-end with a track record of landing strong business impact; Ability to communicate complex data findings in a clear and concise manner to an executive audience. Thus we can categorize: Requirements (education, experience), Skills (technical: SQL, Python, dbt, git, ML Ops), Qualifications maybe overlapping. But we can combine into sections: Requirements (education + experience), Qualifications (maybe business acumen, analytical skills), Skills (technical). However we must avoid thin sections. Perhaps better to have two sections: Requirements (education + experience + core skills) and Responsibilities. But we also have Benefits and Pay and Schedule sections with specific content. Compensation & Benefits: includes base pay range $170,000 - $225,000. Also mentions bonus, benefits, perks. Then "You’ll love working here because:" includes bullet-like prose about hybrid, people, diverse culture, perks (employer-paid health insurance, 401k match, time off, product stipends, wellness stipends, education stipends, IKEA discounts, reproductive health support). Benefits vary by country. So we have Pay (base pay range) and Benefits (list of perks). Also Schedule: hybrid requiring 2 days in office at SF hub every Tuesday & Wednesday. That's schedule info. Thus we need sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly Qualifications not needed if covered. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, diversity statement, AI-Assisted Prescreening Notice, visa sponsorship note? The visa sponsorship note is substantive? It says "Prior to applying please note: We are currently unable to provide visa sponsorship for this position (including H-1B, OPT, F1, CPT or other employment-based visas). Candidates must be legally authorized to work in the United States without employer sponsorship now or in the future." That's a requirement about work authorization. Should we keep? It's substantive info about eligibility. It's not boilerplate? It's a requirement. Could be placed under Requirements or a separate note. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Visa sponsorship note is not exactly those categories; it's a requirement about work authorization. I'd keep it as part of Requirements. Also "This role is hybrid requiring 2 days in office at our San Francisco hub every Tuesday & Wednesday (located at 130 Sutter St, San Francisco, CA)." That's schedule. Now we need to format. We'll produce:About the role
Data Science plays a crucial role in driving impact at Taskrabbit. We are seeking a highly skilled and motivated Staff Data Scientist to join us, working closely with cross-functional teams from Product teams and occasionally Commercial Operations to provide data-driven insights and solutions that enhance our products and accelerate growth while minimizing marketplace losses.
Responsibilities
- Be a strategic thought partner with stakeholders in Product and occasionally Commercial Operations to define high-impact analytical problems, and solve them using different analytical and statistical approaches.
- Present actionable insights in a clear and compelling manner.
- Proactively perform analytical deep dives to identify strategic growth opportunities in key business levers with a focus on Product
- Collaborate with stakeholders to define and measure success metrics for new features and products, conduct advanced experimentation and causal inference to optimize product features and user experiences
- Lead central Data Science initiatives, e.g. experimentation system, building data agents, influencing eventing systems, etc.
- Foster a data-driven culture within the organization by advocating for best practices in data analysis and interpretation.
Requirements
- BS, MS or Ph.D. in a quantitative field (e.g., Statistics, Econometrics, Computer Science, Engineering, Mathematics, Data Science, Operations Research, or related field).
- A minimum of 7 years industry experience in data science.
- Strong and relevant experience with advanced experimentation and statistical modeling.
- Excellent analytical and problem-solving skills.
- Excellent business acumen and strategic thinking skills, especially in a commerce/risk domain.
- Ability to communicate complex data findings in a clear and concise manner to an executive audience.
- Must be legally authorized to work in the United States without employer sponsorship now or in the future (no visa sponsorship available).
Skills
- Expert in SQL.
- Experienced in Python.
- Familiar with data pipeline tooling (e.g., dbt) and git.
- Bonus: experience in productionizing ML models and familiarity with ML Ops.
- A self‑starter with the ability to work independently and drive projects end‑to‑end with a track record of landing strong business impact.
Benefits
- Employer‑paid health insurance.
- 401k match with immediate vesting for US‑based employees.
- Generous and flexible time off with 2 company‑wide closure weeks.
- Taskrabbit product stipends.
- Wellness, productivity, and education stipends.
- IKEA discounts.
- Reproductive health support.
- Benefits vary by country of employment.
Pay
The base pay range for this position is $170,000 - $225,000.
Schedule
Hybrid role requiring 2 days in office at the San Francisco hub every Tuesday & Wednesday (located at 130 Sutter St, San Francisco, CA).
We must ensure we didn't include any filler like "commensurate with experience". Not present. Check for duplication: We included "Ability to communicate complex data findings..." both in Requirements and maybe also in Skills? We placed it only in Requirements. Good. Check that we didn't include "You’ll love working here because:" prose; we turned that into Benefits list. Good. Check that we didn't include "Taskrabbit is a hybrid company..." etc. We used schedule. Check that we didn't include "At Taskrabbit, our approach to compensation is designed to be competitive, transparent, and equitable. Total compensation consists of base pay + bonus + benefits + perks." That's generic; we could include but it's somewhat filler. Might be considered boilerplate? It's not exactly boilerplate but it's generic statement. The instruction: prefer a few substantive sections over many thin ones. Could we include a short paragraph under Pay about total compensation? Might be okay but we already have base pay range. The generic statement could be omitted as not specific. We'll omit. Check that we didn't include "Prior to applying please note:" we incorporated visa note into Requirements. Check that we didn't include "Taskrabbit is a hybrid company with employees distributed across the US and EU and a Built In — Best Places to Work (2022, 2023, 2024, 2025) continually ranked across multiple national and regional categories." That's fluff; could be omitted as not specific to role. It's not required. We'll omit. Check that we didn't include "Join us at Taskrabbit, where your work will be meaningful, your ideas valued, and your potential unleashed!" That's fluff; omit. Check that we didn't include "About Taskrabbit:" description at top; we omitted because not a section heading; but maybe we could include as part of About the role? The About the role section already has description of role; we could keep the company description as a separate paragraph before sections? The instruction says 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 shortor drop it. It doesn't forbid having an introductory paragraph before sections. However they want sections only for specific headings. The intro could be a
before first heading. But they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other
outside sections. However they said "Output ONLY the HTML fragment — no /, no markdown code fences." So we could include a brief intro paragraph about Taskrabbit before the first heading. But is that considered substantive? It's description of company; could be considered relevant. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that description. However they also said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". That's about sections. Intro paragraph is fine