ServiceNowExpert-built kit

Delivery Lead / Project Manager

Unblocks cross-vendor dependencies, updates project schedules, and facilitates daily standups and sprint retrospectives.

Buy this kit · $29.99Preview questions

Interview content for Program Delivery Lead / Program Manager

25
What to ask. Competency and attitude questions, assigned to the right round.
150
What to listen for. Positive and negative indicators, per question.
9
What the hire must do. Capabilities with expected proficiency at each level.

Look inside: one question, as it appears in the kit

Pick the level you’re hiring. The sample changes with the level you select.

Round 2 · Hiring Manager: Core Delivery & Execution18 competency questions

Agile Delivery & Operational Control

Agile Delivery Execution

Coordinates cross-team dependencies and aligns sprint cadences across multiple initiatives to maintain synchronized delivery.

Expected at Program Delivery Lead / Program Manager

Sample competency question

Walk me through a recent program where you had to align multiple teams running different sprint cycles. How did you structure the planning and synchronization?

Ask once, as written, then allow silence. A helpful rephrase may hand the candidate the answer.

Positive indicators

  • References synchronized planning events
  • Cites specific unblocking timelines
  • Emphasizes decision-focused ceremonies

Negative indicators

  • Describes passive status reporting
  • Admits to letting teams operate in silos
  • Lacks concrete synchronization tactics

Program delivery requires synchronizing multiple workstreams where misalignment causes cascading delays; advanced proficiency ensures proactive dependency resolution within the <5 day success indicator.

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Picking a delivery lead for multi-track platform work has never been about finding a perfect scheduler. It comes down to finding someone who can push back when stakeholders get loud while keeping five teams moving without burning them out. I once sat through an interview where a candidate mapped out complex dependencies perfectly but completely stalled when I asked how he handled a department head trying to shove urgent work into an active sprint. The right person tracks what actually moves the business forward instead of chasing empty numbers. They guard team capacity, keep scope tight, and turn executive pressure into a steady pace the group can actually sustain.

Everything in the download, in the order you’ll use it

Level guides for Delivery Lead / Project Manager, Program Delivery Lead / Program Manager and Delivery Director / Practice Manager.

Before you post

  • 1Ready-to-use job description
  • 2Video screening prompts
  • 8Resume screening criteria

In the room

  • 18Competency interview questions
  • 7Attitude interview questions
  • 1Hands-on work simulations
  • 1Presentation prompts

At the debrief

  • Progression framework
  • Exceeds / Meets / Below anchors for every exercise
  • 3Interview plan with time per round

Core Evaluation

Critical questions for this role

The competency and attitude questions below are where the hiring decision is made. They run in the live interview rounds and are calibrated to the level selected above.

18 Competency Questions

1 of 18

  1. Discipline

    Agile Delivery & Operational Control

  2. Job requirement

    Agile Delivery Execution

    Coordinates cross-team dependencies and aligns sprint cadences across multiple initiatives to maintain synchronized delivery.

  3. Expected at Program Delivery Lead / Program Manager

    Program delivery requires synchronizing multiple workstreams where misalignment causes cascading delays; advanced proficiency ensures proactive dependency resolution within the <5 day success indicator.

Interview round: Hiring Manager: Core Delivery & Execution

Walk me through a recent program where you had to align multiple teams running different sprint cycles. How did you structure the planning and synchronization?

Positive indicators

  • References synchronized planning events
  • Cites specific unblocking timelines
  • Emphasizes decision-focused ceremonies

Negative indicators

  • Describes passive status reporting
  • Admits to letting teams operate in silos
  • Lacks concrete synchronization tactics

7 Attitude Questions

1 of 7

Active Listening

Active listening is the disciplined practice of fully concentrating on, understanding, and responsively engaging with both explicit statements and implicit signals during project interactions. It requires suspending judgment, accurately reflecting content and emotional undertones, identifying underlying constraints or latent interests, and synthesizing diverse inputs to inform strategic decisions, mitigate delivery risks, and cultivate psychological safety across cross-functional teams.

