> Markdown version of [/jobs/ext/4789415-lead-data-scientist](https://www.wearedevelopers.com/jobs/ext/4789415-lead-data-scientist). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Lead Data Scientist - **Company:** FI FI DOG COIFFURE LLC - **Location:** New York, NY, United States - **Experience:** Expert - **Salary:** $140,000 - $225,000 - **Contract:** Permanent contract - **Skills:** Geographic Information Systems, Artificial Intelligence, Data Analysis, Information Engineering, Global Positioning Systems (GPS), Mobile Application Software, Python (Programming Language), SQL Databases, Time Tracking Software, Apache Spark, Claude, Databricks - **Published:** November 19, 2026 - **Apply:** https://www.careerbuilder.com/job-details/lead-data-scientist-new-york-ny--90f8b27e-011a-4d43-96ce-0daeb1333b97 ## About the Role Data Science, Leading Edge Technology, Time Tracking, Team Player, Data Science, Mobile Applications, eCommerce, GPS (Global Positioning System), Prototyping, Product Engineering, * 8+ years in data science, including meaningful time at a DTC subscription business * Experience working with ML engineers to take a model from idea to production, and to evaluate it once it's live * Strong Python and SQL, and comfort with Spark/Databricks at scale * Statistical rigor: experiment design, causal reasoning, and knowing when a result is noise * Fluency with AI tools like Claude, and the judgment to check what they produce * A track record of projects you started yourself that shipped * Clear writing, and the confidence to defend a conclusion * Preferred: experience with sensor, wearable or location data ## Description * Partner with the ML team on behavior and health detection: define the signals, test models against what dogs actually did, and measure how they perform once they ship * Know the raw collar data (GPS, accelerometer, activity, sleep) well enough to spot when something is wrong before a customer does * Start your own projects from the data and see them through: evidence, prototypes and proposals that product and engineering pick up * Define what success looks like before a feature launches, and read the results honestly after * Build predictive models, such as likelihood to churn, that power both customer-facing features and internal decisions * Work with Analytics Engineering and Data Engineering so your best analyses become governed tables and metrics, not one-off notebooks * Bring a point of view, and tell leadership what the data says even when it isn't what they expected