Sr. Data Scientist
Pendo · Raleigh, NC
$133,000–$160,000from the description
Jul 23, 2026
Raleigh, NC
Jul 25, 2026
What this job asks for AI summary
A senior individual-contributor role on an internal GTM intelligence team, responsible for the end-to-end lifecycle of data science work — from scoping business problems with Sales, Marketing, and Customer Success stakeholders through building ML and predictive models, communicating findings, and driving adoption. The position suits someone with hands-on modeling and SQL experience who is comfortable working closely with revenue-focused teams and translating analytical outputs into concrete business decisions.
Mid level · 2+ years · Raleigh-Cary, NC · Full-time
Advertised as Senior, but the requirements read as Mid.
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 310 people in the Raleigh-Cary, NC area plausibly meet what this posting asks for (data scientists). range 230–400
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $123,364 (middle half $87,094–$148,700). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The title says 'Senior' but the experience requirement is only 2–4 years, which aligns with a Mid-level role on a standard career ladder. Seniority is assessed as Mid accordingly.
Python and SQL are listed together in the Must-haves section as 'statistical computer languages (Python, SQL)' — both are hard gates. They are emitted as separate skills rather than alternatives because the JD presents them as a combined requirement.
The degree requirement states 'Bachelor's or master's education in a STEM field' but does not explicitly exclude equivalent experience, and the phrasing is aspirational rather than a strict gate — treated as None.
LLM-based tooling, prompt engineering, and agentic AI workflows appear under 'Nice-to-haves'. Cursor and Claude Code are mentioned in the day-to-day narrative as tools the team uses, not as candidate gates.
BI tools (Omni, Looker, Tableau) appear under 'Nice-to-haves' for self-serve analytics delivery. Looker is emitted as the primary with Omni and Tableau as alternatives; Tableau is also emitted separately since it is a distinct, widely-known tool.
Experience with recurring revenue / B2B SaaS and GTM function exposure are listed as preferred/nice-to-have contextual experience rather than named technologies — not emitted as skills per extraction rules.
The alt SOC (15-2031 Operations Research Analysts) is noted because the role has a significant analytics and business-intelligence dimension alongside the ML/modeling work, though the ML emphasis makes 15-2051 the clear primary.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): predictive modeling.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.