> Markdown version of [/jobs/ext/4637742-staff-software-engineer](https://www.wearedevelopers.com/jobs/ext/4637742-staff-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer - **Company:** Perry Weather - **Location:** Oklahoma City, OK, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Java (Programming Language), .NET Framework, Geographic Information Systems, Microsoft Azure, C Sharp (Programming Language), Code Generation, Microsoft SQL Server, SQL Azure, Software Engineering, Azure Service Bus, ReactJS, AI Coding Agents, Backend, Agentic-AI, Kotlin, Event Driven Architecture, Acumatica Cloud ERP Platform, Kubernetes, Production Code, React Native, Hubspot, Terraform - **Published:** November 8, 2026 - **Apply:** https://www.careerbuilder.com/job-details/staff-software-engineer-oklahoma-city-ok--8467ffea-955c-4002-acfd-6399a17e9ef2 ## About the Role Software Engineering, Safety Standards, School Buildings, Risk, Coaching, Team Lead/Manager, Sales Closing Skills, ERP (Enterprise Resource Planning), Finance, Hardware Administration, * 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. * 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. ## Description 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., * 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.