About the role

About Perry Weather Perry Weather is the weather safety standard for organizations that operate outdoors. We combine on-site weather hardware with a software platform that automates alerts, siren activations, and safety decisions for more than 3,000 organizations — from the PGA of America, the NFL, and MLB to Turner Construction, thousands of school districts, cities, and golf courses. We've grown 80%+ annually for five consecutive years, and are continuing to grow. We're headquartered in Dallas at The Centrum, in the Oak Lawn neighborhood, where our teams work together every day to help organizations make faster and safer decisions when weather puts people, assets, and operations at risk. About the Role We're looking for a Platform Engineer to help build and run the infrastructure the rest of engineering depends on. You'll partner closely with our Lead Platform Engineer, designing and delivering the work together, and own real surface area from the start: infrastructure as code, our Kubernetes environments, delivery pipelines, observability, and the guardrails that keep all of it safe to change. Engineering is your customer. Success in this role looks like fast service setup, uneventful deploys, and engineers who can diagnose a failing workload without asking for help. Engineering here also works with AI coding agents daily, which adds to the platform team's job: checks that catch generated infrastructure errors before they apply, scoped credentials and audit trails for automated actors, and cost reporting that accounts for agent usage. You'll use agents in your own work and help build these controls for everyone else. Responsibilities - Infrastructure as code. Write and maintain the Terraform that defines our cloud footprint, review changes for blast radius, and keep our modules usable by engineers outside the platform team. - Kubernetes and workloads. Run our clusters and the Helm-deployed services on them, including resource tuning, scaling behavior, and the failure modes that only show up under load. - Delivery pipelines. Build and maintain CI/CD in GitHub Actions so that builds, tests, and deploys are fast and dependable enough that engineers rely on them. - Observability and reliability. Improve the instrumentation, dashboards, and alerting that tell us how the platform is behaving, and make alerts specific enough that people act on them. - Cost and capacity. Track where our cloud spend goes, find the waste, and add controls that catch expensive changes before they ship. - Guardrails. Secrets management, least-privilege access, dependency and image scanning, and policy checks that catch mistakes during review. - AI and automated actors. Coding agents and automation are regular consumers of our platform. You'll give them scoped identities and audit trails, add the checks that catch generated infrastructure mistakes before they apply, and track what their usage costs alongside the rest of our spend. - On-call and incident support. Share the on-call rotation, respond when the platform degrades, and make the changes that prevent a repeat. Requirements - 4+ years in platform, infrastructure, DevOps, or backend engineering, with real ownership of production infrastructure - You're fluent in infrastructure as code. Terraform experience is ideal, but if you've come from another IaC tool, the fundamentals carry over. You've written and maintained IaC in production and know how to keep what's declared in code in sync with what's actually running - Working depth in a major cloud, including managed databases, networking, identity, and secrets. We're primarily on Azure, but AWS or GCP experience transfers Nice to Have - Kubernetes in production. You can take a failing workload, trace it through configuration, networking, and resource limits, and explain what went wrong to the engineer who owns the service - CI/CD you've built and debugged, ideally GitHub Actions. You've fixed a pipel