{"id":4289359,"url":"https://alion.io/job/delta-exchange-senior-sre","title":"Senior SRE","company":{"id":175589,"name":"Delta Exchange","domain":"delta.exchange","url":"https://alion.io/company/delta-exchange","size_band":"201-500","is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Schema","truth_index":null},"role":"DevOps","role_family":"DevOps","seniority":"senior","employment_type":null,"work_mode":"hybrid","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["India"],"countries":["IN"],"hiring_countries":[],"hiring_countries_total":0,"salary":null,"salary_estimate":null,"experience_years_min":5,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"Amazon EC2","optional":false},{"name":"Amazon EKS","optional":false},{"name":"Amazon S3","optional":false},{"name":"AWS","optional":false},{"name":"CI/CD","optional":false},{"name":"CircleCI","optional":false},{"name":"DNS","optional":false},{"name":"Elixir","optional":false},{"name":"GitHub","optional":false},{"name":"GitHub Actions","optional":false},{"name":"Go","optional":false},{"name":"Grafana","optional":false},{"name":"IAM","optional":false},{"name":"Karpenter","optional":false},{"name":"Kubernetes","optional":false},{"name":"Least Privilege","optional":false},{"name":"Linux","optional":false},{"name":"LLM","optional":false},{"name":"Model Context Protocol","optional":false},{"name":"OpenTelemetry","optional":false},{"name":"Platform Engineering","optional":false},{"name":"Progressive Delivery","optional":false},{"name":"Prometheus","optional":false},{"name":"Python","optional":false},{"name":"Sentry","optional":false},{"name":"SLI/SLO/SLA","optional":false},{"name":"Tcpdump","optional":false},{"name":"Terraform","optional":false},{"name":"VictoriaMetrics","optional":false},{"name":"Apache Kafka","optional":true},{"name":"Chaos Engineering","optional":true},{"name":"Claude Code","optional":true},{"name":"Cloudflare","optional":true},{"name":"Copilot","optional":true},{"name":"Cursor","optional":true},{"name":"Google Workspace","optional":true},{"name":"ISO 27001","optional":true},{"name":"JavaScript","optional":true},{"name":"LLM Guardrails","optional":true},{"name":"MySQL","optional":true},{"name":"Node JS","optional":true},{"name":"Opsgenie","optional":true},{"name":"PagerDuty","optional":true},{"name":"PostgreSQL","optional":true},{"name":"Redis","optional":true},{"name":"SOC 2","optional":true},{"name":"TimescaleDB","optional":true},{"name":"Twingate","optional":true},{"name":"Vault","optional":true},{"name":"Zero Trust","optional":true}],"status":"live","first_seen_at":"2026-11-13T22:36:35Z","employer_posted_date":null,"last_verified_at":"2026-11-13T22:36:35Z","board_verified":false,"closed_at":null,"days_open":0,"trust":{"level":"not_scored","repost_count":null,"flags":[],"days_open":0},"description":"This is a hybrid role, roughly 70% SRE and 30% DevOps / platform engineering. You will spend the majority of your time helping us build the SRE practice at Delta Exchange from the ground up: defining reliability, measuring it, responding when things break, and making sure the same thing does not break twice. The remaining time is spent in the DevOps trenches with the rest of the infra team - Terraform, EKS, CI/CD, AWS platform work, and the automation that keeps the fleet boring.\n\nWe think this split is the right one for our stage: we need someone who cares deeply about reliability and can lead that culture change, but who is also happy rolling up their sleeves and shipping Terraform, tuning a Karpenter provisioner, or debugging a broken CircleCI pipeline. If you are the kind of engineer who has strong opinions about what a good postmortem looks like AND about how a Terraform module should be structured, this role is designed for you. One thing worth calling out up front: security is a first-class concern in every part of this role. We hold customer funds and operate under regulatory scrutiny - every Terraform PR, every access grant, every alert, every incident carries a security lens by default. This is baked into how the infra team thinks, not delegated to a separate track.\n\nThe candidate will have responsibilities across the following functions: \n\nSite Reliability (~60%) \nIncident response and postmortems:\nOwn our incident response process end to end, from paging discipline and severity classification, through incident command, to blameless postmortems and follow-up action tracking.\nBring the muscle memory of production incidents you have already been through, and help us turn each incident into durable systemic improvement.\nSLOs, SLIs, error budgets.\nPartner with service owners to define meaningful SLIs and SLOs for our critical user journeys - order placement, order matching, market data, funding, deposits/withdrawals.\nEstablish error budgets that actually influence engineering decisions, not just dashboards nobody looks at.\nObservability:\nDeepen our observability stack across metrics, logs, and traces. We run VictoriaMetrics, VictoriaLogs, VictoriaTraces, and Grafana, and are rolling out OpenTelemetry distributed tracing across Elixir, Go, and Python services.\nYou will help make this the tooling engineers reach for first when something feels off.\nReliability engineering:\nIdentify systemic reliability risks - single points of failure, thundering herd patterns, cascading failure modes, capacity cliffs - and drive their remediation.\nDesign and run game days and chaos experiments.\nBuild capacity models.\nReview architecture decisions from a reliability lens.\nDisaster recovery, RPO and RTO:\nOwn the disaster recovery posture end to end.\nDefine and continually validate Recovery Point Objectives and Recovery Time Objectives for our critical systems - trading engine, matching, market data, wallet, customer data - in partnership with product and business stakeholders.\nOn-call and operational excellence:\nContribute to a healthy, sustainable on-call rotation.\nImprove alert quality (fewer, better alerts), build runbooks that actually help the person paged at 3 AM, and shift work leftward from on-call to platform improvements.\n\nDevOps / Platform (~40%) \nInfrastructure as code and AWS platform:\nOwn and evolve significant chunks of our Terraform codebase across multiple AWS accounts under Control Tower.\nDesign cloud infrastructure that is secure, cost-efficient, and reproducible - VPCs, IAM Identity Centre permission sets, RDS, networking, CloudFront, S3, and everything in between.\nKubernetes platform.\nOperate and improve our EKS clusters - cluster upgrades, add-on management, Karpenter provisioners, ingress and load balancer controllers, security policies. Make Kubernetes a stable, well-lit platform for our product teams rather than something they need to reason about.\nCI/CD and developer experience.\nMaintain and evolve our CircleCI and GitHub-based delivery pipelines.\nReduce build times, improve pipeline reliability, and work with product teams to make deployments safer via progressive delivery, feature flags, canary analysis, and automated rollback.\nAutomation and toil reduction:\nAutomate away recurring operational work - access provisioning, backup verification, cost hygiene, compliance evidence collection.\nIf you find yourself doing something twice, you should already be thinking about how to make sure you never do it a third time.\nAI-augmented operations:\nWe are actively integrating LLM-based tooling into our SRE and DevOps workflows - AWS DevOps Agent, MCP servers for our observability stack (VictoriaLogs, Grafana, Sentry), and AI-assisted incident investigation.\nHelp us push this frontier: figure out where LLMs genuinely save time (incident triage, log analysis, runbook generation, IaC scaffolding, postmortem drafting), where they do not, and build the guardrails, evaluation, and access controls so we can rely on them in production contexts.\nSecurity engineering as a default:\nSecurity is not a separate lane at Delta - it is woven through everything the infra team does.\nYou will drive least-privilege IAM (we run IAM Identity Centre with ABAC and AWS TEAM for JIT approvals), secrets hygiene, workload hardening on EKS and EC2, Terraform review with a security lens, supply-chain hardening across our CI pipelines, and audit posture for ITGC and future compliance frameworks.\nWhen a security-flavoured incident happens, you help lead the response - and, more importantly, you help design the systems that make those incidents rare in the first place.\n\nRequirements: \n4-6 years of production engineering experience at a product company (SaaS, fintech, exchange, e-commerce, gaming, or similar).\nYou have owned services in production, not just built infrastructure for others to run. A meaningful portion of your recent experience should be explicitly SRE-flavoured (SLOs, incident command, postmortems, reliability projects) rather than pure DevOps ticket work.\nReal incident response experience. You have led or been a first responder on multiple significant production incidents, written the postmortems, and driven the follow-ups to completion. You can talk through past incidents in depth - what broke, how you found it, what the fix was, and what you changed structurally afterwards.\nHands-on backup, DR, and business continuity experience. You have defined RPO and RTO targets, designed backup strategies for stateful systems (relational databases, object stores, message brokers), verified restores by actually running them, and participated in real DR drills - not just documented them.\nStrong AWS fundamentals, ideally including EKS, EC2, RDS, VPC networking, IAM, and how AWS actually fails.\nKubernetes - you have debugged pod evictions, node pressure, PDBs, HPA misbehaviour, DNS issues, and the other Kubernetes classics on a real workload. You have also operated clusters end to end (upgrades, add-ons, security policies), not just deployed to them.\nStrong Terraform in production, at a scale where module design, state management, and drift matter.\nSecurity-first defaults. You reach for least-privilege IAM, secrets managers, network segmentation, encryption in transit and at rest, and audit logging as a matter of habit, not as a checklist after the fact. You have opinions on what makes a Terraform change or a Kubernetes manifest safe or unsafe, and you understand that in an exchange context, a security incident can eclipse a reliability incident in impact.\nSolid observability chops. You know the difference between logs, metrics, and traces, when to reach for each, and how to instrument a service so that future-you can actually debug it. Experience with Prometheus/VictoriaMetrics, Grafana, and OpenTelemetry is a strong plus.\nCI/CD experience with CircleCI, GitHub Actions, or similar - you have designed pipelines, not just edited them.\nComfortable with Linux internals and networking. You can read a tcpdump, reason about a slow query, and know what to look at when latency spikes but CPU is idle.\nProgramming ability in at least one of Go, Python, or a similar language - enough to build tooling, write meaningful automation, and read the services you support. Familiarity with Elixir/BEAM is a bonus given our trading stack.\nFluency with AI/LLM tools in your daily workflow. You use coding assistants (Claude Code, Cursor, Copilot, or similar) to move faster on Terraform, scripts, and code review, and you have calibrated judgment about when AI-generated output can be trusted in an infra context and when it needs careful human review. Bonus if you have wired LLMs into your own on-call, log analysis, or incident investigation workflow.\nCommunication. SRE is a socio-technical discipline. You can push back on a launch politely, write a postmortem that developers actually read, and explain reliability tradeoffs to product and business stakeholders.\n\nNice to Have: \nExperience at a trading platform, exchange, or other latency-sensitive financial system.\nFamiliarity with MySQL/PostgreSQL tuning, replication, and failover behaviour.\nExperience designing cross-region failover and active/passive or active/active architectures for stateful systems (RDS, Kafka/message brokers, object stores) at production scale.\nFamiliarity with AWS Backup, Vault Lock, cross-account backup patterns, immutable backups, and backup cost/retention modelling.\nExperience with chaos engineering tooling (Chaos Mesh, Gremlin, LitmusChaos, or homegrown), including chaos experiments that validate DR assumptions, not just steady-state resilience.\nExperience building on-call and incident tooling - PagerDuty/Opsgenie automation, incident-response bots, retro tooling.\nExperience building or integrating with MCP servers, LLM-based agents, or AI-powered internal tooling for ops workflows.\nExperience using LLMs for log analysis, incident investigation, alert triage, or postmortem drafting in a production context, including opinions on evaluation, hallucination guardrails, and cost/latency tradeoffs.\nDeep experience with Karpenter, spot capacity management, or Kubernetes cost optimisation.\nExperience with zero-trust access tooling (Twingate, Tailscale, Cloudflare Access) and JIT access workflows.\nFamiliarity with regulatory / audit contexts (ITGC, SOC 2, ISO 27001) and how they intersect with SRE and DevOps work.\nPrior experience bootstrapping an SRE practice where none existed, not just operating a mature one.\n\nTech Stack: \nCloud: AWS\nData: RDS MySQL, PostgreSQL, Valkey/Redis, TimescaleDB, various message brokers.\nObservability: VictoriaMetrics, VictoriaLogs, Prometheus, VictoriaTraces, Grafana, OpenTelemetry.\nLanguages: Elixir, Go, Python, NodeJs.\nIaC and CI: Terraform, CircleCI, GitHub.\nAccess: Twingate ZTNA, AWS TEAM for JIT, Google Workspace.\nSkills\nAWS, DevOps, EKS, Grafana, Incident, Kubernetes, Observability, OpenTelemetry, SLO, SRE, Site Reliability, Terraform","description_format":"text","description_chars":10992,"description_truncated":false,"requirements":{"experience_years_min":5,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[],"hiring_excludes":[],"relocation_offered":false,"industries":["Crypto Exchanges"],"lifecycle":[{"event":"open","at":"2026-11-13T22:36:35Z"}],"visa":[],"liveness":{"score":86,"band":"hot","label":"Hiring now","p_open":1,"p_active":0.86,"p_room":1,"age_days":0,"expected_fill_days":36,"reasons":["seen:0","win:early"],"computed_at":"2026-11-14T03:15:08Z"},"pay":null,"html_url":"https://alion.io/job/delta-exchange-senior-sre","json_url":"https://alion.io/job/delta-exchange-senior-sre.json","meta":{"generated_at":"2026-11-14T03:15:08Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","about":"Alion is a live layer of people, companies and AI agents: who they are, whether they are real and active right now, what they do and how to work with them, readable by people and by agents and paid per call.","catalog":"https://alion.io/catalog.json","usage":{"tier":"crawler_verified","counted_by":"address","units_charged":1,"used_today":4784,"day_limit":null,"remaining_today":null,"minute_limit":300,"resets_at":"2026-11-15T00:00:00Z"}},"offers":[{"id":"company.slices","title":"One company in depth, by slice","status":"live","price":{"credits":0.1,"usd":0.01,"plus_per_slice":{"credits":0.05,"usd":0.005}},"unit":"per company, plus each slice with data","note":"the employer in depth","call":{"mcp_tool":"get_company","arguments":{"id":175589},"rest":"https://alion.io/mcp/rest/get_company?id=175589"},"human":"https://alion.io/catalog?offer=company.slices&for=job%2Fdelta-exchange-senior-sre"},{"id":"market.stats","title":"A market slice: pay, demand and time to fill","status":"free","price":{"credits":0,"usd":0},"unit":"per slice","note":"pay, demand and time to fill for this role and place","call":{"mcp_tool":"market_stats"},"human":"https://alion.io/catalog?offer=market.stats&for=job%2Fdelta-exchange-senior-sre"},{"id":"job.search","title":"Open jobs by role, technology, place, pay and visa","status":"live","price":{"credits":0.1,"usd":0.01},"unit":"per posting in a list","note":"similar open postings","call":{"mcp_tool":"search_jobs"},"human":"https://alion.io/catalog?offer=job.search&for=job%2Fdelta-exchange-senior-sre"},{"id":"company.verify","title":"Is this company real and active right now","status":"pilot","price":null,"unit":"per company","request":{"url":"https://alion.io/catalog/request","method":"POST","body":"{\"offer\": \"company.verify\", \"for\": \"job/delta-exchange-senior-sre\", \"note\": \"what you need it for\"}"},"human":"https://alion.io/catalog?offer=company.verify&for=job%2Fdelta-exchange-senior-sre"}],"agent":{"mcp":"https://alion.io/mcp/jobs","mcp_open":"https://alion.io/mcp/open","next":[{"tool":"get_job","arguments":{"id":4289359}},{"tool":"search_jobs","arguments":{"company":"delta.exchange","detail":"compact"}},{"tool":"match_people","arguments":{"job_id":4289359},"note":"people open to offers who fit this vacancy"}],"note":"The same data through MCP tools: https://alion.io/mcp/open needs no sign-in (compact searches, postings, people); https://alion.io/mcp with an Alion account has everything. Docs: https://alion.io/developers"}}