Senior Developer, Data Engineer
Intercontinental Exchange (company site, opens in a new tab)3+ yrsHyderabadOn-siteDirect career pageEst. 30–45 LPA
Posted 5d ago
Reach people at Intercontinental Exchange
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Intercontinental Exchange you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own production Airflow orchestration, including complex DAGs, Kubernetes operations, reliability, testing, and team-wide engineering standards.
- Build fault-tolerant ETL/ELT pipelines and maintain an Apache Iceberg lakehouse, with data quality, freshness, governance, and observability built in.
- Deliver reusable data platform components and reliable datasets for analytics and ML; contribute to architecture decisions, mentoring, runbooks, and on-call coverage.
Minimum Requirements
- Work Experience Required: At least 3 years running Apache Airflow in production; demonstrable production-scale data engineering and pipeline orchestration experience.
- Hands-on experience deploying and operating Airflow on Kubernetes using KubernetesExecutor or CeleryKubernetesExecutor, including Helm, pod templates, resource tuning, and upgrades.
- Strong, tested Python engineering and experience building maintainable batch or incremental ETL/ELT pipelines with validation and lineage.
- Practical experience with Apache Iceberg and lakehouse design, Databricks (including Delta Lake and Unity Catalog), and building dbt projects integrated with Airflow.
Ideal Candidate Profile
- Has operated Airflow and data pipelines at production scale, with ownership extending to scheduler health, incident prevention, monitoring, and on-call.
- Can make practical lakehouse design decisions around Iceberg tables, medallion layers, schema evolution, partitioning, and reliable downstream access.
- Experience with Kafka or streaming, Spark, cloud data services, infrastructure as code, governance tools, or ML feature pipelines is an advantage.