C#/.NET Development & Azure Consulting
Backend services, integrations, architecture reviews, and deployment pipelines, from a .NET consultant in Boise, Idaho who has run this in production at scale.
Vague on paper, real in production
C# has been my main language for my whole career. This is the work of designing data models, wiring up integrations, handling the edge cases, and shipping something the business can rely on every day. Backend services, APIs, Azure Functions, SQL Server, React front ends when the project needs one.
I’m comfortable owning a system end to end: the architecture decisions, the integrations nobody wants to touch, and the operational details (logging, retries, audit trails) that decide whether it survives contact with real users. I’ve done it on a platform serving 500+ users at 99.9% uptime, including inside Azure Government where the compliance rules are stricter.
- Backend services and APIs in .NET, with the boring parts (auth, validation, logging, retries) done properly.
- Azure integrations: Functions, Service Bus, storage, Managed Identity, and the glue between systems that don’t want to talk.
- Modernization of .NET Framework and legacy code that has gotten hard to change, without a big-bang rewrite.
- Full-stack builds with React on the front and .NET on the back.
- Architecture reviews: a two-week audit of what you have, what’s fragile, and a written path forward with the trade-offs spelled out. Useful before a big build or after inheriting a system.
- CI/CD and deployment automation in Azure DevOps. If your team dreads deploys, this is the fastest win available.
Project or Retainer
Scoped project work for a defined build, or a retainer for ongoing .NET and Azure needs. Architecture reviews are fixed-scope: two weeks, written recommendations. Either way you get direct communication and an engineer who owns the outcome, not just the ticket.
Boise, Idaho · Remote-Friendly
Based in Boise, working with Idaho businesses and government teams and with remote clients anywhere in the US. Azure Government work can be done fully remote inside the required compliance boundaries.
4 Hours to 15 Minutes
I rebuilt the release pipeline for a mission-critical government system in Azure DevOps. Deploys went from a four-hour manual procedure to 15 minutes, and the human-error steps went away with it.
Read Case StudyHave a system that needs to hold up?
Tell me what you’re building or what’s currently fragile, and I’ll be direct about whether I’m the right fit.