Software Delivery Lead

Role Overview

The Software Delivery Lead is responsible for delivery predictability, readiness discipline, and execution orchestration for complex, embedded, and regulated software programs. This role does not include people management or technical design authority. Instead, it focuses on ensuring that software work starts ready, progresses predictably, risks are surfaced early, and delivery trade-offs are framed clearly for decision-making.

Key Responsibilities

Delivery Orchestration & Predictability

• Own planning and delivery for assigned software programs
• Define and enforce readiness criteria before execution begins
• Track execution against milestones and commitments
• Use delivery indicators and milestone confidence signals to surface risks early
• Identify delivery risks, dependencies, and constraint violations proactively
• Experience managing delivery in environments with both iterative and milestone-driven work

Status & Planning Coordination

• Serve as the primary point of contact for software delivery status, planning coordination, and cross-functional dependencies
• Consolidate delivery inputs into clear, leadership-ready updates
• Create dashboards to communicate delivery status, progress and risks
• Ensure consistent delivery messaging across project and program forums

Scope, Resource & Budget Trade-off Management

• Lead structured scope change impact assessments across schedule, capacity, cost, dependencies, and risk
• Support delivery-level resource planning and identify capacity risks early
• Track software delivery budget and spend at the project or program level
• Frame trade-off options and support commitment resets when required

Cross-Functional Coordination

• Coordinate dependencies across software, hardware, systems, quality, regulatory, and operations teams
• Remove blockers or escalate when resolution exceeds team-level authority
• Support one or more projects in parallel, depending on size and complexity

Role Boundaries

This role owns delivery orchestration and readiness discipline, execution tracking and delivery predictability, delivery risk identification and escalation, cross-functional coordination and dependency management, and delivery-level resource and budget visibility. This role does NOT own people management or performance management, software architecture or technical design authority, formal technical or regulatory approval or sign-off, cost center ownership or financial approvals, or tool administration or Scrum-only ceremony ownership.

Authority & Leadership Model

The Senior Software Delivery Lead leads delivery orchestration, readiness, and cross-functional coordination. Final trade-off decisions when scope, schedule, risk, and quality conflict remain with senior leadership. Strong facilitation and communication skills, with a proven ability to lead through ambiguity. Demonstrated ability to influence without authority and coordinate across stakeholder groups.

Required Qualifications

• Bachelor's Degree or Equivalent years of directly related experience (or high school +13 yrs.; Assoc.+9 yrs.; M.S.+2 yrs.; PhD+0 yrs.)
• The ability to fluently read, write, understand, and communicate in English
• 5 Years of Relevant Experience

Preferred Qualifications

• 5+ years as an embedded software developer
• Delivery or program certifications such as PMP, SAFe, or equivalent
• Experience supporting multiple concurrent programs in regulated environments
• 8+ years of experience in software delivery, technical program management, or delivery leadership
• Experience delivering embedded and/or regulated software, including hardware-software dependencies
• Demonstrated ability to lead through influence without direct authority
• Strong executive-level communication and stakeholder management skills
• Experience with delivery and planning tools such as Azure DevOps, Jira, Microsoft Project, or Planner
• Strong understanding of the software development life cycle and working with technical teams

What Success Looks Like

• Predictable software delivery with fewer late surprises
• Clear readiness before execution begins
• Early visibility into schedule, capacity, and budget risks
• Reduced coordination and status burden on Software Leads
• Sustainable execution across multiple parallel programs