year Requirements: Strong background in Python, SQL, and core data engineering practices Hands-on experience building ETL/ELT... ..., and troubleshooting procedures Partner with Data Scientists, Analysts, Business Teams,…
Data Scientist jobs in Pittsburgh, PA
Data scientists turn raw data into decisions and products, using statistics, experimentation, and machine learning to answer questions the business could not otherwise settle.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open data scientist roles
11 shown of 904 · sorted by freshness
Skills & Experience • Strong hands-on experience with Snowflake (tables, views, performance tuning) • Advanced SQL skills and data transformation expertise • Experience building data ingestion pipelines (ETL/ELT) • Exper…
Data Engineer Position Description We are seeking a Data Engineer with 5 years of experience to design and maintain scalable data pipeline supporting analytics, reporting, and operational needs. The role involves collabo…
Data Engineer – Azure Databricks Contract-to-Hire Pittsburgh, PA – Onsite Job ID J0726-0569 Visa : USC, GC, EAD (No Sponsorship) Position Overview Seeking an experienced Data Engineer to join a high-performing data engin…
Position Title: Data Engineer Location: PA – Pittsburgh (Locals Preferred) Work Status : Onsite 5 days a week Duration : Contract to Hire Years Of Experience Required : 6+ Years Industry Background: Finance / Banking Fun…
Data Ideology At DI, we provide Data & Analytics expertise to drive measurable business outcomes, often solving complex business problems for our clients. Our data analytics advisory services enable our customers to tran…
Data Engineer - Databricks - Local to Pittsburgh, PA Position Description Join a high performing data engineering team responsible for building modern, cloud native data platforms on Microsoft Azure. This role offers the…
and executing at the speed of operational demands, the front line gets what it needs to succeed. Job Description The Lead Data Scientist will provide visionary technical leadership to a team of data scientists and AI eng…
speed of operational demands, the front line gets what it needs to succeed. Job Description We are seeking an inquisitive data scientist to join our team and work with our various datasets to find connections, knowledge,…
speed of operational demands, the front line gets what it needs to succeed. Job Description We are seeking an inquisitive Data Scientist to join our team, leveraging deep expertise in Artificial Intelligence and a keen u…
speed of operational demands, the front line gets what it needs to succeed. Job Description We are seeking an inquisitive Data Scientist to join our team, leveraging deep expertise in Artificial Intelligence and a keen u…
What data scientists earn in Pittsburgh
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $38–$51 | $78k–$107k |
| Mid level | $51–$70 | $107k–$146k |
| Senior | $68–$93 | $141k–$194k |
Adjusted for the Pittsburgh market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through a data project that changed a decision.
Structure it as question, approach, finding, action. Projects that ended in a decision — even 'we did not launch' — beat technically impressive analyses that went nowhere.
How would you design an A/B test for a new feature?
Cover the metric, randomization unit, sample size, and duration, plus a pitfall like peeking or interference. Practical rigor is what is being tested.
Your model performs well offline but poorly in production. Why might that be?
Discuss train/serve skew, data leakage, distribution shift, and feedback loops. Listing several plausible causes and how you would check each is the strong answer.
Explain p-values or confidence intervals to a non-technical stakeholder.
Use plain language and a concrete scenario, and resist overstating certainty. They are testing whether your statistics survive translation.
How do you handle missing or messy data?
First ask why it is missing — the mechanism matters more than the imputation method. Then discuss options and how the choice affects conclusions.
When would you not use machine learning for a problem?
When a rule, a query, or a simple heuristic wins on cost and interpretability. Knowing when ML is overkill signals maturity.
How do you decide which metric a team should optimize?
Talk about proxy versus true goals, gameability, and counter-metrics. A story about a metric that backfired is very effective here.
Resume tips that move the needle
For data scientists specifically — generic advice costs you here
Lead every bullet with the business result — revenue, retention, cost — and put the method second.
Specify your stack concretely: Python libraries, SQL dialects, experimentation platforms, and any production ML experience.
Distinguish shipped work from research; 'model serving 2M users' and 'notebook analysis' are different claims.
Keep one or two public projects or publications linkable, tailored to the industry you are targeting.
Name the size and kind of data you worked with — event streams, tabular, text — so teams can map you to their problems.
Where this role goes
Typical progression
Applying for data scientist jobs in Pittsburgh?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.