Tracking 100,000+ career sites
Senior Data Engineer Jobs
Built from a 20M+ job database and updated hourly, this list surfaces senior data engineer roles across pipelines, warehousing, architecture, orchestration, and cloud data platforms.
Openings may be titled senior or lead data engineer, analytics engineer, data platform engineer, data architect, streaming engineer, or data engineering manager. Work can include designing batch and real-time pipelines, modeling warehouse or lakehouse data, operating orchestration systems, improving lineage and data quality, governing access, and building platforms used by analysts, scientists, product teams, or external customers. In a product team, engineers may own event collection and operational data services; centralized platform groups often emphasize reusable infrastructure and standards; regulated employers may add privacy, retention, and audit controls. Judge seniority by architectural authority, production accountability, scale and criticality of datasets, influence on upstream and downstream teams, and responsibility for mentoring or management. A staff-level platform specialist and a people manager may have similar titles but very different hiring signals and daily work.
Create a small comparison matrix for platform users, data latency, architecture ownership, and operational support. Those fields expose major differences between an analytics-engineering role, a domain pipeline team, and a shared data platform. Add the cloud, warehouse or lakehouse, orchestration, streaming, transformation, and programming stack from the original posting, along with governance and on-call duties. Also record whether the team owns source ingestion, semantic models, serving layers, or the full path. A stated assessment may cover SQL, coding, modeling, distributed systems, or pipeline design; prepare only after checking the described process. Employer, location, compensation, and sponsorship filters handle practical constraints. Weigh disclosed pay and equity against platform maturity, incident burden, team structure, and architecture authority, and confirm all current requirements at the source.
Browse and filter the data-engineering inventory for free. With an optional free account, save the strongest matches, record application stages, and use Copilot where helpful. Keep platform and ownership notes tied to each application.





