Lead Full-Stack Application Developer (.NET & Azure)

Job Requisition: Lead Full-Stack Application Developer (.NET & Azure)

Location: Remote / Hybrid (Collaborating across multi-geographic locations)

Team: Autonomous Microservices Engineering Scrum Teams

Framework: Scaled Agile (SAFe) Ecosystem

Position Overview

We are seeking an experienced Lead Full-Stack Application Developer to provide hands-on technical expertise and end-to-end ownership of Azure software development tasks within our distributed scrum teams. In this role, you will collaborate with cross-functional engineering units across multiple geographic locations to ship resilient software while maintaining absolute environmental parity.

You will interact effectively with clients and leadership, adapting your communication style for the appropriate technical or business audience. Rather than acting as a passive recipient of requirements, you will actively read, comprehend, and translate software requirements into structured agile user stories, tasks, and reference documentation.

Role Requirements

• Azure Cloud & Leadership Experience: Minimum 10–12 years of proven experience as a developer building, configuring, and deploying enterprise APIs, websites, and related software into the Microsoft Azure cloud. This must include demonstrated experience guiding and leading an application team to adopt shift-left continuous deployment and continuous integration (CI/CD) workflows.
• Team Enablement Focus: Demonstrated experience in mentoring, upskilling, and enabling team members to successfully adopt and mature these modern CI/CD and shift-left practices.
• Azure Government Cloud (Preferred): Familiarity with Azure Gov Cloud environments alongside a strong awareness of FedRAMP, FISMA, and Zero Trust Architecture is highly desired.
• Core Technology Stack:
  • Languages & Frameworks: Expert proficiency in C#, ASP.NET, JavaScript, TypeScript, HTML, and modern frameworks like Angular.
  • Infrastructure, Security & Automation: Expertise in Git, Terraform, Jenkins, and Azure DevOps. Strong hands-on experience securing applications via Fortify and Sonatype code scanning tools.

Explicit Operational Expectations

1. Shift-Left Quality, Security & Identity Validation

• Context: Continuous Integration pipelines and secure cloud architectures.
• Execution: When code is committed and pipelines run, you ensure all local unit tests pass and all automated regression pass for that topic area.
• Standard: You are directly responsible for fully remediating all critical, high, and medium findings flagged by Sonatype and Fortify code scanning tools prior to any environment deployment and remediating any automated regression identified bugs.

2. Pre-Dev Test Authoring & Agile Story Development

• Context: Feature requirements, user stories, and technical alignment.
• Execution: When features are initialized, your team will assist in translating complex requirements into active scrum tasks and author BDD acceptance criteria using Gherkin syntax (Given-When-Then) in conjunction with the Product Owner and Quality leads..
• Standard: You must check BDD feature files into version control before writing application code, ensuring 100% Requirements Traceability Matrix (RTM) depth back to Azure DevOps user stories.

3. Fail-First Methodology & Red-to-Green Transition

• Context: Local full-stack microservices and API development.
• Execution: You must execute automated tests in a proactive, fail-first (TDD) manner.
• Standard: You will maintain a rapid Red-to-Green cycle velocity, treating successfully passing unit tests as the mandatory gate required to trigger high-level Playwright component acceptance tests.
• Each topic area’s microservices must be able to be tested independently of other topic areas.

4. Dynamic Feature Management & Environmental Parity

• Context: Continuous delivery across distributed, multi-geographic teams.
• Execution: When code progresses through environments, application behavior must be wrapped in conditional feature flags.
• Standard: You must merge incomplete code behind runtime toggles in an "Off State" so that daily commits never disrupt shared environments or cause "staging drift".

5. Performance Tuning, Resiliency & Scaling Validation

• Context: Multi-stage environment progression and system optimization.
• Execution: You own the proactive troubleshooting, configuration, performance tuning, and installation of applications to ensure absolute system resiliency and disaster recovery readiness.
• Standard: You will analyze performance telemetry via Azure Monitor and Application Insights during scaling tests in INT and stress testing in LOD, optimizing code to protect CPU, memory, and database lag targets.

6. Decoupled Architecture via Service Virtualization

• Context: Integration testing within the DEV environment.
• Execution: When verifying cross-application workflows locally, you must keep testing entirely self-contained to avoid stalling pipelines across geographic sectors.
• Standard: Your quality team will utilize API Contract Testing and Service Virtualization for all downstream and upstream interactions inside the DEV environment, restricting live connections to external apps.

7. Zero-Day Production Validation & Dark Launches

• Context: Release approval and promotion to production.
• Execution: When code is pushed to the live PRD environment, you will execute a silent Dark Launch.
• Standard: You will configure precise targeting filters within the feature management UI to allow safe verification using production data and remain ready to execute toggle rollbacks in milliseconds if anomalies arise.

8. Zero Dev-Bug Logging, Documentation & Knowledge Sharing

• Context: Local feature assembly inside the DEV tier.
• Execution: When faults are discovered during local development, you troubleshoot and fix them instantly. You focus formal tracking on higher environments, shifting your developer focus toward creating detailed technical documentation.
• Standard: No formal bug tickets are to be filed for faults identified prior to code leaving the DEV environment. Instead, you dedicate that operational velocity to facilitating knowledge sharing and technical documentation within the team.

Core Performance & Quality KPIs

Your engineering impact within the scrum team will be directly measured by:

• Escaped Defects to Integration Environment: Target: Zero.
• System Resiliency & MTTR: Rapid troubleshooting and optimal application uptime trends.
• Documentation & Asset Fidelity: Up-to-date architectures, API contracts, and team knowledge-base contributions.