Senior Dotnet Developer
About the role
- We’re looking for a Senior .NET / Azure Engineer to join a high-impact modernization effort for a federal client.
- This is not a typical developer role; we need someone who can step into an active project, improve delivery velocity, and help stabilize a growing engineering team.
- You’ll be working on a greenfield Azure-based platform replacing a legacy InfoPath system, collaborating closely with architects and cross-functional teams.
- What You’ll Be Working OnBuilding modern applications using ASP.NET Core and Azure
- Replacing legacy systems (InfoPath to cloud-native architecture)
- Designing and integrating APIs with downstream systems
- Improving team velocity, code quality, and delivery standards
- Contributing to CI/CD pipelines using Azure DevOps (ADO)
- ASP.NET Core / C#Azure (App Services, Azure SQL, AD/Auth)
- Experience with Azure DevOps (CI/CD pipelines)
- Solid experience with REST APIs and integrations
- Ability to work in fast-moving, evolving environments
- What Sets You Apart
- Experience modernizing legacy systems (InfoPath, SharePoint, etc.)Proven ability to step into struggling teams and improve delivery
- Strong debugging and problem-solving skills
- Comfortable acting as a mentor / technical leader when needed
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
