Ensure delivery-level stakeholder alignment — keeping business, product, and technology partners informed of program status, risks, trade-offs, and decisions that affect commitments; proactively building relationships with subject matter experts and decision-makers outside your immediate area
Own full program delivery across the entire lifecycle — discovery, requirements, scope, schedule, resources, testing, quality, release, and costs — for complex, cross-functional initiatives; accountable for outcomes, not just progress updates
Drive the delivery roadmap with a 6-to-12-month planning horizon — translate product priorities into phased delivery plans, set milestones, stage early deliverables to address long-lead-time work, and proactively identify and influence upstream and downstream dependencies to protect delivery timelines
Use program communications as a deliberate tool — to drive alignment, influence decisions, surface risks early, and secure leadership support; anticipate misalignments and conflicts before they block progress, working proactively to resolve them
Drive teams toward pragmatic decisions — cut through ambiguity, escalate when needed, and ensure the program keeps moving forward
Engage actively in technical design reviews — contribute to trade-off decisions by articulating cross-functional technical and business impacts, and ensure designs serve both near-term delivery and long-term architectural needs. Use retrospectives, RCAs, and team learnings to drive continuous improvements in production stability and squad delivery efficiency; partner with product management to interpret success-metrics and use outcomes to inform roadmap adjustments and delivery decisions
Hold partners and stakeholders at all levels accountable — not just internal team members — with clear expectations, feasibility assessments, and consistent follow-through
Partner with product management to translate requirements into actionable technical plans — ensuring scope, dependencies, and acceptance criteria are clearly understood by engineering teams
Requirements
4+ years’ experience in program management or related program delivery experience
A bachelor’s degree (in Computer Science, Engineering or related technical field is preferred but not required)
Comfort in fast-paced, ambiguous environments, with a natural curiosity and bias toward bringing order and forward momentum.
Fluency in Agile delivery methodologies and modern SDLC practices — you understand how software gets built and can work fluidly within iterative, fast-moving engineering teams
Clear and effective written and verbal communication and strong interpersonal skills
Strong working knowledge of Supply Chain and warehouse management systems (e.g. WMS, core Supply Chain services, Cloud Technologies) or other Retail systems — required; component-level understanding of how systems interact is strongly preferred
Experience managing large-scale program workstreams as part of a larger program
Effective interpersonal influence, collaboration and listening skills with experience working across many levels of an organization
Rigorous attention to detail and follow through
Dependency-mapping program management tools such as Microsoft Project, Smart Sheet etc.
Familiarity with Atlassian tools and A/I toolsets
Experience contributing to technical design reviews and supporting engineering trade-off decisions by representing customer and business impact
Ability to troubleshoot systems and query underlying data layers to identify operational risks and insights.