Back to jobs

Senior Software Engineer - Data Infrastructure

Bengaluru · Bengaluru, Karnataka, India

Actively hiring, first seen by us 10 days ago
Pay
Pay not listed
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering — team source
Department: Engineering
From the employer’s posting

What you’ll work on

Full posting
  • Build and run the ingestion service, Kafka, and pipes that land events in ClickHouse within seconds

  • Design ClickHouse Cloud tables, compute, quotas and per-tenant isolation

  • Build dbt models and Airflow DAGs, CDC and re-runnable backfill jobs

  • Run the platform in production with Terraform, Helm, monitoring, on-call and RCAs

  • Build a self-serve dataset registry and provisioning and permissions as code

From the employer’s posting
Build and run the ingestion path: the service every product sends events to, Kafka behind it, and the pipes that land data in ClickHouse within seconds.
Design tables for the read path (sorting keys, partitions, materialized views, TTL), separate compute per workload, set per-user limits and per-tenant isolation
dbt models and Airflow DAGs with the BI engineers, CDC from product databases, sync and backfill jobs that are safe to re-run
be on call; handle incidents end to end, write the RCA and fix the root cause
Make the platform self-serve: a registry of every dataset with its owner, schema, freshness and access; provisioning and permissions as code.
Apply at Sarvam

Posting record

Report an error

Actively hiringFirst seen by us 10 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 11, 202610 days ago
Recorded sightings
11
Last seen by us
Nov 21, 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 10

Similar jobs usually come down between day 6 and day 56.

At Sarvam, jobs usually come down by about day 70.

From 14,766 similar postings that came down, and 8 of Sarvam’s. Coming down is not always a hire.

Sarvam is hiring

5 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Takes jobs down at a usual pace
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • AWS
  • BigQuery
  • ClickHouse
  • dbt
  • Kafka
  • Kubernetes
  • Redshift
  • Spark
  • Terraform
  • Airflow
  • Go
Where the posting names them
Sarvam's products produce events, model traces, evals and billing data, and need to read that data back. The Data Platform team builds and runs the central data infrastructure every product uses: ingestion, streaming, the analytical warehouse, transformations, access control and audit. We are hiring a Software Engineer / Senior Software Engineer (2–5 years of experience) to own this platform end to end. You will design, build and run systems that other teams depend on in production, and make real decisions on database internals, streaming and platform design. Stack: Go/Python, ClickHouse Cloud, Kafka, Avro, Airflow, dbt, Kubernetes, Terraform, AWS. What You'll Own & Do
- Experience with large-scale messaging systems like Kafka or RabbitMQ: partitions, consumer groups, delivery guarantees, backpressure. - Good at Go, or good at Python. - You know the usual data-system problems: schema evolution, idempotency, backpressure, partitioning, retention and TTL, CDC.
- You know the usual data-system problems: schema evolution, idempotency, backpressure, partitioning, retention and TTL, CDC. - You have built or run at least one of: an event pipeline, a transformation layer (dbt, Spark or SQL on Airflow), a provisioning or control-plane service, or a multi-tenant data service with access control. - Comfortable with AWS, Kubernetes and Terraform in production.
- You have built or run at least one of: an event pipeline, a transformation layer (dbt, Spark or SQL on Airflow), a provisioning or control-plane service, or a multi-tenant data service with access control. - Comfortable with AWS, Kubernetes and Terraform in production. - You test before shipping, debug with metrics and traces, write RCAs, and document what you build.
- 2–5 years of experience building, shipping and running large-scale, data-intensive systems in production, ideally at a startup where you owned things and were on call for them. - Deep expertise in at least one of: an OLAP database (ClickHouse preferred; Druid, BigQuery or Redshift also fine) or Kafka / event streaming. You understand how a columnar store writes, merges and scans data, or how a partitioned log gives ordering and delivery guarantees. - Experience with large-scale messaging systems like Kafka or RabbitMQ: partitions, consumer groups, delivery guarantees, backpressure.
What You'll Own & Do - Build and run the ingestion path: the service every product sends events to, Kafka behind it, and the pipes that land data in ClickHouse within seconds. Own schema validation, rate limits, dead-letter handling and the client SDKs. - Own the warehouse: ClickHouse Cloud. Design tables for the read path (sorting keys, partitions, materialized views, TTL), separate compute per workload, set per-user limits and per-tenant isolation, and attribute cost to the team that spent it.
- Build and run the ingestion path: the service every product sends events to, Kafka behind it, and the pipes that land data in ClickHouse within seconds. Own schema validation, rate limits, dead-letter handling and the client SDKs. - Own the warehouse: ClickHouse Cloud. Design tables for the read path (sorting keys, partitions, materialized views, TTL), separate compute per workload, set per-user limits and per-tenant isolation, and attribute cost to the team that spent it. - Build reliable data pipelines and solve data problems: dbt models and Airflow DAGs with the BI engineers, CDC from product databases, sync and backfill jobs that are safe to re-run, and the data problems product teams bring you, such as a late source, a number that doesn't match or a query that has slowed down.
Nice to Have - ClickHouse in production: MergeTree, materialized views, projections, quotas, settings profiles, row policies, ClickHouse Cloud. - Kafka in depth: MSK, Kafka Connect, schema registry (Glue or Confluent), Avro.
- Own the warehouse: ClickHouse Cloud. Design tables for the read path (sorting keys, partitions, materialized views, TTL), separate compute per workload, set per-user limits and per-tenant isolation, and attribute cost to the team that spent it. - Build reliable data pipelines and solve data problems: dbt models and Airflow DAGs with the BI engineers, CDC from product databases, sync and backfill jobs that are safe to re-run, and the data problems product teams bring you, such as a late source, a number that doesn't match or a query that has slowed down. - Make the platform self-serve: a registry of every dataset with its owner, schema, freshness and access; provisioning and permissions as code.
- Kafka in depth: MSK, Kafka Connect, schema registry (Glue or Confluent), Avro. - dbt and Airflow at scale. - Audit or security data systems: append-only logs, integrity checks, tenant isolation.
- Deep expertise in at least one of: an OLAP database (ClickHouse preferred; Druid, BigQuery or Redshift also fine) or Kafka / event streaming. You understand how a columnar store writes, merges and scans data, or how a partitioned log gives ordering and delivery guarantees. - Experience with large-scale messaging systems like Kafka or RabbitMQ: partitions, consumer groups, delivery guarantees, backpressure. - Good at Go, or good at Python.
- ClickHouse in production: MergeTree, materialized views, projections, quotas, settings profiles, row policies, ClickHouse Cloud. - Kafka in depth: MSK, Kafka Connect, schema registry (Glue or Confluent), Avro. - dbt and Airflow at scale.
- Make the platform self-serve: a registry of every dataset with its owner, schema, freshness and access; provisioning and permissions as code. - Run it in production: everything as Terraform and Helm with metrics, traces and alerts; be on call; handle incidents end to end, write the RCA and fix the root cause. - Grow the platform: new products keep arriving. You will help decide what the platform should do next and build it, whether that is a new source or sink, or a new way for teams to use the data.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

The Role

Sarvam's products produce events, model traces, evals and billing data, and need to read that data back. The Data Platform team builds and runs the central data infrastructure every product uses: ingestion, streaming, the analytical warehouse, transformations, access control and audit.

We are hiring a Software Engineer / Senior Software Engineer (2–5 years of experience) to own this platform end to end. You will design, build and run systems that other teams depend on in production, and make real decisions on database internals, streaming and platform design. Stack: Go/Python, ClickHouse Cloud, Kafka, Avro, Airflow, dbt, Kubernetes, Terraform, AWS.


What You'll Own & Do

  • Build and run the ingestion path: the service every product sends events to, Kafka behind it, and the pipes that land data in ClickHouse within seconds. Own schema validation, rate limits, dead-letter handling and the client SDKs.

  • Own the warehouse: ClickHouse Cloud. Design tables for the read path (sorting keys, partitions, materialized views, TTL), separate compute per workload, set per-user limits and per-tenant isolation, and attribute cost to the team that spent it.

  • Build reliable data pipelines and solve data problems: dbt models and Airflow DAGs with the BI engineers, CDC from product databases, sync and backfill jobs that are safe to re-run, and the data problems product teams bring you, such as a late source, a number that doesn't match or a query that has slowed down.

  • Make the platform self-serve: a registry of every dataset with its owner, schema, freshness and access; provisioning and permissions as code.

  • Run it in production: everything as Terraform and Helm with metrics, traces and alerts; be on call; handle incidents end to end, write the RCA and fix the root cause.

  • Grow the platform: new products keep arriving. You will help decide what the platform should do next and build it, whether that is a new source or sink, or a new way for teams to use the data.

What We're Looking For

  • 2–5 years of experience building, shipping and running large-scale, data-intensive systems in production, ideally at a startup where you owned things and were on call for them.

  • Deep expertise in at least one of: an OLAP database (ClickHouse preferred; Druid, BigQuery or Redshift also fine) or Kafka / event streaming. You understand how a columnar store writes, merges and scans data, or how a partitioned log gives ordering and delivery guarantees.

  • Experience with large-scale messaging systems like Kafka or RabbitMQ: partitions, consumer groups, delivery guarantees, backpressure.

  • Good at Go, or good at Python.

  • You know the usual data-system problems: schema evolution, idempotency, backpressure, partitioning, retention and TTL, CDC.

  • You have built or run at least one of: an event pipeline, a transformation layer (dbt, Spark or SQL on Airflow), a provisioning or control-plane service, or a multi-tenant data service with access control.

  • Comfortable with AWS, Kubernetes and Terraform in production.

  • You test before shipping, debug with metrics and traces, write RCAs, and document what you build.

  • Passion for data infrastructure and for enabling others by making their data easier to access.

Nice to Have

  • ClickHouse in production: MergeTree, materialized views, projections, quotas, settings profiles, row policies, ClickHouse Cloud.

  • Kafka in depth: MSK, Kafka Connect, schema registry (Glue or Confluent), Avro.

  • dbt and Airflow at scale.

  • Audit or security data systems: append-only logs, integrity checks, tenant isolation.

  • OpenTelemetry, LLM observability (Langfuse or similar), eval pipelines.

  • Built an internal platform that other teams adopted.

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

Bengaluru, Karnataka, India

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

Work authorization

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

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.