We are redirecting you to the source. If you are not redirected in 3 seconds, please click here.

L2 DevOps Engineer at OpenFX. . Location: Bengaluru/Remote.  . . The Problem. . OpenFX processes billions of dollars in transaction volume every month across global corridors. Our systems power pricing, transaction execution, settlement, reconciliation, and risk management. These systems must remain available, observable, and correct under retries, partial failures, external partner downtime, and sudden traffic spikes.. . As volume scales from billions to tens of billions, operational complexity increases faster than headcount. Without strong DevOps ownership, we risk silent failures, slow incident response, fragile deployments, and growing operational debt.. . We need DevOps Engineers who can . own production reliability. , design safe deployment systems, and reduce operational risk through automation and strong engineering judgment.. . If we do not invest in this now, engineering velocity and system trust will degrade.. . . What You Will Actually Do & Own. . In your first 6 to 12 months, you will:. . . Own reliability and operability of 1 to 2 production services. , including services on the money path.. . Design and maintain CI/CD pipelines. that enable frequent, safe deployments.. . Define and improve observability. across metrics, logs, and alerts.. . Participate in on call rotations. and lead incident response when needed.. . Identify and reduce operational risk. by improving resilience and failure handling.. . Automate repetitive operational workflows. such as deployments, rollbacks, and recovery steps.. . Partner with Backend, Security, and Infra teams. to translate system requirements into infrastructure solutions. . Improve reliability metrics. such as availability, MTTR, alert quality, and incident frequency.. . .  . . . What Success Looks Like. . You will be measured on:. . . System reliability:. Services meet defined SLOs for availability and latency. . Operational clarity:. Issues are detected via monitoring rather than customer reports. . Incident handling:. Incidents are mitigated quickly with limited blast radius. . Automation:. Manual operational work decreases over time. . Judgment:. Infrastructure tradeoffs are deliberate and defensible. . Trust:. . Engineering teams rely on the platforms you operate. . .  . . Requirements. . Required (Non negotiable). . . 3 to 7 years experience operating production systems. . Strong fundamentals in Linux, networking, and cloud infrastructure. . Experience running containerized workloads in production. . Hands on experience with CI/CD pipelines. . Experience designing monitoring and alerting systems. . Proven experience handling production incidents. . Ability to clearly explain operational decisions. . . Preferred (Accelerates ramp, not required). . . Experience with Kubernetes or similar orchestration platforms. . Infrastructure as Code experience (Terraform or equivalent). . Operational experience with PostgreSQL, Redis, Kafka, or similar systems. . Experience in fintech or high transaction volume systems. . Security and compliance exposure. . Experience mentoring junior engineers. . .  . . Why This Role. . Impact:. You operate systems that move real money.. . Ownership:. You own reliability outcomes, not just tooling.. . Learning:. You work on complex, failure prone systems.. . Scope:. You help define DevOps standards as the company scales.. . Access:. You work closely with senior engineers and leadership.. .  . .  . .  . .