Staff Software Engineer

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

You will lead the team that builds and improves the systems deciding when weather is unsafe at a stadium, a school, or a job site, and what happens next. You set technical direction, write production code most weeks, and lead through designs, reviews, and coaching.

You will move the team toward one shared rule for when conditions are unsafe, alerts that reach the right siren exactly once, and closed deals that reach the ERP without manual entry.

The team owns the policy engine, the policy templates customers configure, the sirens and strobes that act on each decision, partner integrations such as Singlewire, and the HubSpot to Acumatica sync for closed deals. Hardware, support, sales, and finance all depend on these systems.

Stack: C# and .NET on Azure Kubernetes, Azure SQL, Azure Service Bus, React and React Native, and Terraform. You will build with AI coding agents every day.

Responsibilities

• Make one source of truth for "conditions are unsafe." Several services keep their own copy of that rule today, and the copies can disagree. Pick the version, move callers to it one at a time, and delete the rest.

• Make the message paths reliable end to end. When a command to a siren is sent twice or never, or a partner webhook carries the wrong trigger, find the shared cause and fix it in the design so that whole class of failure stops.

• Co-own the service that sends commands to field hardware with our hardware team, from the software decision to the device that acts on it.

• Finish the HubSpot to Acumatica sync so every closed deal reaches the ERP on its own, failures alert and can be replayed, and manual order entry goes away.

• Write designs that other teams review, push back on, and build on.

• Bring down reliability numbers several teams share (incidents customers find before we do, pages per day, time to detect) and keep them down after you move on.

• Coach senior engineers until they own systems and designs of their own.

• Review closely, take your turn on call, and help set how the team works with AI agents.

This role is not a fit for an architect who has stopped coding, a manager of managers, or someone whose best work stayed inside one team.

Requirements

• 8+ years shipping production software, including time as technical lead for four to six engineers while you still wrote code.

• Event-driven systems you designed and ran in production: services that talk through queues, consumers that handle the same message twice safely, retries, and dead-letter queues.

• A system you split into services along domain lines. You can say where each boundary sits and why.

• Backend depth in a statically typed language. We use C#; strong Java, Go, or Kotlin carries over.

• Work that reached past your own team. We want to hear all four of these, with the numbers:

  • A design other teams argued with and then built on.

  • A metric several teams shared that you brought down, and that held a quarter after you stepped back.

  • A duplicate system you retired by moving its users over one at a time. How many copies did you delete?

  • A senior engineer you coached into owning a system. Who goes to them now?

• Judgment with AI-generated code. Agent output often looks right when the logic is wrong. You check it against the requirement and can explain every line you ship.

• Willingness to be on call. Our customers get alerts during severe weather, and a dropped alert can put someone at risk.

Nice to have: Azure Service Bus or MassTransit, Kubernetes, SQL Server, IoT or field-deployed hardware, real-time weather or geospatial data, and React or React Native.

Benefits

• You'll want to come into the office. Our Oak Lawn office isn't just a place to sit — it's where ideas move fast and culture stays strong. The whole team is here Monday through Friday, which means real collaboration, no chasing people down over Slack, and a genuinely fun place to spend your work days.

• Your wellbeing is covered. Competitive health insurance, 401(k) with employer matching, and a full suite of voluntary benefits, because you shouldn't have to think twice about the basics.

• Good people, good times. Monthly All-Hands, Office Olympics, happy hours, and more. We take the work seriously and the culture seriously too.

• You're getting in early, and that matters. We're growing fast, but the biggest opportunities are still ahead. The people joining now will help shape what Perry Weather becomes.