Engineering Lead

About this role

Engineering Lead Large, Complex Federal Government Program | Full-Time W-2 | Fully Remote (U.S.) The Problem We're Hiring You to Solve Monthly production releases. Zero escaped critical defects. Most engineering organizations treat those as a tradeoff. On this program they are both commitments, measured every release, in front of the customer. We are hiring the engineering leader who builds an organization that delivers both at once: multiple cross-functional development teams modernizing a federal home loan benefit platform while sustaining the 20-year-old system it replaces. If you believe speed and quality are the same discipline practiced well, and you have the delivery record to prove it, keep reading. The Opportunity Most engineering leadership roles ask you to protect a delivery machine someone else built. This one asks you to build the machine. The program spans multiple development teams working in parallel across a modern platform (Salesforce-centered, configuration-first, supplemented by serverless capabilities in a government cloud) and a legacy suite that must stay stable until it is decommissioned. Work arrives through a formal intake process that turns business needs into executable plans with committed scope, timelines, and team sizing in days. Then your organization delivers against those commitments, publicly and measurably. The quality bar is unusually explicit. Every release ships with 100% automated test coverage for its features before user acceptance testing begins. Defect detection before UAT must exceed 95%. Escaped critical defects must be zero. Critical production bugs get fixed in three days. Accessibility and security compliance are release gates, not aspirations. These are not stretch goals on a slide. They are how the program measures the engineering organization every month. That bar is exactly why this role is interesting. Hitting it once takes heroics. Hitting it every month takes an engineering system: disciplined definition of done, test automation as a first-class craft, engineers who own quality instead of throwing code over a wall, and a leader who builds all of that into how teams work rather than inspecting it in afterward. That leader is you. You will work alongside a Senior DevSecOps & Platform Engineering Lead who owns the delivery pipeline and an Enterprise Solution Architect who owns the designs. You own the organization that turns those designs into shipped, tested, production software. What You'll Own The engineering organization. Lead multiple cross-functional development teams across modern and legacy platforms, flexing team size and composition as workflows through intake. Teams form, deliver, and re-form around the work. You make that fluid instead of chaotic. Delivery you put your name on. Commit to scope, level of effort, and timelines in executable plans, then hit them. When you cannot, say so early, with a recovery plan, before the customer discovers it. A quality system, not a QA gate. Engineer quality into how teams work: definition of done that includes full automated testing, code review that catches problems, and metrics that surface risk early. The outcomes that prove it: zero escaped critical defects, defect detection above 95% before UAT, and critical fixes inside three days. Test automation as a craft. Build the discipline where every feature ships with complete positive and negative automated coverage, and the regression suite becomes the safety net the customer trusts enough to focus UAT on new functionality only. The monthly release drumbeat. Production value ships every 30 days or faster, release after release, without burning the team down to do it. Dual-stack engineering. Run modern configuration-first platform development and legacy sustainment side by side, including the warranty on everything your teams release. Engineering standards that outlast you. Set and enforce the bar for code quality, review, documentation, and definition of done across every tea

Skills and categories