Devops Engineer Bengaluru

DevOps Engineer Experience: 2–4 years Location: Bangalore (in-office) Stack: Azure (primary), AWS (parity), Bicep/Terraform, GitHub Actions, PostgreSQL, OpenTelemetry Reports to: CTO About the Role Zenalyst builds an enterprise agentic execution layer for the CFO's office — treasury, procure-to-pay and collections automation for large organisations. We run a multi-tenant platform where every customer has their own physical database, deployed across Azure and AWS with full parity, and offered in three modes — managed multi-tenant, single-tenant in a customer VPC, and bring-your-own-cloud. Enterprise buyers audit us. Banks allowlist our egress IPs. Certificates expire and someone has to know before they do. You will own that infrastructure. This is not a role where you inherit a reliable estate and keep it running; you will be building it out as we scale. Responsibilities Infrastructure and IaC Own and extend our infrastructure as code — Bicep on Azure, Terraform/CDK on AWS Provision and manage container workloads on Azure Container Apps and ECS Fargate, including autoscaling rules driven by CPU, HTTP concurrency and queue depth Manage the tenant provisioning pipeline: current customer, new physical Postgres, new secrets, current connection routing Maintain cloud parity — every change we make on Azure has to have an AWS equivalent CI/CD Own GitHub Actions pipelines across Java, Python, Node and React services Maintain OIDC federated deploy identity — no static cloud credentials anywhere Build and maintain container image pipelines: registries, scanning, signing, geo-replication Manage Flyway and Alembic migration execution across tenant databases safely Networking and security Manage private endpoints, private DNS, NAT gateways and static egress IPs — banks allowlist these, so they cannot change casually Maintain egress FQDN allowlists and firewall rules; default-deny is the baseline Own certificate lifecycle for bank mTLS connections, including expiry alerting Manage secrets i