Software Engineer, DevOps
PlaneIndiaOn-Site
Needs a free Superjobs account. You'll finish on Plane's Ashby page.
Skill score
Summary
This person owns Plane Cloud's infrastructure and the CI/CD and installation path that delivers one codebase to Plane Cloud and to self-hosted, sovereign, and air-gapped customer environments. They debug problems across every layer, respond to alerts, and work with engineers and customer platform teams, so the role suits an experienced DevOps or SRE engineer who enjoys end-to-end ownership.
- Function
- Development
- Estimated salary
- Est. ₹8–12 LPA
- Estimated for a mid-level role, ~3 yrs experience (typical for the level), India. Not published by the employer.
- Work mode and location
- On-Site, India
- Employment type
- Full-time
Job description
Overview
Plane runs as a managed Cloud service, on customers' own infrastructure, and inside isolated environments that never touch the internet. Adoption is growing fastest on Plane Cloud and in sovereign clouds, and that growth is why this role exists. Every one of those environments is somewhere our releases have to install, upgrade, and stay healthy, mostly on machines we will never log into. You will own the infrastructure behind Plane Cloud and the path that gets one codebase into every self-hosted environment: Terraform, Kubernetes, CI/CD, and the alerts that tell us something broke. You will work with backend and frontend engineers in San Francisco and Hyderabad, and directly with customers' platform teams when a self-hosted install misbehaves.
Roles and responsibilities
- Own Plane Cloud's infrastructure on AWS and Kubernetes: defined in Terraform, deployed through GitOps with Argo CD and Rancher Fleet, and sized so capacity and cost keep pace with usage.
- Build and run the CI/CD pipelines that ship one codebase to Plane Cloud and to the Docker Compose and Kubernetes deployments self-hosted customers run.
- Design installs and upgrades that work in places you will never log into: customers' own clouds, sovereign clouds, and air-gapped networks with no internet connection.
- Run observability across the platform, with Datadog and the LGTM stack for metrics, logs, and traces, so we hear about degradation before a customer does. When an alert fires, you respond.
- Own infrastructure security: access controls, vulnerability management, and the findings Wiz surfaces. Regulated industries choose Plane for control and auditability, so this work is part of what customers buy.
- Work daily with backend and frontend engineers in San Francisco and Hyderabad, with customers' platform teams, and with community members whose self-hosted issue reports land in public on GitHub.
- Debug problems that cross every layer. A self-hosted ticket can turn out to be a reverse proxy, a Postgres setting, a firewall rule, or a bug in our own code. You will chase it to the real cause, then turn the fix into a default or a doc so the next customer never hits it.
Skills required
Top skills
- AWS
- Kubernetes
- Terraform
- Docker Compose
All skills (8)
- CI/CD pipelines
- Python
- Go
- Bash
- Prometheus
- Postgres
- Argo CD
- Rancher Fleet
Qualifications
You have run production infrastructure on AWS or GCP, defined as code in Terraform or similar, and you can walk us through an outage you handled and what you changed afterwards.
- You have operated Kubernetes clusters in production, not only deployed to them, and you have packaged applications with Docker and Docker Compose.
- You have built CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins, or similar) that a team shipped through every day, and you automate the rest in Bash, Python, or Go.
- You follow a problem past the edge of your job title. You have traced an issue into networking (DNS, TLS, firewalls, VPNs, load balancers), a reverse proxy like Nginx or Caddy, or the Postgres and Redis behind an application, and you can tell us how you found it.
- You have set up monitoring and alerting (Prometheus, Grafana, Datadog, or similar) that caught a real problem before users did.
- You have put infrastructure security into practice: least-privilege access, secrets management, and patching vulnerabilities on a schedule rather than after an incident.
Nice to have
- You have contributed to Plane, run it self-hosted, or contributed to an open-source infrastructure tool people rely on.
- You have deployed into regulated, sovereign, or air-gapped environments, where pulling an image from the internet was not an option.
- You have run GitOps with Argo CD or Rancher Fleet, or managed many clusters with Rancher.
- You have operated RabbitMQ or Kafka in production.
- You have used AI agents in operations work, and you have opinions about what an agent should be allowed to change on real infrastructure.
Other details
- Languages: Python, Go, Bash
- Infrastructure as code: Terraform
- Infrastructure: AWS, Kubernetes, Docker, Rancher
- Delivery: GitOps with Argo CD and Rancher Fleet
- Data and messaging: Postgres, Redis, RabbitMQ, Kafka
- Observability: Datadog, LGTM stack (Loki, Grafana, Tempo, Mimir)
- Security: Wiz
- Incident management: incident.io
- Everyday tools: GitHub, Plane (yes, we run on it), Slack
Company info
About Plane
Plane's mission is to build the infrastructure the world's work runs on. Every organization runs on three things: the projects it's driving, the knowledge it keeps, and the requests it fields. Plane brings all three into one open, adaptable platform: simple enough for any team to adopt, dependable enough for