The AWS Analytics Engineering (AAE) organization is the analytics backbone of AWS — we build and operate the data platform that powers business decisions across more than 150 AWS services.
Every insight surfaced to AWS product leadership, from service adoption trends to revenue drivers, flows through systems our team designs, builds, and maintains.
We operate at massive scale — processing petabytes of data daily through thousands of jobs consisting of transformations, reporting queries, ingestions, and infrastructure management scripts.
Our engineers work directly with source systems to procure data, convert it into structured formats, build large-scale processing pipelines, design analytical data models, and maintain infrastructure with the highest security and compliance standards.
We are seeking a Senior Data Engineer to join our team.
This individual will own 3-5 data domains end-to-end, operate hundreds of pipelines, and drive architectural improvements that impact how AWS leadership makes decisions.
You will partner with service teams across AWS to design data contracts, build ingestion flows, and deliver analytical models that serve the entire organization.
The ideal candidate is a technical leader who thrives in ambiguity, takes a long-term architectural view, and consistently delivers exemplary solutions.
You are an expert with SQL, ETL, and data processing, with experience leveraging cloud-based data services such as AWS EMR, Glue, Redshift, and Lambda.
The candidate should have hands-on experience with
AI/ML technologies, including LLMs, and a strong understanding of designing and building Agentic Frameworks — including autonomous agents, multi-agent orchestration, and tool integration.
You are comfortable with ambiguity in a fast-paced environment, able to think big while paying careful attention to detail, and passionate about building data platforms using AI to accelerate the next generation of analytics at AWS scale.
Key job responsibilities
Identify limitations and opportunities in data processing tools, drive improvements and innovation, define data processing guidelines, and ensure best practices in all pipelines designed and reviewed.
For example: redesigning ingestion frameworks to handle new AWS service telemetry data, or building reusable transformation patterns adopted across multiple teams.
Define and own data architecture at the team level — ensuring architecture effectively matches business problems and data challenges with security, scalability, and cost effectiveness.
Show good judgment making technical trade-offs between short-term technology needs and long-term business needs.
Produce exemplary code — solutions that are easily usable by customers, inventive, secure, easily maintainable, appropriately scalable, and extensible.
Build solutions that are easy for others to contribute to.
Work to simplify, optimize, and remove bottlenecks.
Define and own infrastructure architecture at the team level.
Anticipate data management and access patterns, evolve the technology stack to remove bottlenecks, and deliver systems that are secure, scalable, and long lasting.
Define team-level guidelines and best practices for infrastructure management and automation.
Solve complex ambiguous problems — for example, designing cross-domain data models that unify billing, usage, and service telemetry data, or combining multiple datasets to solve problems that couldn't be solved before.
Spot areas that might lead to customer confusion, data misinterpretation, or gaps in data contracts.
Effectively split project work into parallel tasks that can be performed by themselves and others and reassembled successfully.
Drive to completion projects with dependencies on peers or other teams.
Influence related teams' data architecture and software design.
Provide technical assessments for promotions.
Actively mentor and develop others.
Build consensus when confronted with discordant views.
Drive data engineering best practices — Data Discovery, Naming Conventions, Operational Excellence, Data Security.
Ensure team's data is auditable, available, and accessible.
Proactively fix data architecture deficiencies and propose larger projects which may require the work of other teams.
Drive improvements through code review, design discussions, team planning, and operational reviews.
Participate in on-call rotation and own operational health of data systems — establish monitoring, alarming, runbooks, and SLA tracking.
Drive continuous improvement in reliability and incident response.