Data Scientist, Developer Productivity

About this role

<div class="content-intro"><h2><strong>About Anthropic</strong></h2> <p>Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems.</p></div><h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="3:1-3:18;42-59">About the role</h2> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="5:1-5:539;61-599">You'll partner with Developer Productivity engineering leadership to define what "developer productivity" means in an AI-first org and to set the strategy for how Anthropic measures, understands, and improves it. This is a space where the playbook doesn't exist yet: AI-assisted development is reshaping how engineers work faster than anyone can measure, and last quarter's answer is already suspect. You'll decide which questions are worth asking, build the evidence to answer them, and stay ready to revise when the ground shifts again.</p> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="7:1-7:427;601-1027">You'll own the data strategy end-to-end: which metrics earn the org's trust, which investments to push for, which assumptions to challenge — including your own. The space rewards people who hold conclusions loosely, instrument early, and update fast when the data disagrees with the narrative. This role sits at the intersection of data science, developer experience, and frontier AI, with Anthropic's own teams as your users.</p> <h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="9:1-9:24;1029-1052">Key responsibilities</h2> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" data-sourcepos="11:1-17:175;1054-2249"> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="11:1-11:170;1054-1223">Lead ambiguous, high-stakes investigations where the question isn't yet well-formed — from "is Claude making engineers faster?" to "what does 'faster' even mean here?"</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="12:1-12:189;1224-1412">Treat findings as provisional in a space that changes month to month. Bias toward instrumenting first, collecting evidence broadly, and revising the team's priors as the picture sharpens</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="13:1-13:156;1413-1568">Partner with Developer Productivity engineering leadership to set the team's measurement and research agenda — what to study, what to build, what to stop</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="14:1-14:170;1569-1738">Define the metrics framework for developer productivity in an AI-augmented org, and drive its adoption as the basis for tooling and infrastructure investment decisions</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="15:1-15:139;1739-1877">Design and run experiments on internal tooling and workflow changes; build the causal evidence base for what actually moves productivity</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="16:1-16:197;1878-2074">Influence engineering, infrastructure, and product leadership with data. Push back when the data doesn't support the prevailing narrative, and say so plainly when it doesn't support yours either</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="17:1-17:175;2075-2249">Build the analytical foundations (pipelines, dashboards, models) yourself or through partners — staying hands-on and close to the work rather than directing from a distance</li> </ul> <h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="19:1-19:26;2251-2276">Minimum qualifications</h2> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" data-sourcepos="21:1-26:142;2278-3216"> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="21:1-21:136;2278-2413">Experience writing production-quality SQL and Python (or a similar language) to build pipelines, dashboards, and models independently</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="22:1-22:141;2414-2554">Experience serving as the primary data or analytics voice in a space where the questions weren't yet well-defined, and helping define them</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="23:1-23:190;2555-2744">A track record of holding conclusions loosely — favoring instrumentation and evidence-gathering over defending a prior position, and revising views in public when the evidence warrants it</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="24:1-24:166;2745-2910">Experience shaping what an engineering or product team worked on, not only measuring what they shipped — being consulted before a decision was made, not just after</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="25:1-25:164;2911-3074">Genuine interest in how AI is changing the way software gets built, with some firsthand experience grappling with the harder, less-defined parts of that question</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="26:1-26:142;3075-3216">Comfort presenting data-backed conclusions to a room of engineers, including when that means saying a built feature isn't moving the needle</li> </ul> <h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="28:1-28:28;3218-3245">Preferred qualifications</h2> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" data-sourcepos="30:1-34:119;3247-3821"> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="30:1-30:109;3247-3355">8+ years of hands-on data science experience, ideally in infrastructure, performance, or platform contexts</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="31:1-31:105;3356-3460">Direct experience with developer productivity, developer experience, or internal tooling, at any scale</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="32:1-32:126;3461-3586">Experience measuring the adoption or impact of AI-assisted workflows, or other tooling where the ground truth was contested</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="33:1-33:116;3587-3702">A track record of building an experimentation or causal-inference practice in an org that didn't already have one</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="34:1-34:119;3703-3821">Prior staff-level or tech-lead scope: setting direction for other ICs and owning a domain's data strategy end to end</li> </ul> <p><strong>Deadline to apply:</strong> None. Applications are reviewed on a rolling basis.</p><div class="content-pay-transparency"><div class="pay-input"><div class="description"><p>The annual compensation range for this role is listed below.&nbsp;</p> <p>For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role.</p></div><div class="title">Annual Salary: