Senior Software Engineer - Data Infrastructure

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.