Senior Data Scientist - Applied Machine Learning Remote 3-6+ Months Hands-on senior technical resource on a two-person... ...Classification / probability-based modeling Feature engineering and feature selection Feature i…
Engineering & IT · St. Louis, MO
Data Engineer jobs in St. Louis, MO
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.
88
Open roles today
$35–$86/hr
Typical pay range
$119k
Median, full-time
8
Fresh in this list
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.
01
Open data engineer roles
12 shown of 88 · sorted by freshness
$123k - $163k
services concepts and terminology, particularly in wealth management ~ Proficient in T-SQL, relational databases, and foundational data modeling principles ~ Ability to write SQL queries that aggregate, analyze, and stru…
Working Ameren Title: Senior AI Platform Engineer Day-to-day: The Senior AI Platform Engineer will support the development of the company's AI platform, working closely with the Lead AI Platform Engineer to enhance chatb…
headquartered in Ann Arbor, Michigan that offers strategic talent solutions to our clients world-wide. Job Title: IT Data Engineer Location: St Louis, MO, 63146 Duration: 12 Months Job Type: Temporary Assignment Work Typ…
Associate Backend Software Engineer, Phantom WorksCompany:The Boeing CompanyThe Boeing Company is currently seeking an Associate Backend... ...for web-applications and services. You will design APIs, create data processi…
$58 - $63 per hour
enterprise ServiceNow platform. This role will focus on platform engineering, workflow automation, release management, configuration... ...with Configuration Management Database (CMDB), Common Service Data Model (CSDM),…
Job Title: Databricks Data Engineer ( Databricks, AWS/Azure, Snowflake ) - St. Louis Primary Location: St. Louis, MO Work Model: Hybrid Security Clearance: Visa Independent (Green Card holder or US Citizen) Supplier Comm…
$180k - $208k
~7+ years of experience in designing and building intricate data processing pipelines and streaming solutions. ~ Familiarity with... ...Responsibilities: Develop, improve, and resolve complex data engineering, visualizat…
$55.4k - $113k
changing technology solutions. We are looking for Fullstack Engineers who will collaborate with clients to transform their business... ...planet, while building trust in capital markets. Enabled by data, AI and advanced…
$88.2k - $198k
Senior Full Stack Data Engineer Position Description This position must be performed on-site, hybrid in St. Louis, MO. Join a team responsible for designing and delivering cloud-based applications that support complex bu…
We are seeking a Data Scientist with strong experience in advanced analytics, statistical modeling, machine learning, and artificial... ...goals. Collaborate closely with Data Analysts, Data Engineers, Business Stakehold…
for conversational AI - Integrate with Azure OpenAI APIs with circuit breaker patterns and fallback chains - Implement prompt engineering and dynamic prompt management (DB-backed with in-memory caching) - Design and impl…
02
What data engineers earn in St. Louis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$48 | $72k–$99k |
| Mid level | $48–$66 | $99k–$138k |
| Senior | $64–$86 | $133k–$179k |
Adjusted for the St. Louis market from national ranges.
03
What employers ask for
The skills these listings keep naming
SQL and data modelingPython or ScalaAirflow or similar orchestrationSpark or other batch processingWarehouses (Snowflake, BigQuery)dbtStreaming (Kafka)Data quality testingCloud infrastructure
04
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.
05
Resume tips that move the needle
For data engineers specifically — generic advice costs you here
01
State data scale plainly — rows per day, terabytes managed, pipeline counts — because it is the first thing hiring managers scan for.
02
Name your orchestration, processing, and warehouse tools per role; the modern stack (Airflow, dbt, Snowflake) is a keyword screen.
03
Highlight reliability outcomes: pipeline failure rates, data freshness SLAs met, incident reductions.
04
Show cost work if you have it — warehouse spend is a live concern and optimization stories differentiate.
05
Mention who consumed your data (analysts, ML teams, executives) to show you build for users, not just movement.
06
Where this role goes
Typical progression
01
Junior Data Engineer
02
Data Engineer
03
Senior Data Engineer
04
Staff Data Engineer
05
Data Platform Lead
Ten quiet minutes a day
Applying for data engineer jobs in St. Louis?
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.