₹13L – ₹25L a year estimatetypical for IT Jobs in Bangalore, 281 posts
Posted 13 days ago
Free · takes a minute · your resume fills your profile
CoreHRx never asks candidates for money. If anyone does, .
Role at a glance
You will
Design, build, and own ETL/ELT pipelines that ingest, transform, and load customer-interaction and context data at a scale of billions of…
Establish and document best practices for data modeling, warehousing, and pipeline design across the team.
Experience
3+ years
Must-have skills
Data EngineeringData ModelingETLSQL
How well do your skills match this job?
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Job description
Location: Bengaluru, India
Description Join Alexa AI - ML Engineering and help power personalized, proactive experiences for hundreds of millions of Alexa customers worldwide. As a Data Engineer II, you will design and own the large-scale data pipelines that turn raw customer-interaction signals into the context and features our personalization and proactive-agent models depend on, working side-by-side with SDEs to shape our data strategy and architecture.
You will build and operate ETL/ELT pipelines processing billions of records a day, using AWS big-data services (Glue, EMR, Kinesis, Redshift, DynamoDB) and distributed compute.
You will partner with SDEs and applied scientists to define data strategy, contracts, and feature pipelines, and to decide architecture direction together.
You will own operational health: data migrations, schema/platform updates, and triage of pipeline tickets, directly supporting the SDE team's work.
This is a high-visibility role: the data you deliver, and keep running, directly shapes what Alexa proactively tells customers, and when.
Key job responsibilities
Partner closely with SDEs to help define data strategy, architecture direction, and the long-term roadmap for the team's data platform.
Design, build, and own ETL/ELT pipelines that ingest, transform, and load customer-interaction and context data at a scale of billions of records per day.
Own operational items end-to-end: data migrations, schema and platform updates, and triage/resolution of data-pipeline tickets, providing day-to-day support to the SDE team.
Partner with applied scientists and ML engineers to define data contracts, feature pipelines, and data-quality checks feeding personalization and proactive-agent models.
Operate and continuously improve production pipelines: optimize data delivery, redesign for scalability, manage deployments, and drive root-cause fixes for pipeline incidents.
Establish and document best practices for data modeling, warehousing, and pipeline design across the team.
A day in the life You'll join SDEs in a design discussion to shape data strategy and architecture, then pick up a migration or platform-update ticket and see it through to resolution. You'll trace a data-quality issue in a personalization feature pipeline, support SDEs with any operational asks on your pipelines, and monitor the health of systems processing billions of daily customer-interaction events. You'll partner with applied scientists to onboard new signal sources and triage pipeline alerts. About the team Alexa AI - ML Engineering builds the personalization and proactive-intelligence systems that let Alexa anticipate what customers need before they ask. Data Engineers work side-by-side with SDEs and applied scientists, combining data strategy and large-scale engineering to turn billions of daily customer-interaction signals into the context, features, and content that drive Alexa's ranking, personalization, and proactive-agent experiences. We value ownership, data quality, and working backwards from the customer. Basic Qualifications
3+ years of data engineering experience
4+ years of SQL experience
Experience with data modeling, warehousing and building ETL pipelines
Preferred Qualifications
Experience with AWS technologies like Redshift, S3, AWS Glue, EMR, Kinesis, FireHose, Lambda, and IAM roles and permissions
Experience with non-relational databases / data stores (object storage, document or key-value stores, graph databases, column-family databases)
Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner.
Most IT Jobs posts in Bangalore ask for 3–6 years of experience (41% of 5429 that say).
Hiring most for IT Jobs in Bangalore
Bosch Group207 open jobs
Eurofins123 open jobs
Brillio117 open jobs
Jobs asking for Data Engineering in Bangalore also ask for
Python64%
SQL59%
AWS39%
Microsoft Azure38%
ETL37%
From live job posts on CoreHRx, updated 21 Nov 2026. Skill figures count posts that list their skills; salary figures only posts that show a salary.
Questions about this job
What is the salary for this Data Engineer II, Alexa AI - ML Engineering job?
The post does not state the pay. As an estimate, comparable posts on CoreHRx advertise ₹13L – ₹25L a year (typical for IT Jobs in Bangalore, 281 posts).
This guide is for Indian job seekers preparing for SQL rounds in data analyst, data engineer, backend developer and database roles, from freshers to experienced professionals. It has 60 questions in three levels: easy covers joins, grouping and NULLs; medium covers window functions, CTEs, indexes and isolation levels; hard covers locking, MVCC, query tuning and classic puzzles such as login streaks and medians. Answers use ANSI SQL, with MySQL 8 and PostgreSQL notes where the two differ. Write each query against your own sample tables first, then compare your result with the sample answer.
Questions you may be asked
What is the difference between WHERE and HAVING?
What is the difference between DELETE, TRUNCATE and DROP?
What is the difference between an INNER JOIN and a LEFT JOIN?
What is the difference between a primary key and a unique key?