- today
ShiftSenior Data Engineer - Terraform skillsParis, FranceNot listedtoday - today
EltropyLead Data EngineerRemote in IndiaNot listedtoday - today
Lab37 RoboticsCloud Platform Data Engineer$130k - $164.5kPittsburgh, PA$130k - $164.5ktoday - today
PayPay IndiaData EngineerGurugram, IndiaNot listedtoday - today
AtomsCloud Platform Data Engineer$130k - $164.5kPittsburgh, PA$130k - $164.5ktoday - today
Ford Motor CompanyFull Stack Data EngineerChennai, IndiaNot listedtoday - today
iCIMSPrincipal Data EngineerHyderabad, IndiaNot listedtoday - today
DigibleSenior Analytics Engineer$140k - $160kRemote in USA$140k - $160ktoday - today
YipitDataSenior Data Engineer - Global TeamRemote in IndiaNot listedtoday - today
MillSenior Data Engineer - Data Recommendations$185k - $210kSan Bruno, CA$185k - $210ktoday - today
AAreteSenior Data Engineer - Payment Intelligence - Data Architecture & EngineeringPune, IndiaNot listedtoday - today
Nissan GlobalLead Data Engineer - Data Governance & ComplianceThiruvananthapuram, IndiaNot listedtoday - today
LexisNexis Risk SolutionsConsulting Data Engineer$104.9k - $174.7kRaleigh, NC$104.9k - $174.7ktoday - today
LexisNexis Risk SolutionsContent Data Engineering Manager$109.5k - $230.7kRemote in USA$109.5k - $230.7ktoday - today
Marsh & McLennanDirector Enterprise Data Engineering & Analytics$139k - $277.9kNew York, NY$139k - $277.9ktoday - today
General MotorsSenior Robotics Data Engineer/Data Scientist - Manufacturing Data Organization$125k - $168.7kAustin, TX$125k - $168.7ktoday - today
General MotorsSenior Data Engineer$133k - $188.6kAustin, TX$133k - $188.6ktoday - today
Marsh & McLennanData and Analytics Engineering Lead - Reinsurance$139k - $277.9kPrinceton, NJ$139k - $277.9ktoday - today
SteampunkEnterprise Data Architect$135k - $165kMcLean, VA$135k - $165ktoday - yesterday
Boston ScientificSenior Data Engineer - Data Science & Business Intelligence$85k - $161.5kArden Hills, MN$85k - $161.5kyesterday - yesterday
Northrop GrummanPrincipal Data Engineer - Program and CoTE Analytics$98.4k - $184.2kMelbourne, FL$98.4k - $184.2kyesterday - yesterday
NovartisAssociate Director Data Engineering Lead$152.6k - $283.4kEast Hanover, NJ$152.6k - $283.4kyesterday - yesterday
HumanaLead Cyber Threat Intelligence Data Architect$129.3k - $177.8kBoston, MA$129.3k - $177.8kyesterday - yesterday
Zone 5 TechnologiesData Engineer - AI/ML III/IV$130k - $187kUnited States$130k - $187kyesterday
Explore More
Related Job Lists
Curated lists closely related to this one — similar roles, industries, and locations.
Senior Data Scientist Jobs
This list tracks 100K+ company job sources and updates hourly with senior data scientist roles across modeling, experimentation, forecasting, product analytics, decision science, and machine learning. Openings range from senior and lead data scientists to principal data scientists, decision scientists, applied scientists, analytics directors, and data science managers. Work spans product measurement, pricing, risk, growth, operations, healthcare, finance, and other data-driven areas. The list helps separate experimentation and product-analytics positions from applied machine learning, forecasting, decision science, and data-science leadership. The clearest evidence of level usually appears in the responsibilities rather than the heading. Review the complexity of the work, autonomy, stakeholder seniority, team or program scale, and accountability for results. Then compare those expectations with the stated experience and credentials. This approach can reveal when a lead or principal opening remains hands-on, when a manager role carries substantial execution, and when a senior title implies broader organizational leadership. Use these distinctions to tailor your resume toward the leadership examples, domain decisions, and measurable outcomes most relevant to each opening. Filter by company, location, industry, compensation, or sponsorship requirement. Review the original posting for required experience, degree expectations, technical tools, management responsibilities, and whether the role emphasizes statistical analysis, machine learning, or team leadership. Run a broad search once to learn the market's vocabulary, then refine it with the terms that recur in genuinely relevant postings. Use employer and location filters for practical constraints, and check compensation or sponsorship fields where available. Before applying, return to the source listing to confirm that availability and requirements have not changed and that the role still matches your intended work. A consistent comparison note for scope, requirements, workplace, timing, and next action makes repeated reviews faster and less subjective. Browsing and filtering are free. With a free Simplify account, you can save relevant roles, track applications in one place, and use Copilot autofill when you choose to apply. Use notes for verified details that are not visible in the summary card.
Senior AI and Machine Learning Jobs
This list is updated hourly from a 20M+ job database and surfaces senior AI and machine learning roles across applied AI, ML engineering, generative AI, research, and production models. Roles include senior, staff, or principal machine learning engineer, AI engineer, applied scientist, research scientist, ML platform engineer, AI architect, and engineering or research manager. Work may center on large language models, computer vision, natural language processing, recommendations, forecasting, model evaluation, inference systems, data and training infrastructure, or responsible-AI controls. A research lab may prioritize novel methods and publications, a product team may emphasize evaluation and user impact, and an ML platform group may own reliability, cost, deployment, and tools for other engineers. Seniority depends on technical originality, production or research ownership, the scale and risk of decisions, cross-team direction, and mentoring or management. Distinguish roles that train models from those integrating model APIs, and distinguish principal technical leadership from responsibility for hiring and team performance. Place each role on a research-to-production spectrum before comparing its tool list. Confirm how much work involves model development, evaluation, software engineering, data or training infrastructure, deployment, and ongoing operations. Ask who defines evaluation criteria, owns model behavior after release, and decides when a system is ready for use. The original posting should also clarify model families and frameworks, cloud stack, publication or advanced-degree expectations, safety responsibilities, and on-call terms. A stated selection process may involve coding, ML system design, statistics, a research presentation, or evaluation work; use the description to prioritize preparation. Company, location, compensation, and sponsorship filters handle practical constraints. Weigh disclosed compensation and equity against company stage, compute and data resources, research freedom, technical scope, and management expectations. Browsing does not require an account. A free account adds saved AI and machine-learning roles, application tracking, and Copilot. Keep the research-to-production balance in your notes and recheck the source before applying.
Senior DevOps and Infrastructure Jobs
This list is updated hourly from 100K+ company job sources and surfaces senior DevOps and infrastructure roles across CI/CD, SRE, platform engineering, systems, networks, databases, and observability. Openings may be labeled senior DevOps engineer, site reliability engineer, platform engineer, infrastructure engineer, systems or network engineer, database administrator, production engineer, or infrastructure lead. Responsibilities can include deployment automation, internal developer platforms, Kubernetes operations, network and database reliability, monitoring, capacity planning, incident response, and modernization of core systems. The balance between software development, platform enablement, and direct operations varies by team and should be clear in the source description. Some postings measure the role through developer adoption and delivery speed; others focus on availability, recovery, capacity, or safe change. Seniority is reflected in production ownership, architectural judgment, incident command, automation depth, and the ability to reduce recurring operational work. Staff and principal roles may set technical direction without direct reports; managers and operations leaders can add staffing, service-level, and escalation responsibilities. Production responsibility is the most useful starting point. Determine whether the engineer owns services, a shared platform, networks, databases, or an operating process, and how much of the work is software development versus administration. Then verify the cloud and operating environment, coding and infrastructure-as-code tools, container stack, observability systems, security or clearance needs, on-call rotation, and role during high-severity incidents. Look for evidence of who sets service objectives, approves risky changes, and follows remediation work after an incident. A disclosed interview plan may call for coding, systems design, troubleshooting, or incident examples; tailor preparation to the ownership described. Compare pay with call frequency, remote-access limits, and platform maturity. Company, location, compensation, and sponsorship filters refine the list, while the original posting controls authorization and workplace requirements. The list remains free to browse and filter. An optional free account keeps saved infrastructure roles and application progress together and offers Copilot for selected forms. Revisit any saved posting before applying.
Explore our FAQ section to learn more.
Recognizable employers to research include Amazon, Google, Microsoft, Meta, Snowflake, Databricks, JPMorgan Chase, Capital One, and Walmart. Technology companies need engineers for product analytics and platform data, while banks and retailers operate large internal systems for transactions, risk, supply chains, and customer reporting. Consulting firms also hire experienced data engineers for client migrations and platform projects. Treat these names as research starting points, not proof of a current opening. Search each employer's careers site for data engineer, analytics engineer, data platform, and data architect titles, then confirm the location, level, and work authorization terms in the posting.
A data engineer is usually ready when they can own a production system rather than complete only assigned pipeline work. That means making sound choices about schemas, orchestration, storage, access, testing, and recovery, then explaining the tradeoffs to other engineers and business partners. Senior candidates should have examples of diagnosing failures, planning migrations, improving reliability, and preventing the same incident from returning. Mentoring helps, but direct reports are not required. Job titles vary widely, so judge readiness by scope: the number of teams affected, the consequences of mistakes, and whether other people depend on the standards you set.
Describe the system, your decision, and the result. Instead of writing that you built pipelines, state what data moved, who relied on it, what scale or reliability problem existed, and which part you personally owned. Useful results include shorter processing time, fewer failed jobs, lower cloud spending, improved data freshness, faster recovery, or a migration completed without disrupting users. Include architecture choices only when you can explain why they mattered. If the work involved several teams, separate your contribution from the group's. A senior resume should show judgment under constraints, not a long inventory of databases and orchestration tools.
Expect a mix of data modeling, SQL, system design, and production troubleshooting. An interviewer may ask you to design a pipeline, choose between batch and streaming, handle late or duplicated events, control access, or recover after a partial failure. Coding rounds often use Python, Java, or another language named in the posting. The senior signal is not choosing one fashionable tool. It is identifying requirements, stating assumptions, and explaining failure modes, cost, and operational burden. Prepare two real projects in detail, including a decision you reversed, an incident you handled, and what you changed afterward to make the system safer.
Data engineers usually build and operate ingestion, storage, transformation, and serving systems. Analytics engineers work closer to analysts and business teams, shaping warehouse data into tested, documented models that people can use consistently. Data architects define broader structures, standards, and integration patterns, often across several teams or business units. The boundaries blur, especially at smaller companies where one person may do all three. Compare the deliverables in the posting: production services and orchestration point toward data engineering, warehouse models toward analytics engineering, and organization-wide design authority toward architecture. Ask who owns code, incidents, and data definitions before relying on the title.
Ask who notices bad data first, how teams declare and enforce data contracts, and what happens when a pipeline misses its deadline. Find out whether the platform has automated tests, lineage, monitoring, documented owners, and a clear process for changing shared schemas. Incident questions are revealing: ask about a recent failure, how long recovery took, and whether the team had time to remove the cause afterward. Also ask how much work is new development versus repairing old pipelines. A mature team can describe its weak spots plainly. Vague claims that quality belongs to everyone often mean nobody has the authority or time to own it.
Yes. Many organizations have an individual contributor ladder that continues through staff, principal, architect, or distinguished engineer levels. Advancement on that path comes from widening technical scope: setting platform standards, leading migrations, reviewing designs, resolving failures that cross team boundaries, and helping other engineers make better decisions. You may mentor people and lead projects without conducting performance reviews or managing headcount. Ask recruiters to show you the engineering ladder and describe the last promotion above senior level. If every example involves becoming a manager, the individual contributor path may exist only on paper. Compare authority, expectations, and compensation at equivalent technical and management levels.
Some do, particularly large technology companies, financial institutions, consultancies, and data-platform vendors with established immigration teams. Sponsorship still depends on the specific role, location, candidate, and hiring cycle. A company that has filed H-1B specialty occupation petitions before does not sponsor every opening. Candidates already working through Optional Practical Training, an existing H-1B, permanent residence, or another authorization should state their current status and future needs accurately. Read the application questions carefully and ask the recruiter when the posting is unclear. Remote roles can carry state or country restrictions as well. This is general information, not immigration advice.