Interview round: Recruiter Screen: Role Fit & Logistics

During a cross-functional alignment meeting, two workstream leads present mutually exclusive timelines for a shared integration. How do you facilitate the discussion?

Positive indicators

  • Mentions creating space for both leads to explain
  • Describes mapping constraints to shared goals
  • Highlights moving from debate to co-created solutions

Negative indicators

  • Imposes a timeline without exploring root causes
  • Allows the meeting to devolve into positional bargaining
  • Fails to document the agreed resolution

Supporting Evaluation

How candidates earn the selection conversation

The goal is to reduce effort for everyone by collecting more useful signals before adding more interviews. Lightweight application prompts and structured screens help your team focus interview time on the candidates most likely to succeed.

Stage 1 · Application

Filter at the door

Runs the moment a candidate hits Submit. Disqualifying answers end the application; everything else is captured for review.

Video-Response Questions

1 of 2

Application Screen: Video Response

You are managing a critical implementation where platform constraints force a delay in the original delivery timeline. The customer’s executive sponsor is pushing for the original launch date despite engineering feedback about necessary stability testing. Describe how you would structure a conversation with this stakeholder to renegotiate the timeline while preserving trust and securing alignment on adjusted acceptance criteria.

Candidate experience

REC
0:42 / 2:00
1Record
2Review
3Submit

Response time

2 min

Format

Recorded video

Stage 2 · Resume Screening

Read the resume against fixed criteria

Reviewers score every application that clears the door against the same criteria. Stronger reviews advance to live interviews; weaker ones are archived without further screening.

Resume Review Criteria

8 criteria
Manages interdependencies across multiple delivery tracks to prevent cascading disruptions and maintains program-level risk registers.
Utilizes forecasting models and agile scaling frameworks to optimize resource allocation and synchronize delivery cadences across parallel workstreams.
Ensures program-wide adherence to regulatory, data privacy, and platform best practices through structured audit preparation and quality gate standardization.
Translates executive objectives into prioritized program epics, manages cross-workstream backlogs, and facilitates steering committee decision-making.

Does the resume show relevant prior work experience?

Is the resume complete, well-organized, and free from formatting, spelling, and grammar mistakes?

Does the resume indicate required academic credentials, relevant certifications, or necessary training?

Does the cover letter or personal statement convey clear relevance and familiarity with the job?

Stage 3 · During Interviews

Where the hire is decided

Interview rounds use the competency and attitude questions outlined above, then add tests, work simulations, and presentations that reveal deeper evidence about how the candidate thinks and works.

Presentation Prompt

Prepare a short deck on a past or hypothetical multi-track program where cross-workstream dependencies created chronic bottlenecks. Walk us through your approach to mapping those dependencies, synchronizing delivery cadences, and establishing an orchestration framework to prevent future disruptions.

Format

deck-and-walkthrough · 20 min · ~2 hr prep

Audience

Program Management Office, Engineering Directors, Client Success Leadership

What to prepare

  • 3-5 slides outlining the program context, your dependency mapping approach, synchronization strategy, and recommended governance framework

Deliverables

  • A short deck and verbal walkthrough covering root cause analysis, cross-track coordination tactics, escalation protocols, and measurable outcomes

Ground rules

  • You may use anonymized past program data or construct a fictionalized model based on the prompt
  • Do not produce net-new strategic artifacts beyond the 3-5 slide analysis
  • Focus on reasoning, trade-offs, and how you would drive alignment across siloed teams

Scoring anchors

Exceeds
Designs a predictive dependency model, establishes clear cross-track decision rights, integrates AI/augmented tracking for early warning, and aligns technical cadences with business value delivery while maintaining compliance.
Meets
Identifies key bottlenecks, proposes a realistic synchronization cadence, defines clear handoff protocols, and outlines basic escalation paths.
Below
Offers superficial status-tracking solutions, ignores cross-workstream impact, lacks a clear governance structure, or fails to address root cause dependencies.

Response time

20 min

