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 appli…
Data Engineer jobs in Austin, TX
Data engineers build the pipelines and warehouses that move data from source systems to the people and models that need it, keeping it fresh, correct, and queryable at scale.
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 engineer roles
11 shown of 785 · sorted by freshness
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…
-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 transfer…
by human error. It allows security organizations to become 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 A…
create and nurture the experiences under the PlayStation brand a name synonymous with entertainment excellence and creativity. Data Engineer PlayStations Infrastructure Business Operations team is looking for a Data Engi…
About the role Teza's Data Platform team owns the data the firm trades on: every backtest, every live strategy, every portfolio... ...strategies This is a hands-on position on a small team of data engineers with growth p…
rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and... ...operational data coherent and extensible enough for other engineers to bring…
This is a test for all departments and teams in Austin, Texas. Conversica has a strong engineering team that is committed to our customers, passionate about technology and motivated to succeed. We are driven, self-starti…
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…
Employer: Amazon.com Services LLC Position: Data Engineer III - AMZ27926.2 Location: Austin, TX Multiple Positions Available: Design, develop, implement, test, document, and operate large-scale, high-volume, high-perform…
FDE – Vulnerability Data and Workflow Engineer Location: Austin, TX Type: Fixed Term (12 Months) [Eligible for benefits with the possibility of extension] Job Summary Deliver the workflow, data extraction, and leadership…
What data engineers earn in Austin
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $39–$54 | $82k–$113k |
| Mid level | $54–$76 | $113k–$158k |
| Senior | $73–$99 | $152k–$205k |
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
Design a pipeline that loads data from a production database into a warehouse daily.
Cover extraction strategy, incremental loads versus full refresh, idempotency, and monitoring. Saying how you would backfill after a failure shows real pipeline experience.
How do you handle late-arriving or duplicate data?
Discuss idempotent upserts, watermarks, and dedup keys. This is a daily reality of the job, so a concrete example lands well.
Batch or streaming — how do you decide?
Anchor on the actual freshness requirement and cost. Most 'real-time' asks are fine at minutes; recognizing that is the mature answer.
A stakeholder says the numbers in their dashboard are wrong. Walk me through your debugging.
Trace lineage from the dashboard back to the source, isolating which layer diverged. Showing calm, structured lineage-tracing is the point of the question.
How do you model data for analytics — star schema, wide tables, something else?
Show you know the classic patterns and modern warehouse economics, and that you choose based on query patterns and team skill, not doctrine.
How do you test data pipelines?
Talk about schema and freshness checks, row-count and distribution tests, and tools like dbt tests or Great Expectations — plus alerting when they fail.
Tell me about a pipeline that failed badly and what you changed.
Structure it like an incident review: impact, cause, fix, prevention. Emphasize the durable improvement, such as monitoring or contract enforcement.
Resume tips that move the needle
For data engineers specifically — generic advice costs you here
State data scale plainly — rows per day, terabytes managed, pipeline counts — because it is the first thing hiring managers scan for.
Name your orchestration, processing, and warehouse tools per role; the modern stack (Airflow, dbt, Snowflake) is a keyword screen.
Highlight reliability outcomes: pipeline failure rates, data freshness SLAs met, incident reductions.
Show cost work if you have it — warehouse spend is a live concern and optimization stories differentiate.
Mention who consumed your data (analysts, ML teams, executives) to show you build for users, not just movement.
Where this role goes
Typical progression
Applying for data engineer 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.