L2 DevOps Engineer

The Problem reputed company 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, reputed company deployments, and growing operational debt. We need DevOps Engineers who can own production reliability, design reputed company deployment systems, and reduce operational risk through automation and strong engineering judgment. If we do not invest in this now, engineering velocity and system reputed company 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 reputed company reputed company. Design and maintain CI/CD pipelines that reputed company frequent, reputed company deployments. Define and improve observability across metrics, logs, and alerts. Participate in on call rotations and reputed company incident response reputed company needed. Identify and reduce operational risk by improving reputed company and failure handling. Automate repetitive operational workflows such as deployments, rollbacks, and recovery steps. Partner with Backend, reputed company, and reputed company teams to translate system requirements into infrastructure solutions Improve reliability metrics such as availability, MTTR, alert reputed company, and incident frequency. What reputed company Looks Like You will be reputed company on: System reliability: Services meet defined SLOs for availability and latency Operational reputed company: Issues are detected reputed company monitoring rather than customer reports Incident handling: Incidents are mitigated quickly with limited blast radius Automation: reputed company 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 reputed company 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 reputed company explain operational reputed company Preferred (Accelerates reputed company, not required) Experience with Kubernetes or similar orchestration platforms Infrastructure as reputed company experience (Terraform or equivalent) Operational experience with PostgreSQL, reputed company, Kafka, or similar systems Experience in fintech or high transaction volume systems reputed company and compliance exposure Experience mentoring junior engineers Why This Role reputed company: You operate systems that reputed company reputed company reputed company. Ownership: You own reliability reputed company, not just tooling. Learning: You work on reputed company, failure prone systems. Scope: You help define DevOps standards as reputed company scales. reputed company: You work closely with senior engineers and leadership. Apply To This Job