Senior .Net Developer

Senior.NET DeveloperImprovix Technologies is hiring a Senior.NET Developer to be the person who settles that argument. You'll own architecture and tooling decisions across a portfolio of Microsoft and modern web applications on a high-visibility federal program — defining the patterns, setting the standards, running the modernization roadmap, and making the call on when low-code is genuinely the right answer and when it's a trap with a short time-to-demo.New work here is built on ASP.NET Core and a currently supported.NET release. The Framework applications in the portfolio are migration candidates with a roadmap, not a permanent tax — and shaping that roadmap is part of the job. Three days a week onsite in DC, two remote.Why Senior Engineers Take This RoleModern.NET is the destination, not the pitch.You set the standards rather than inherit them.The build-versus-buy call is actually yours.Modernization with a real mandate.You stay in the code.What You'll OwnArchitecture & Technical DirectionOwn the technical architecture for full stack applications built on ASP.NET Core and modern web frameworks — defining the patterns, standards, and practices the team builds against.Evaluate, select, and recommend tools, frameworks, libraries, and platforms, weighing scalability, maintainability, security, and total cost of ownership — and articulate the reasoning, including to people who will disagree with it.Lead technical design reviews and make the architectural calls that keep a mixed portfolio coherent instead of merely functional.Define and maintain the modernization roadmap: migrating legacy SharePoint-backed systems to modern architectures, and planning the path for .NET Framework applications onto supported .NET releases.Identify and remediate technical debt, performance bottlenecks, and security risks across the portfolio — ideally before they become incidents.Hands-On DevelopmentPrototype solutions, unblock developers, and contribute code on critical-path items.Build and maintain data access with MS SQL and Entity Framework Core, including schema design for enterprise applications.Set the reference implementations — the service, the API, the test project that everyone else copies — so the standards exist in code and not only in a document.Microsoft Platform StrategyProvide architectural oversight for Power Platform solutions — guiding when Power Apps (canvas and model-driven), Power Automate, and Dataverse are the right fit, and when custom development is the honest answer.Establish data architecture and governance patterns for Dataverse: table design, relationships, business rules, and security role models.Lead SharePoint modernization across SharePoint Online and legacy SharePoint (2013 or newer).Keep the low-code estate governed so it stays an asset rather than turning into shadow IT with a Microsoft logo on it.Integration & API StrategyGuide API strategy and integration architecture — RESTful service design, authentication patterns, and service-oriented design.Architect integrations across Microsoft 365, SharePoint, Teams, and external systems.Define identity and access patterns against Active Directory and enterprise identity services.Engineering Practice & QualityEstablish coding standards and own the code review process, so quality is consistent across the team rather than dependent on who happened to write it.Improve CI/CD pipelines, branching strategy, and release management to support frequent, reliable deployments — GitHub Actions, Azure DevOps, or similar.Build application security into the design rather than into a remediation ticket filed after the scan.Support deployment activities, including the occasional weekend release window.Team LeadershipMentor mid-level and junior developers through knowledge transfer sessions, pairing, and review that teaches rather than just approves.Partner with program leadership, government stakeholders, and technical leads to translate mission requirements into achievable technical solutions.Present technical recommendations to engineering teams and non-technical stakeholders, and leave both audiences understanding the tradeoff.What You BringThese are the requirements — everything in “Bonus Points” below is genuinely optional. If you meet this list, apply.5+ years of progressive C# and.NET development experience, including time setting technical direction for other developers.Recent, hands-on ASP.NET Core work on a currently supported.NET release —.NET 8 or later, with.NET 10 the current LTS. This is the stack we're hiring for, and it's the part of your résumé we'll read closest.Demonstrated ownership of architecture and technology selection decisions for enterprise applications — and the ability to explain the reasoning behind them.Strong command of full stack architecture, including modern frontend frameworks (React or similar), RESTful API design, and service-oriented patterns.Hands-on Microsoft Power Platform experience — Power Apps (canvas and/or model-driven), Power Automate, and Power BI — with the judgment to know when low-code is and isn't the right answer.Experience leading SharePoint modernization or migration, with familiarity across SharePoint Online and legacy SharePoint (2013 or newer).Deep experience with MS SQL, Entity Framework or EF Core, and database design for enterprise applications.Proven experience establishing or maturing CI/CD pipelines and DevOps practices (GitHub Actions, Azure DevOps, or similar).Experience running code reviews, setting coding standards, and mentoring development teams.Strong understanding of application security concepts, Active Directory, and identity and access patterns in enterprise environments.Working familiarity with Microsoft 365 — SharePoint Online, Teams, Outlook, Excel, Word, and OneDrive — in a collaborative enterprise environment.Excellent communication skills, able to present a technical recommendation to an engineering team and a non-technical stakeholder in the same meeting.U.S. citizenship and an active Secret clearance.Ability to work onsite in Washington, DC three days per week, including occasional Saturday hours for deployment activities.Bonus PointsExperience migrating.NET Framework applications to modern .NET — including the parts that don't port cleanly and the judgment to know what should be rewritten instead.Working familiarity with.NET Framework and older ASP.NET (MVC or Web Forms) for supporting the legacy portfolio.Architecting solutions in Azure, including deployments in a federal or FedRAMP context.Minimal APIs, dependency injection patterns, or modern ASP.NET Core middleware and configuration practice.Dataverse for Teams, and Power Apps embedded in Microsoft Teams.TypeScript across the frontend, Node.js development, or both.Containerization and orchestration — Docker, Kubernetes, or similar.Integrating AI or LLM capabilities into applications, or AI-assisted tooling into team workflows.Working knowledge of Section 508 accessibility standards.Prior experience supporting federal programs and working inside government security and compliance frameworks.Microsoft certifications — Azure Solutions Architect, Power Platform Solution Architect, or equivalent.Working HereImprovix Technologies delivers secure, modern, integrated technology solutions that keep the nation's most critical systems running. We're small enough that a good idea reaches a decision-maker in a day, and close enough to the mission that you'll know exactly what your work supports.On Core versus Framework: there are .NET Framework applications in this portfolio and you will touch them — we're not going to pretend otherwise. But we're hiring for where the portfolio is going, not where it's been. New development targets ASP.NET Core on a supported release. If your last several years have been Framework and Web Forms, you're still welcome to apply, but come ready to talk about how you'd plan the move — because that conversation will happen in the interview and then again most quarters after you start.A straight answer on schedule: three days onsite in Washington, DC and two remote, plus occasional Saturday hours when a deployment window requires them. The weekend time is genuinely occasional and tied to releases, not a standing expectation — but it is real, and we'd rather you hear it now than in week three.What “