Senior Software Engineer (.NET / Azure)

Senior Software Engineer (.NET / Azure) *Zephyr Wind Services · Fully remote (Boise\-area candidates only) · Must be authorized to work in the U.S. without sponsorship · In\-person interviews required · $130,000–$140,000* **The short version** We're a small software team inside a 150\+ person wind energy company, and we're growing the crew. We want a Senior Software Engineer — a strong, trusted builder who'd rather be on a tiny team where every person's work matters than buried in an eight\-person feature team where nobody owns anything. We're an AI\-first shop: we plan and design our solutions with Claude Code, let it write the code, then bring deep expertise to bear making sure that code is right. That's the heart of the role, and the first thing we'd want you to be excited about. This is an individual contributor role reporting to the Director of Software Engineering, working shoulder\-to\-shoulder with our Senior engineer and the Lead we're also hiring. A handful of people building software that runs a real, growing business. We move fast, hold a high bar, and have fun doing it. **What we actually do all day** This part will either light you up or send you running — worth knowing which before you apply. Our day\-to\-day is not typing out .NET by hand. It starts with planning: genuinely designing the solution alongside Claude Code, thinking through the approach before a line is written. Then we let it write the code and work with it to get that code right — making sure it follows our established patterns, doesn't quietly invent new ones, doesn't ship subtle bugs, and reflects the big\-picture context the tool simply doesn't have. We bring the large context to the small context of the agent. That's the craft now. We work in Claude Code inside Visual Studio — every task starts in plan mode, working out the architecture and decisions with the agent before a line of code is written. We use Skills to keep our patterns consistent, and we track everything in Azure DevOps. A huge part of “right” is keeping it simple. Left unsupervised, an AI will happily over\-engineer, reinvent wheels, and build clever, convoluted code paths. We don't want any of that. The simple solution is almost always the correct one, and code should be human\-readable: if a teammate can't understand it, it gets rejected — partly because it's hard to troubleshoot, partly because complicated code is more likely to need troubleshooting in the first place. So when we say “deep .NET experience is non\-negotiable,” it's not because we want you grinding out boilerplate. It's because you can't supervise code you can't read fluently. The .NET fluency is what lets you spot the wrong pattern, the un\-idiomatic API, the introduced bug, the thing that works but is needlessly complex. Our API, Functions, and services are where the sharpest eye is needed. One thing to be clear about up front: this is a shared, standardized workflow — same tools, same model, same patterns, on purpose