work that truly matters for patients, we invite you to join us. Job Description Purpose: The Associate Director, RWD Data Engineering is a hands-on technical role that builds and delivers the engineering vision for Lilly…
Data Engineer jobs in Indianapolis, IN
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
12 shown of 140 · sorted by freshness
opportunities! At Xenon7, we work with leading enterprise clients and innovative startups on high-impact projects across Data, AI, Cloud, and Software Engineering. Our expertise in AI solution architecture and specialize…
being redefined by AI. About the Role You own LILTs data transformation layer: the dbt layer and warehouse behind every... ...you make it a role. You lead a new Data sub-team in Platform Engineering reporting to the head…
employee to be extraordinary. We are currently looking for Software Engineer Interns who want to make an impact. As a Database Engineer... ...and traditional architecture skills to deliver critical data analysis and arch…
Validation Engineer AI & Data Location: Indianapolis IN Summary: Validate the accuracy reliability completeness and consistency of business context and AI generated responses against approved business requirements and gr…
Data & AI Engineer Location: Indianapolis, IN Summary: Develop and integrate the technical components that capture, store, process, and deliver business context to the client’s existing AI ecosystem. Responsibilities: De…
purpose and ready to bring your best to work that truly matters for patients, we invite you to join us. NLP & Market Research Data Engineering Lead Customer Insights and Analytics (CIA) At Lilly, we unite caring with dis…
As MISO's Senior Data Scientist on the Emerging Technology team, you will bring deep data science expertise to rapid prototyping and... ...complex operational and market data through feature engineering, model developmen…
ready to bring your best to work that truly matters for patients, we invite you to join us. We are seeking a highly motivated Data Engineer for our LillyDirect Pharmacy Covered Entity (LDPCE) Master Data team. This role…
respects the remarkable individuality of everyone's culture, history, and service. Description We are seeking a Senior Cloud Data Engineer to join our consulting team. In this role, you will design, build, and maintain s…
Developer-Information Services III - Data Engineer Our teams shape strategic initiatives, have passion, and work to improve health outcomes. They advance our mission and exemplify excellence, compassion, teamwork, and pu…
responsible for building, optimizing, and managing large-scale data pipelines and solutions that power critical business insights and... ...Bachelors degree in information systems, Computer Science, Engineering or equiva…
What data engineers earn in Indianapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$48 | $73k–$100k |
| Mid level | $48–$67 | $100k–$140k |
| Senior | $65–$87 | $135k–$181k |
Adjusted for the Indianapolis 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 Indianapolis?
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.