ABOUT WAY Way is building the AI, data, and infrastructure layer for the experience economy. As artificial intelligence automates labor and people reclaim time, the shift toward spending on experiences over things only a…
Data Scientist jobs in Austin, TX
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
9 shown of 2,607 · sorted by freshness
on your long-term career development while valuing your unique skills and experiences. **Your role and responsibilities** As a Data Engineer specializing in Data Modeling, you will design and implement data models for ap…
create and nurture the experiences under the PlayStation brand, a name synonymous with entertainment excellence and creativity. Data Engineer II, JVM Austin, TX The Data Engineering Team fuels real-time, intelligent data…
long-term career development while valuing your unique skills and experiences. **Your role and responsibilities** As a seasoned Data Engineer specializing in Data Integration, you will design and build solutions to trans…
enablers for engineering and business teams to move faster as they adopt new cloud and SaaS tooling. The product is heavily driven by data analytics as well as AI/ML. The core idea is to analyze events & logs from enterp…
About the role Teza's Data Platform team owns the data the firm trades on: every backtest, every live strategy, every portfolio decision starts with data we ingested, cleaned, stored, and served. The scale, in plain numb…
Tektend LLC is seeking a skilled and proactive BI & Analytics Engineer to bridge the gap between raw data infrastructure and executive business insights. Based in our Austin, TX office on a hybrid schedule, you will desi…
Lead & Senior Data Engineers Location: Remote United States (US work authorization required) Job Type: Multi-month engagement, likely to extend Openings: 4 positions, 2 Lead and 2 Senior Start Date: Around December 1, 20…
productionize machine learning for manufacturing and to build the data engineering that those models depend on. This person will... ...model, feature design, model evaluation, and working with data scientists to turn exp…
What data scientists earn in Austin
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $40–$56 | $84k–$116k |
| Mid level | $56–$76 | $116k–$158k |
| Senior | $73–$101 | $152k–$210k |
Adjusted for the Austin 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 Austin?
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.