Job Description
The Cloud Infrastructure team builds the platform that helps Petal’s product teams deploy and run applications safely, reliably, and efficiently. Our work gives developers the tools, templates, pipelines, and visibility they need to ship with confidence.
As a Developer II on this team, you’ll own well-scoped infrastructure work from design to delivery and operation. You’ll collaborate with product engineers to understand what they need from the platform, and with fellow cloud engineers to improve the reliability, security, and developer experience of shared services.
You do not need to have used every tool in our stack. Strong cloud fundamentals, Kubernetes experience, Infrastructure as Code, and curiosity matter more than checking every box.
In your day to day, you will:
Build and maintain cloud infrastructure using Terraform, OpenTofu, or similar Infrastructure as Code tools.
Help operate Kubernetes environments on Azure, including deployments, Helm releases, secure traffic routing, certificates, and cluster configuration.
Improve CI/CD pipelines and deployment automation so product teams can ship with more speed and less risk.
Contribute to Petal’s internal developer platform, including golden paths, self-service templates, and tooling that makes infrastructure easier for product teams to use.
Support observability, alerting, and incident response for shared services. Over time, once ramped up, you may join the on-call rotation with support from the team, runbooks, and shared incident practices.
Strengthen security patterns across identity, access control, secrets, private networking, and vulnerability scanning.
Work directly with product teams to help them get what they need from the platform without needing to become infrastructure experts.
Write and maintain practical runbooks and operational guides that other engineers can actually use.
Use AI tools thoughtfully for scripting, research, debugging, and documentation, while validating the output and protecting sensitive information.
Participate in design discussions, flag operational risks early, and give useful feedback in code and infrastructure reviews.