Positive indicators

  • Maps dependencies explicitly using impact matrices or shared release calendars
  • Proposes structured governance that balances local track optimizations with overall program velocity
  • Defines clear escalation paths and decision rights for cross-workstream conflicts
  • Asks clarifying questions about current tooling, communication gaps, and compliance realities

Negative indicators

  • Treats tracks in isolation and recommends purely technical fixes without addressing process gaps
  • Fails to define escalation paths or cross-functional decision rights
  • Overlooks platform constraint or compliance realities in the synchronization plan
  • Presents a rigid framework without discussing trade-offs or adoption challenges

Work Simulation Scenario

Scenario. You are overseeing a multi-track program spanning ITSM, ITOM, and CSM workstreams. The upcoming maintenance window requires synchronizing discovery scans, change deployments, and portal updates to prevent platform disruption. You must drive a 1:1 conversation with the IT Operations Director, who is pushing back on your proposed schedule due to competing infrastructure upgrades. Your goal is to surface hidden dependencies, negotiate a phased approach, and secure commitment to a unified window that prevents system degradation.

Problem to solve. Align conflicting operational priorities into a synchronized delivery cadence that respects infrastructure constraints, prevents cross-subdomain disruption, and maintains program momentum.

Format

stakeholder-roleplay · 45 min · ~2 hr prep

Success criteria

  • Surface and map the true impact of overlapping discovery and change windows
  • Negotiate a phased or staggered execution plan that respects infrastructure limits
  • Secure explicit commitment to a unified maintenance window with clear escalation triggers

What to review beforehand

  • ServiceNow ITOM discovery scheduling and performance impact guidelines
  • Cross-workstream dependency mapping frameworks
  • Capacity forecasting and resource allocation principles for parallel tracks

Ground rules

  • Drive the conversation toward alignment, not debate
  • Focus on infrastructure constraints, risk mitigation, and phased execution
  • Do not draft a new schedule; negotiate verbal commitments and documented next steps
  • Escalate to steering committee only if operational risk cannot be contained

Roles in scenario

IT Operations Director (skeptical_stakeholder, played by leadership)

Motivation. Protect platform stability and prevent performance degradation during a critical infrastructure upgrade cycle.

Constraints

  • Legacy network switches require a 4-hour maintenance window next week
  • ITOM discovery scans historically cause 15-20% CPU spikes on production nodes
  • Your team is already at 90% capacity managing the core upgrade

Tensions to introduce

  • Reject the proposed simultaneous discovery and change deployment window
  • Insist that ITSM portal updates be delayed until post-upgrade stabilization
  • Question the accuracy of the candidate's capacity forecasting model

In-character guidance

  • Answer honestly about legacy system fragility and team bandwidth when asked
  • Maintain a firm but collaborative stance focused on operational risk
  • Remain open to staggered windows if performance impact is mitigated

Do not

  • Do not volunteer the optimal schedule or solve the alignment problem
  • Do not withhold information about CPU thresholds or legacy constraints
  • Do not escalate to executive leadership unless the candidate ignores risk data

Scoring anchors

Exceeds
Systematically quantifies cross-subdomain impact, designs a phased window that isolates high-risk activities, and secures explicit operational commitments with clear rollback triggers. Demonstrates exceptional capacity forecasting and stakeholder alignment under infrastructure constraints.
Meets
Identifies the core scheduling conflict, proposes a realistic staggered window, and validates key performance thresholds. Maintains clear communication and respects operational boundaries, though risk mitigation framing may lack granular detail.
Below
Insists on simultaneous execution, ignores legacy system fragility, or relies on vague capacity estimates. Fails to secure explicit commitments, avoids addressing rollback protocols, and leaves the alignment session unresolved.

Response time

45 min

Positive indicators

  • Asks targeted questions to quantify discovery scan impact and legacy system thresholds
  • Proposes a staggered or phased execution window that isolates high-risk activities
  • Validates operational constraints before committing to a synchronized cadence
  • Articulates clear escalation triggers and rollback protocols for the unified window
  • Maintains psychological safety while negotiating infrastructure boundaries

Negative indicators

  • Pushes for simultaneous execution despite documented performance risks
  • Fails to probe hidden dependencies between ITOM discovery and ITSM/CSM portals
  • Relies on generic capacity assumptions instead of validating real-time constraints
  • Avoids direct answers on rollback triggers or escalation paths
  • Allows the conversation to stall without securing explicit operational commitments

Progression Framework

This table shows how competencies evolve across experience levels. Each cell shows competency at that level.

Agile Delivery & Operational Control

5 competencies

CompetencyDelivery Lead / Project ManagerProgram Delivery Lead / Program ManagerDelivery Director / Practice Manager
Agile Delivery Execution

Facilitates daily stand-ups, sprint planning, and backlog grooming to ensure predictable task completion and team alignment.

Coordinates cross-team dependencies and aligns sprint cadences across multiple initiatives to maintain synchronized delivery.

Establishes enterprise agile frameworks, optimizes portfolio throughput, and standardizes delivery practices across the organization.

Delivery Reporting & Metrics

Generates sprint burndown charts, velocity reports, and defect metrics to inform team retrospectives and adjustments.

Aggregates multi-project KPIs, identifies systemic delivery bottlenecks, and produces portfolio-level performance dashboards.

Defines enterprise delivery KPIs, presents executive performance reviews, and drives data-informed operational strategy.

Release & Quality Governance

Coordinates release schedules, executes pre-deployment checklists, and tracks defect resolution for assigned deliverables.

Standardizes release calendars across teams, manages rollback protocols, and enforces cross-initiative quality metrics.

Architects enterprise release governance frameworks, mandates automated quality thresholds, and minimizes production risk at scale.

Resource & Capacity Planning

Monitors individual task assignments and adjusts sprint allocations based on real-time availability and skill sets.

Pools resources across initiatives, forecasts capacity constraints, and implements cross-training to balance demand.

Aligns workforce planning with strategic roadmaps, optimizes budget-to-capacity ratios, and drives hiring or contracting strategies.

Scope & Change Management

Documents requirements, tracks change requests, and communicates scope adjustments to the immediate delivery team.

Evaluates cross-project impact of scope changes, negotiates trade-offs, and maintains baseline alignment across workstreams.

Defines enterprise change control policies, prioritizes strategic pivots, and ensures scope aligns with overarching business objectives.

Platform Integration & Strategic Value

4 competencies

CompetencyDelivery Lead / Project ManagerProgram Delivery Lead / Program ManagerDelivery Director / Practice Manager
AI & Experience Automation

Deploys automation scripts, configures virtual agent intents, and monitors user adoption metrics for targeted workflows.

Scales AI automation across service lines, establishes reuse frameworks, and measures experience impact across departments.

Sets AI adoption strategy, governs ethical automation standards, and aligns automation investments with CX/EX roadmaps.

Business Value & ROI Tracking

Tracks feature adoption, collects stakeholder feedback, and reports on immediate delivery outcomes against project baselines.

Correlates cross-project deliverables to business KPIs, optimizes value streams, and manages benefit realization across initiatives.

Aligns portfolio investments to enterprise strategy, forecasts long-term ROI, and drives value-based prioritization frameworks.

Platform Governance & Compliance

Applies platform guardrails, tracks compliance checklists, and resolves audit findings for assigned delivery workstreams.

Harmonizes compliance requirements across portfolios, implements automated policy checks, and manages cross-program risk registers.

Defines enterprise governance frameworks, ensures regulatory alignment, and oversees platform security posture at organizational scale.

Service Integration & Workflow Orchestration

Maps service dependencies, tracks integration milestones, and resolves cross-team workflow blockers during implementation.

Orchestrates multi-vendor and multi-platform integrations, standardizes handoff protocols, and optimizes end-to-end process flow.

Designs enterprise service architecture alignment, governs cross-domain workflow standards, and ensures ecosystem interoperability at scale.