Senior Delivery Manager (Remote)

Other Jobs To Apply

<p><b><span style="font-size:14px">Progressive Leasing </span></b><span style="font-size:14px">is a leading provider of in-store and e-commerce lease-to-own solutions. With more than 20 years in FinTech, we’ve grown from start-up to industry leader by innovating, simplifying, and valuing people. We are a subsidiary of PROG Holdings (NYSE: PRG), a FinTech holding company with three business segments: Progressive Leasing, Purchasing Power (a leading employee purchase program for consumer products and services using payroll deduction), and Four, a Buy Now Pay Later (BNPL) platform.</span></p><p> </p><p><span>We are currently hiring a<b> Senior Delivery Manager</b> to help grow our company and ensure our mission is achieved!  </span>  </p><p></p><p><i>This role is work from home position and can be performed remotely anywhere in the continental US or in one of our corporate locations in Utah, Arizona or Colorado</i></p><p></p><p><i>Employee Value Proposition (EVP)<b>:</b> PROG is dedicated to providing people with opportunity; opportunity for inclusive collaboration, opportunity for innovation, and opportunity for development.</i></p><p></p><p><b>WE ARE:</b> Prog Tech is the driving force behind our company’s technological evolution. We are passionate problem solvers and technical experts, working together to deliver impactful solutions. We pride ourselves on craftsmanship, continuous improvement, and collaboration. Our culture encourages experimentation, learning from failures, and delivering meaningful outcomes.</p><p></p><p><b>YOU ARE: </b></p><p>A technically fluent delivery manager who operates at the team level — close to the work, the risk, and the engineers doing both. You understand the full software development lifecycle, from planning through delivery. You build systems that create predictability, surface risk early, and protect delivery integrity. You influence engineers, product managers, and stakeholders through structure, data, and clear framing.</p><p>You are comfortable operating in ambiguity. When dependencies slip, scope pressure mounts, or execution variability surfaces, your instinct is to model the impact, structure the options, and reset expectations with clarity.</p><p>You are equally at home in flow-based, service-oriented environments where work is continuous and interrupt-driven as you are in iteration-based teams. You understand that delivery discipline looks different depending on the team operating model, and you adapt your approach accordingly without losing rigor.</p><p>You treat AI tools as force multipliers for delivery work by using them to draft communications, model trade-offs, accelerate backlog synthesis, and generate operational artifacts faster than manual methods allow. You have a point of view on where AI augments delivery rigor versus where it creates false confidence, and you apply that judgment deliberately.</p><p></p><p><b>YOUR DAY-TO-DAY:</b></p><p></p><p><b>Delivery System Operations</b></p><ul><li><p>Maintain and improve delivery visibility across complex, dependency-heavy work by tracking cross-team blockers, integration risks, and upstream/downstream exposure</p></li><li><p>Model the impact of scope changes, timeline shifts, and capacity constraints by presenting structured options with clear trade-offs to decision-makers</p></li><li><p>Drive backlog readiness discipline, ensuring work entering execution is well-defined and dependency-mapped before it starts</p></li><li><p>Identify and actively manage delivery risk through surfacing issues proactively, quantifying impact, and framing resolution paths for engineering and product leadership</p></li><li><p>Maintain and improve delivery operating norms that reduce rework, carryover, and execution variability over time</p></li><li><p>Leverage AI tooling to accelerate operational work, including status synthesis, risk narrative generation, and backlog readiness summarization, while maintaining human judgment on prioritization and stakeholder framing decisions.</p></li></ul><p></p><p><b>Influence and Stakeholder Management</b></p><ul><li><p>Influence engineer and product manager behavior through structure and data by driving accountability and shared clarity on delivery commitments</p></li><li><p>Frame delivery trade-offs clearly by presenting structured options with explicit implications on timeline, quality, and capacity</p></li><li><p>Partner with Product Managers to enforce readiness standards and protect delivery integrity when scope pressure mounts</p></li><li><p>Communicate delivery feasibility and confidence clearly to the engineering team and partnering Project Managers by providing early warning when assumptions change and surfacing recovery options when they do</p></li><li><p>Socialize production release schedules in advance with the development team, Product Manager, and relevant change advisory processes ensuring the team is prepared for releases</p></li></ul><p></p><p><b>Technical Fluency</b></p><ul><li><p>Maintain working fluency in the technical systems your team supports through a solid  understanding of integration surfaces, API dependencies, and release risk in context</p></li><li><p>Coordinate across engineering, QE, architecture, and platform teams to manage cross-functional dependencies and resolve blockers at the right level</p></li><li><p>Apply delivery metrics (i.e. cycle time, throughput, carryover, predictability) as operational signals that drive structural change in how the team works</p></li></ul><p></p><p><b>Service-Oriented Team Operations</b></p><ul><li><p>Manage a Kanban-based delivery system for a team handling a mix of planned work and high-priority operational demand</p></li><li><p>Balance intake discipline with responsiveness by maintaining flow efficiency while protecting planned delivery commitments from reactive work pressure</p></li><li><p>Model WIP impact and context-switching costs to protect team throughput and focus</p></li><li><p>Maintain and improve intake and triage processes that bring structure to interrupt-driven work without creating bureaucratic overhead</p></li><li><p>Monitor Kanban flow metrics (i.e. lead time, cycle time, and queue depth) to identify bottlenecks and maintain healthy throughput</p></li><li><p>Coordinate with dependent teams and platform consumers to maintain demand visibility and set clear expectations proactively</p></li></ul><p></p><p><b>Iteration-Based Team Operations</b></p><ul><li><p>Manage sprint cadence and iteration health across one or more engineering teams with a focus on commitment reliability and sprint goal integrity</p></li><li><p>Enforce sprint entry discipline by ensuring stories meet sizing and readiness standards before planning begins, and holding the line when they don’t</p></li><li><p>Track and improve sprint predictability using carryover, velocity trends, and planning accuracy as signals to adjust how the team operates</p></li><li><p>Manage scope pressure during active sprints through modeling the impact of additions or changes and presenting clear trade-off options to the Product Manager before commitments shift</p></li><li><p>Maintain cross-sprint dependency visibility across teams or workstreams, identifying what is at risk and when</p></li><li><p>Run retrospectives as structured operational reviews by identifying systemic delivery friction and driving follow-through on changes</p></li></ul><p></p><p><b>YOU’LL BRING:</b></p><ul><li><p>5 to 7 years of delivery management experience embedded within software engineering teams in a fintech or similarly regulated, technically complex environment</p></li><li><p>Demonstrated ability to influence engineer and product manager behavior through structure, data, and clear framing</p></li><li><p>Proven experience building or materially improving delivery systems: reducing carryover, improving commitment reliability, or increasing planning quality through structural changes</p></li><li><p>Experience modeling delivery trade-offs and presenting structured options to leadership</p></li><li><p>Deep SDLC fluency, including integration complexity, release management, dependency modeling, and cross-team coordination</p></li><li><p>Strong working knowledge of Jira for dependency tracking, delivery modeling, and operational insight</p></li><li><p>Comfort operating in API-heavy, <span style="overflow-wrap: break-word; display: inline; text-decoration: inherit; hyphens: auto;">integration-dependent</span> backend environments where delivery risk lives in the connections between systems</p></li><li><p>Prior experience managing Kanban-based teams in service-oriented or platform engineering environments</p></li><li><p>Demonstrated use of flow metrics (i.e. lead time, cycle time, WIP) as day-to-day operational tools for managing team health and throughput</p></li><li><p>Demonstrated use of AI-assisted tooling (LLMs, AI-augmented Jira workflows, or similar) to improve delivery throughput, reduce coordination overhead, or accelerate artifact generation with the discernment to know when AI output requires human review before it reaches stakeholders.</p></li><li><p>Calm, structured approach to ambiguity and able to reset expectations and protect delivery integrity when plans change</p></li><li><p>Strong written and verbal communication skills, including the ability to frame engineering consequences clearly for non-technical stakeholders</p></li><li><p>Bachelor’s degree or equivalent experience</p></li></ul><p></p><p><b>YOU MIGHT ALSO HAVE:</b></p><ul><li><p>Prior experience managing sprint-based teams, including planning discipline, Definition of Ready enforcement, and iteration health management</p></li><li><p>Working knowledge of CI/CD pipelines, deployment infrastructure, or cloud services sufficiently enough to understand release risk and coordinate across platform teams</p></li><li><p>Experience coordinating across both iterative (sprint-based) and continuous-flow (Kanban) teams within the same organization</p></li><li><p>Familiarity with ServiceNow or similar change management tooling in a governed release environment</p></li><li><p>Experience supporting offshore or distributed engineering teams with uneven execution maturity</p></li><li><p>Agile, Scrum, or Kanban certification (CSM, PSM, KMP, or equivalent)</p></li></ul><div><div><div><p></p></div></div></div><p><b>WE OFFER:    </b></p><ul><li><p>Competitive Compensation</p></li><li><p>Full Health Benefits; <span style="overflow-wrap: break-word; display: inline; text-decoration: inherit; hyphens: auto;">Medical/Dental/Vision/Life</span> Insurance + Paid Parental Leave</p></li><li><p>Company Matched 401k</p></li><li><p>Paid Time Off + Paid Holidays + Paid Volunteer Hours</p></li><li><p>Employee Resource Groups (Black Inclusion Group, Women in Leadership, PRIDE, Adelante)</p></li><li><p>Employee Stock Purchase Program</p></li><li><p>Tuition Reimbursement</p></li><li><p>Charitable Gift Matching</p></li><li><p>Job required equipment and services</p></li></ul><p style="text-align:inherit"></p><p style="text-align:left"><i>Progressive Leasing welcomes and encourages diversity in the workplace. We do not discriminate in any aspect of employment on the basis of race, color, religion, national origin, ancestry, gender, sexual orientation, gender identity and/or expression, age, veteran status, disability, or any other characteristic protected by federal, state, or local employment discrimination laws where Progressive Leasing does business.</i></p>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...