Back to jobs

Senior Data Engineer

Pay
Pay not listed
Work setting
Remote — work setting source
Work setup in the employer’s posting: Remote
From the employer’s posting
Employment
Not stated

What you’ll work on

Full posting
  • Work on Kafka ingestion pipelines covering topics, partitions, consumers and schema evolution

  • Design and optimize transformations across SQL, NoSQL and graph databases

  • Implement data quality checks and schema handling across pipelines

  • Monitor ingestion performance, throughput, and reliability

From the employer’s posting
Work on Kafka ingestion pipelines — topics, partitions, consumer logic, schema evolution.
Design and optimize transformations across SQL, NoSQL, and graph database ecosystems.
Implement data quality checks, schema handling, and consistency across pipelines.
Monitor ingestion performance, throughput, and reliability.

What you’ll bring

All qualifications

Core experience

  • 4–9 years of experience
  • Strong Python for ETL, utilities and data processing
  • Mandatory Spark experience with batch transformations and performance tuning
  • Strong SQL, including query optimization and data modeling
  • Kafka basics: producers, consumers, offsets, schema handling
Qualification wording
Experience: 4–9 years
Strong Python — ETL, utilities, data processing.
Mandatory Spark experience — batch transformations, performance tuning.
Strong SQL — query optimization and data modeling fundamentals.
Kafka basics — producers, consumers, offsets, schema handling.

Tools in this posting

  • Python
  • SQL
  • Kafka
  • NoSQL
  • Spark
  • Terraform
Source — Tool mentions in context
Senior Data Engineer – Data Ingestion & Pipelines Location: India (Bangalore) Experience: 4–9 years About the Role We are looking for a Senior Data Engineer who is deeply comfortable working with data — building ingestion pipelines, writing efficient transformations, exploring different database technologies, and ensuring reliable data movement across the organization. You will primarily work on our Kafka ingestion flow, distributed data systems, and multiple storage layers (SQL, NoSQL, and graph databases). The ideal candidate enjoys working with raw data, optimizing queries, and building stable pipelines using Python and Spark. This role is perfect for someone who is data-heavy, curious about the data world. Key Responsibilities Data Engineering (Primary Focus) ● Build and maintain robust ETL/ELT workflows using Python and Apache Spark. ● Design and optimize transformations across SQL, NoSQL, and graph database ecosystems. ● Implement data quality checks, schema handling, and consistency across pipelines. ● Deal with complex, high-volume datasets and real-world production data. Streaming & Ingestion ● Work on Kafka ingestion pipelines — topics, partitions, consumer logic, schema evolution. ● Monitor ingestion performance, throughput, and reliability. ● Build connectors/utilities for integrating various sources and sinks. Querying & Multi-Database Work ● Write and optimize complex queries across relational and NoSQL systems. ● Exposure to graph databases and graph query languages (e.g., Cypher, Gremlin). ● Understand indexing, modeling, and access patterns across different DB types. Python & DevOps Awareness ● Write clean and modular Python code for ETL jobs and data utilities. ● Basic understanding of CI/CD, job orchestration, logging, and monitoring. ● Ability to debug production ETL issues end-to-end. Required Skills ● Strong Python — ETL, utilities, data processing. ● Strong SQL — query optimization and data modeling fundamentals. ● Mandatory Spark experience — batch transformations, performance tuning. ● Kafka basics — producers, consumers, offsets, schema handling. ● Hands-on experience with relational and NoSQL databases. ● Exposure to graph databases and graph query languages. ● Strong debugging and data exploration skills. Nice-To-Have ● Retail or e-commerce domain experience. ● Familiarity with Terraform or basic infra automation. ● Experience with nested JSON, denormalized structures, and semi-structured data. ● Understanding of distributed storage concepts. Soft Skills ● High ownership and end-to-end problem solving. ● Enjoys working with complex or messy data. ● Curious mindset — comfortable exploring new databases and data flows. ● Clear communication and ability to collaborate with backend and product teams.
Check the employer’s page ↗

Posting record

Report an error

Open 5 monthsWe first saw this posting 170 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.

Status in our records
Live
First seen by us
Jun 4, 2026170 days ago
Recorded sightings
90
Last seen by us
Nov 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 170

Up longer than most. Similar jobs usually come down between day 6 and day 56.

From 14,771 similar postings that came down. Coming down is not always a hire.

Your next step

Check the employer’s posting for the current role and application details.

Applying through BambooHR

  • No account needed. The form takes images too, but an image of a resume has no text for anyone to search: upload a PDF or Word file.

Already applied? Track this application

Job description

View original posting ↗

Senior Data Engineer – Data Ingestion & Pipelines
Location: India (Bangalore) Experience: 4–9 years
About the Role
We are looking for a Senior Data Engineer who is deeply comfortable working with data — building ingestion pipelines, writing efficient transformations, exploring different database technologies, and ensuring reliable data movement across the organization.
You will primarily work on our Kafka ingestion flow, distributed data systems, and multiple storage layers (SQL, NoSQL, and graph databases). The ideal candidate enjoys working with raw data, optimizing queries, and building stable pipelines using Python and Spark.
This role is perfect for someone who is data-heavy, curious about the data world.
Key Responsibilities
Data Engineering (Primary Focus)
● Build and maintain robust ETL/ELT workflows using Python and Apache Spark.
● Design and optimize transformations across SQL, NoSQL, and graph database ecosystems.
● Implement data quality checks, schema handling, and consistency across pipelines.
● Deal with complex, high-volume datasets and real-world production data.
Streaming & Ingestion
● Work on Kafka ingestion pipelines — topics, partitions, consumer logic, schema evolution.
● Monitor ingestion performance, throughput, and reliability.
● Build connectors/utilities for integrating various sources and sinks.
Querying & Multi-Database Work
● Write and optimize complex queries across relational and NoSQL systems.
● Exposure to graph databases and graph query languages (e.g., Cypher, Gremlin).
● Understand indexing, modeling, and access patterns across different DB types.
Python & DevOps Awareness
● Write clean and modular Python code for ETL jobs and data utilities.
● Basic understanding of CI/CD, job orchestration, logging, and monitoring.
● Ability to debug production ETL issues end-to-end.
Required Skills
● Strong Python — ETL, utilities, data processing.
● Strong SQL — query optimization and data modeling fundamentals.
● Mandatory Spark experience — batch transformations, performance tuning.
● Kafka basics — producers, consumers, offsets, schema handling.
● Hands-on experience with relational and NoSQL databases.
● Exposure to graph databases and graph query languages.
● Strong debugging and data exploration skills.
Nice-To-Have
● Retail or e-commerce domain experience.
● Familiarity with Terraform or basic infra automation.
● Experience with nested JSON, denormalized structures, and semi-structured data.
● Understanding of distributed storage concepts.
Soft Skills
● High ownership and end-to-end problem solving.
● Enjoys working with complex or messy data.
● Curious mindset — comfortable exploring new databases and data flows.
● Clear communication and ability to collaborate with backend and product teams.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Bangalore, Karnataka, India

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

AI answers unavailable

We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting