Pay
$120K–$194K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 3,983 postings in the last year. Stated ranges, not salaries paid.
San Francisco, California, United States
Open 5 months, first seen by us 172 days agoWork setup in the employer’s posting: On-siteFrom the employer’s posting
Employment type in the employer’s posting: FullTimeFrom the employer’s posting
Analyze user behavior to inform the product roadmap and find UX improvements
Design, run, and analyze A/B tests and turn results into product recommendations
Define metrics, guardrails, and dashboards for product and company health
Build reusable tables, models, and documentation for analysis
Automate recurring analysis and build AI-assisted data workflows
analyze user behavior to inform product roadmap, accelerate adoption, and identify opportunities to improve the user experience
form hypotheses, define success metrics, run A/B tests, interpret results, and turn findings into product recommendations
build the metrics, guardrails, dashboards, and reporting workflows that help teams understand product and company health
create tables, models, and documentation that make analysis faster, more consistent, and easier for humans and AI systems to use
automate recurring analysis, build AI-assisted workflows, improve documentation
Open 5 monthsWe first saw this posting 172 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$120K–$194K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 3,983 postings in the last year. Stated ranges, not salaries paid.
Day 172
Up longer than most. Similar jobs usually come down between day 7 and day 60.
Well past Perplexity’s usual: its jobs come down by about day 81.
From 12,339 similar postings that came down, and 6 of Perplexity’s. Coming down is not always a hire.
14 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Experience with dbt, data modeling, or analytics engineering. - Python experience for analysis, automation, or internal tools. - Experience with Snowflake, especially performance and cost-aware querying.
- Strong product sense - you understand user behavior, product tradeoffs, and how to connect analysis to decisions. - SQL expertise - you can navigate a complex data warehouse on your own, reason about grain and joins, and debug data issues when something looks wrong. - Experimentation depth - you have significant experience designing, running, and analyzing A/B tests.
Bonus - Experience with dbt, data modeling, or analytics engineering. - Python experience for analysis, automation, or internal tools.
- AI-native working style - you use LLMs and AI tools to move faster without outsourcing analytical judgment. - Metrics and dashboard experience - you've built useful reporting in tools such as Omni, Mode, Hex, Looker, or similar, and know how to turn metrics into better product decisions. - Comfort with ambiguity - you can take an open-ended question, structure it, execute the analysis, and make a clear recommendation.
- Python experience for analysis, automation, or internal tools. - Experience with Snowflake, especially performance and cost-aware querying. - Experience combining qualitative user research with quantitative product analysis.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Perplexity is AI for people who expect more. This role brings that standard to how we understand our users, shape our product, and decide what to build next.
We're looking for a data scientist who can turn product questions into clear decisions. You'll work across product, engineering, growth, design, and user research to understand user behavior, define metrics, design experiments, and identify the highest-leverage opportunities for the company.
The data team is AI-native by default. We use AI to accelerate analysis, write and review code, explore hypotheses, document data, generate first drafts, and automate recurring workflows. But the core of the role is still judgment: asking the right question, choosing the right metric, designing the right test, and knowing when the answer is strong enough to act on.
What You'll DoDevelop product insights - analyze user behavior to inform product roadmap, accelerate adoption, and identify opportunities to improve the user experience.
Design and analyze experiments - form hypotheses, define success metrics, run A/B tests, interpret results, and turn findings into product recommendations.
Define the metrics that matter - build the metrics, guardrails, dashboards, and reporting workflows that help teams understand product and company health.
Partner across functions - work closely with engineering, product, growth, design, and user research to answer ambiguous questions and drive decisions.
Build reusable data assets - create tables, models, and documentation that make analysis faster, more consistent, and easier for humans and AI systems to use.
Use AI to scale data science - automate recurring analysis, build AI-assisted workflows, improve documentation, and turn one-off investigations into repeatable systems.
Tell the story clearly - communicate findings, assumptions, uncertainty, and recommendations in a way that helps teams make decisions.
6+ years of experience as a data scientist or closely related role.
Strong product sense - you understand user behavior, product tradeoffs, and how to connect analysis to decisions.
SQL expertise - you can navigate a complex data warehouse on your own, reason about grain and joins, and debug data issues when something looks wrong.
Experimentation depth - you have significant experience designing, running, and analyzing A/B tests.
AI-native working style - you use LLMs and AI tools to move faster without outsourcing analytical judgment.
Metrics and dashboard experience - you've built useful reporting in tools such as Omni, Mode, Hex, Looker, or similar, and know how to turn metrics into better product decisions.
Comfort with ambiguity - you can take an open-ended question, structure it, execute the analysis, and make a clear recommendation.
End-to-end ownership - you take responsibility for the work from problem definition to stakeholder adoption.
Experience with dbt, data modeling, or analytics engineering.
Python experience for analysis, automation, or internal tools.
Experience with Snowflake, especially performance and cost-aware querying.
Experience combining qualitative user research with quantitative product analysis.
Experience as one of the first data scientists at an early or growth-stage company.
ML experience or experience working across multiple product surfaces.
Define data science at Perplexity - you'll help set the bar for how an AI-native data science team operates.
Work on questions with no playbook - AI-native products are too new for established benchmarks. What engagement, retention, and user success look like for AI products that answer questions and get real work done is still an open question, and you'll help define it.
Use AI where it actually matters - you'll use frontier tools to make analysis faster, more repeatable, and more useful.
Direct impact - small team, high ownership, and work that shapes product and company direction.
New Data Scientist postings at the employers we follow are up 3% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Scientist, by the work the posting describes.
Data scientists use statistics and models to answer harder questions, such as whether a change worked, what demand will look like next quarter, or which customers are likely to leave.
Postings usually ask for Python or R, SQL, statistics, experiment design and common machine learning methods.
Unlike an ML engineer, a data scientist's main output is often an analysis or a first model, not software running inside a product.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-2051.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
San Francisco, California, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.