About the role

Developer II on Cloud Infrastructure team building and maintaining cloud solutions for Petal's product teams. Collaborating with engineers for cloud stability and reliability.

Responsibilities

Work in the Cloud Infrastructure team: small and technical.
Build and maintain cloud infrastructure using Terraform and OpenTofu on Azure, following IaC practices the whole team can review and trust.
Operate AKS clusters, including Helm releases, ingress/TLS configuration, cert-manager, and Gateway API CRDs.
Improve CI/CD pipelines and GitLab deployment automation so product teams can ship with more speed and less risk.
Contribute to the Developer Internal Platform: golden paths, self-service templates, and tooling that reduces how much product engineers need to know about infrastructure.
Support observability, alerting, and incident response for shared services, including dashboards, runbooks, and joining the on-call rotation over time.
Harden 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 becoming infrastructure experts.
Write and maintain doc-as-code runbooks and operational guides the broader engineering org actually uses.
Use AI tools to move faster on scripting, research, and debugging. Review outputs critically and keep sensitive data out of them.
Show up in design discussions, flag operational risks early, and give useful feedback in code and infrastructure reviews.

Practical cloud experience: you've worked with compute, networking, storage, identity, and secrets in at least one major cloud provider.
Hands-on IaC experience with Terraform or something comparable. You can write modules, not just run them.
Comfort building or maintaining CI/CD pipelines, deployment workflows, and automation scripts.
Working knowledge of Kubernetes: deployments, services, namespaces, and enough kubectl to troubleshoot in production.
A solid foundation in observability: metrics, logs, traces, alerting, and how to find what's actually broken.
You take ownership of scoped work, communicate trade-offs clearly, and stay focused when things get complicated.
Nice-to-have: Hands-on Azure experience, specifically AKS, EntraID, VNet/subnet, RBAC, managed identities, and the Terraform Azure RM provider.
Helm chart management, GitOps workflows, or Traefik as an ingress controller.
Reliability engineering: SLOs, error budgets, incident analysis, or resilience testing.
IaC security scanning with tools like Wiz, Checkov, or Trivy, or time spent in a compliance-heavy environment.
FinOps instincts: you notice cost drivers, think about tagging, and care about the bill.
GitLab CI: pipelines, environments, and reusable components.