Senior Azure Engineer

Washington, United States | Posted on 10/01/2026

Location: Washington, DC — 888 First Street NE. Hybrid; on site at least two (2) days per week, with additional on-site days for migration events, cutovers, and client reviews.

Clearance: Must be able to obtain and maintain a Public Trust clearance.

Role type: Senior individual contributor — architecture, analysis, and recommendation. Not a people-management or day-to-day operations role.

Experience: 8+ years in infrastructure engineering, with senior-level Azure design ownership.

Key Personnel: This is a designated Key Role on the program. The government client reviews and approves the selected candidate's resume before start — a standard step on federal programs, and one we will walk you through.

A federal agency is planning its move off Azure VMware Solution (AVS) and onto native Azure, and this role owns the technical answer to how. You will design the post-AVS target state, determine which Azure-native services can replace the platforms the agency runs today, build the cost model that supports budget submissions, and shape the 18–24 month cloud roadmap that leadership executes against.

Early work includes assessing Azure application delivery services — Application Gateway, Front Door, and Load Balancer, as alternatives to F5, and answering the broader question of which legacy and third-party platforms can be replaced with Microsoft-native capabilities over the next 18–24 months.

You are the program's deep Azure expert. Your designs set the target state, and your options analyses and recommendations go to the Infrastructure Engineering Lead, program leadership, and government stakeholders as the plan of record. You will assess the current environment, evaluate Azure-native services against what the agency runs today, prototype candidates in non-production, and turn the results into decision-ready recommendations.

Direction and prioritization come from the Infrastructure Engineering Lead; the depth that makes those decisions sound comes from you.

The work is architecture and analysis rather than ticket queues or team management. You will partner closely with the network, systems, and security teams so that what you design is something they can actually run, and serve as the escalation point when a hard Azure problem lands.

Own the post-AVS target-state design. Develop and compare target-state options, identify decision points, dependencies, and risks, and plan how workloads move from AVS to native Azure services.

Shape the 18–24 month cloud roadmap. Provide the technical inputs that keep the roadmap aligned to agency planning and budget cycles.

Evaluate and prototype Azure-native capabilities. Research, prototype, and recommend Microsoft services that replace legacy platforms, improve service delivery, and advance the agency's modernization goals.

Build the cost case. Develop and maintain the AVS-versus-native-Azure cost model, identify near‑term savings in the existing environment, and support budget submissions with defensible projections.

Make designs operable. Document the operational impacts of design decisions — monitoring, patching, backup, disaster recovery (DR), runbooks — and advise on the skills operations teams will need as the model shifts from traditional networking and virtualization to cloud platform management.

Serve as the Azure escalation point. Provide expert guidance on complex Azure issues and share what you know with the engineers around you.

Write it down well. Produce technical designs, options analyses, recommendation memos, roadmaps, and change records suitable for government review.

You do not need all of these. Tell us which ones you have.

Cloud cost modeling and optimization…