Senior .Net Applications Developer at AVER
Washington, DC
—
Jul 19, 2026
Washington, DC
Jul 21, 2026
What this job asks for AI summary
A senior-level software development role building and maintaining .NET-based applications for a government client, covering the full development lifecycle from requirements gathering through deployment and production support. Day-to-day work includes designing data automation solutions, developing web and back-end services, integrating cloud infrastructure on Azure, and providing technical guidance to junior team members. Suits an experienced .NET developer comfortable with government environments and a broad Microsoft stack.
Senior level · 8+ years · Washington-Arlington-Alexandria, DC-VA-MD-WV · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 3 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $154,930 (middle half $123,720–$176,230).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The posting explicitly states a Bachelor's degree OR equivalent applied experience may be substituted, so no hard degree requirement is set.
The security requirement is the ability to obtain a Public Trust (not a clearance per se), and US citizenship is required. This is not a formal security clearance gate (Confidential/Secret/TS), so the clearance requirement is set to None — but note that US citizenship and Public Trust suitability are hard requirements for this role.
The role is hybrid (2 days/week on-site in Washington, DC), not fully remote.
RBAC and claims-based authentication appear in the required section as concepts rather than named tools; they are covered by the Entra ID, SAML, OAuth 2.0, OpenID Connect, and JWT skills already captured.
Agile Scrum & Kanban appear only under Desired Requirements, so they are marked preferred.
MVC and MVVM design patterns appear under Desired Requirements and are conceptual methodologies rather than named tools, so they are omitted per extraction rules.
Microservices architecture appears under Desired Requirements as a concept and is omitted; cloud-native development and secure coding practices are similarly conceptual and omitted.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): Azure API Management.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.