Delta Exchange

Senior DevOps Engineer

Delta Exchange India

Financial Services · 201-500 employees

3 h ago
Remote devops Senior (5-10 yrs) Full-time India
Log in to apply, save this posting, or score it against your profile with AI.

About the role

You will lead the transition from manual infrastructure to an automated, IaC-first environment while owning the delivery cycle and developer experience. Responsibilities include managing the AWS estate, EKS clusters, CI/CD pipelines, and ensuring high reliability and security standards.

What they look for

DevOps AWS Terraform Kubernetes EKS Python Go Bash CI/CD Infrastructure as Code Networking Linux IAM Observability Disaster Recovery System Administration

Requirements

Candidates must have 5-10 years of hands-on experience in DevOps or infrastructure engineering with deep expertise in AWS and Kubernetes. Strong programming skills in Python or Go and a proven track record of implementing automation and disaster recovery strategies are required.

Full description

About the Company

At Delta, we are re-imagining and re-building the financial system. Join our team to make a positive impact on the future of finance.

🎯 Mission Driven: Re-imagine and re-build the future of finance.

💡 Most innovative cryptocurrency derivatives exchange. With a daily traded volume of ~$0.5billion, and increasing. Delta is bigger than all the Indian crypto exchanges combined.

📈 Offer the widest range of derivative products and have been serving traders all over the globe since 2018 and growing fast.

💪🏻  Founding team is comprised of IIT and ISB graduates. Business co-founders have previously worked with Citibank, UBS and GIC; and our tech co-founder is a serial entrepreneur who previously co-founded TinyOwl and Housing.com.

💰 Funded by top crypto funds (Sino Global Capital, CoinFund, Gumi Cryptos) and crypto projects (Aave and Kyber Network).

About the role

Why this role exists

Two mandates define the job.

Drive the shift from manual to automated. A meaningful part of our infra practice today is still hands-on and ticket-driven. We're not looking for someone to contribute to automation inside an already-automated estate we want someone to own the culture shift and build the automated estate itself. If you've converted a manual shop into an IaC-first one before, this is the exact problem you'll solve here.

Own the delivery cycle so developers can just build. Our backend teams (the exchange app is Elixir) should focus on application code. DevOps owns everything else in the path to production: environments, CI/CD, deploys, devnet/testnet health, observability. Developers are your customers. Spinning up working dev environments is a known bottleneck for us today; fixing that is early, visible impact.

What you'll own

  • The AWS estate. VPC and network architecture, EKS cluster lifecycle (upgrades, autoscaling, IRSA, cluster networking), the data and compute tiers, and the cost consequences of how it's all built. AWS-only shop, EKS at the core.
  • Infrastructure as code as the source of truth. Terraform modules, state strategy, drift control, and a PR-driven review culture authored, operated, and evolved over time. You'll replace tickets with self-service paths and turn runbooks into pipelines.
  • The delivery platform teams ship through. CI/CD treated as a product with owned health (build times, flake rates, deploy frequency), ephemeral/preview and self-service dev environments, and staging/devnet/testnet health.
  • Reliability and disaster recovery. RTO/RPO targets, multi-AZ/region failover, game days and tested restores, SLOs, alert quality, and real incident practice. "We back things up" isn't the bar; restores that have actually been tested is.
  • Day-to-day security hygiene. Least-privilege IAM, secrets lifecycle, patch cadence, network segmentation, and guardrails baked into the IaC you write. (A dedicated cloud-security engineer verifies posture; you build it in from the start.)

What we're looking for

  • 5–10 years in DevOps/platform/infra, currently hands-on (recent pure-management years aren't a fit for this IC role).
  • Deep AWS: you've designed and operated production estates, not just consoled around inside one.
  • IaC as a discipline. We care about the practice, not the product. Terraform is what we use, but Pulumi/CloudFormation backgrounds transfer fine if the estate-ownership is real.
  • Production container orchestration: self-managed Kubernetes or EKS. Deep ECS experience works too; we'll talk through the EKS ramp.
  • Real programming beyond config. Python/Go/Bash past glue scripts, custom exporters/operators/controllers, CI tooling you wrote, or app-level instrumentation. YAML-and-consoles only isn't enough for this role.
  • Strong fundamentals beneath the tools: networking (TCP/DNS/routing/TLS/LB), Linux (systemd, perf, deep debugging), and IAM policy reasoning.
  • DR built or seen closely: you've defined targets, run drills, and tested failover, or worked hands-on alongside someone who did.

Bonus (none of these are filters)• Experience at a lean or regulated org, a first-or-only DevOps hire, or building a platform under real resource constraints. Fintech/exchange operations are a plus.

  • A track record of the manual→automated transformation this role is built around.
  • Working AI-augmented with guardrails, LLM-assisted runbooks or IaC gated behind policy-as-code and review standards, agentic tooling built for leverage without shipping slop.
  • Any BEAM/Elixir exposure you're never expected to write Elixir, but familiarity means you could self-serve Elixir observability from day one.

Similar roles