IT Project Manager

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Hiring at this level is hard because the work requires steady operational control instead of basic task tracking. Good candidates take pushback from engineers and vendors, adjust the schedule, and keep the team aligned without losing trust. They can also turn technical constraints into clear budget terms while keeping delivery on track. Most applicants just update a timeline, but hiring panels often overlook the real difference between passive coordinators and the people who can sit through a tense scope review, hear what is actually going wrong, and fix the plan before the next sprint.

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.

16 Competency Questions

1 of 16

  1. Discipline

    Project Governance & Delivery Management

  2. Job requirement

    Agile Delivery & Stakeholder Engagement

    Facilitates agile ceremonies, translates business requirements into prioritized user stories, and manages communication cadences.

  3. Expected at Mid

    Mid PMs independently run agile workflows and bridge business/technical communication, ensuring continuous alignment without escalation.

Interview round: Hiring Manager Technical

Describe a recent initiative where you coordinated iterative delivery cycles with business partners and technical teams.

Positive indicators

  • Describes prioritization framework clearly
  • Mentions regular cadence for updates/reviews
  • Ties deliverables to business value
  • References measurable satisfaction metrics

Negative indicators

  • Focuses only on task completion
  • No mention of backlog prioritization
  • Ad-hoc communication with stakeholders
  • Confuses delivery velocity with business value

11 Attitude Questions

1 of 11

Active Listening

The deliberate cognitive and behavioral practice of fully concentrating on, comprehending, and validating stakeholder communications—both explicit and implicit—before formulating responses, to ensure accurate requirement capture, mitigate misalignment risks, and foster psychological safety across technical, operational, and business domains.

Interview round: Recruiter Screen

How would you approach a kickoff meeting with a new vendor and internal operations team to ensure you capture all potential integration bottlenecks before finalizing the project charter?

Positive indicators

  • Outlines structured questioning strategy for integration discovery
  • Emphasizes verbatim documentation of constraints
  • Maps dependencies before charter finalization
  • Aligns handoff criteria to mitigate bottleneck risks

Negative indicators

  • Rushes through kickoff without probing integration details
  • Fails to document constraints during initial meetings
  • Finalizes charter without addressing dependency risks
  • Leaves handoff criteria undefined or ambiguous

Supporting Evaluation

How candidates earn the selection conversation

The goal is to reduce effort for everyone by collecting more useful signal before adding more interviews. Lightweight application prompts and structured screens help the panel focus live 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 3

Application Screen: Video Response

Describe how you would communicate a critical path delay caused by a vendor to non-technical executive sponsors who demand an immediate launch. What specific information do you share, and how do you frame the trade-offs?

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 concurrent IT initiatives, aligning technical timelines with operational constraints.
Leads public-sector procurement processes, evaluates vendor bids, and tracks contractual deliverables.
Coordinates pilot testing, API integration QA, and phased deployment of hardware or software.
Monitors project financials, reconciles data against funding sources, and tracks system performance metrics.

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

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

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

Does the resume show relevant prior work experience?

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

Walk us through your approach to managing multiple concurrent IT projects or a single complex system rollout, specifically focusing on how you align vendor deliverables with internal operational constraints and negotiate minor scope changes.

Format

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

Audience

IT Delivery Leadership and Cross-Functional Operations Leads

What to prepare

  • 3-5 slides outlining a past project retrospective or a structured hypothetical scenario
  • A brief narrative on how you handled vendor SLAs, internal constraints, and scope adjustments

Deliverables

  • A concise deck and verbal walkthrough of your stakeholder and vendor alignment strategy

Ground rules

  • Focus on your narrative and decision-making process, not on building a new project plan
  • You may anonymize past projects or use a hypothetical scenario if real work is confidential
  • Slides should support your discussion, not replace it

Scoring anchors

Exceeds
Presents a nuanced, adaptable approach to multi-project coordination, clearly articulating how they negotiate scope, manage vendor expectations, and maintain operational alignment under competing constraints.
Meets
Walks through a structured approach to managing concurrent projects, identifies key stakeholder touchpoints, and explains a reasonable process for scope adjustments and vendor alignment.
Below
Relies on generic project management platitudes, fails to address vendor/internal constraint friction, or proposes rigid processes that ignore real-world operational realities.

Response time

20 min

Positive indicators

  • Frames the problem by mapping vendor capabilities to internal operational windows
  • Demonstrates a clear process for evaluating and approving minor scope changes
  • Articulates how they communicate trade-offs to both technical and non-technical stakeholders
  • Balances agile flexibility with structured delivery milestones

Negative indicators

  • Presents a rigid, one-size-fits-all methodology without adapting to stakeholder needs
  • Fails to address how they handle conflicting vendor SLAs or operational constraints
  • Avoids discussing the reality of scope creep or how they push back on unrealistic requests
  • Over-indexes on tool features rather than stakeholder communication and alignment

Work Simulation Scenario

Scenario. You are managing a phased rollout of a multi-modal payment tokenization system across three transit agencies. A critical third-party API partner is threatening to miss the upcoming sprint deadline due to unexpected security compliance reviews. You must facilitate a tradeoff discussion to decide whether to delay the release, adjust the phase scope, or implement a temporary technical workaround.

Problem to solve. Guide a multi-party decision that balances security compliance, vendor deliverables, and agency service commitments, then document the agreed path forward.

Format

cross-functional-decision · 40 min · ~2 hr prep

Success criteria

  • Surfaces hidden dependencies and compliance risks without biasing the group toward a single solution
  • Drives a structured tradeoff discussion that respects both security mandates and vendor SLAs
  • Facilitates a clear decision with defined ownership, rollback criteria, and communication next steps

What to review beforehand

  • Review the current sprint backlog, tokenization phase gates, and vendor SLA penalty clauses
  • Understand the security compliance review workflow and standard workaround approval thresholds

Ground rules

  • You are facilitating the decision, not making unilateral technical or compliance rulings
  • Ensure each party has equal opportunity to present constraints and risk assessments

Roles in scenario

Internal Security Lead (cross_functional_partner, played by cross_functional)

Motivation. Ensure zero compliance violations and protect the agency's data governance standards.

Constraints

  • Regulatory audit cycle begins in two weeks
  • Company policy forbids bypassing penetration testing for live payment APIs

Tensions to introduce

  • Reject any workaround that lacks formal audit documentation
  • Highlight that a delay is preferable to a compliance breach
  • Question the vendor's readiness if they push for a rushed deployment

In-character guidance

  • Maintain a risk-aware, compliance-first stance throughout the discussion
  • Answer technical compliance questions directly when asked
  • Acknowledge tradeoff proposals that include formal audit pathways

Do not

  • Do not dictate the final project timeline
  • Do not volunteer alternative security architectures unless asked
  • Do not dismiss vendor constraints out of hand without hearing their technical rationale

Vendor Technical Lead (external_partner, played by peer)

Motivation. Deliver the sprint milestone on time to avoid financial penalties and maintain partnership trust.

Constraints

  • Engineering team is already allocated to the next sprint
  • Compliance review queue has a known 7-day backlog

Tensions to introduce

  • Argue that the proposed workaround has been safely used in other jurisdictions
  • Warn that a full sprint delay will trigger contractual penalty clauses
  • Push for parallel testing to compress the timeline

In-character guidance

  • Advocate firmly for timeline preservation while acknowledging security realities
  • Provide honest technical details about the workaround's limitations when questioned
  • Stay collaborative and avoid blame-shifting

Do not

  • Do not agree to bypass security protocols without explicit candidate facilitation
  • Do not unilaterally commit to new delivery dates outside the candidate's decision framework
  • Do not withhold known integration dependencies if asked

Scoring anchors

Exceeds
Orchestrates a highly structured tradeoff analysis, surfaces non-obvious dependencies, and drives a consensus decision with explicit risk mitigation, ownership, and communication protocols.
Meets
Facilitates a balanced discussion, identifies key tradeoffs, and guides the group to a documented decision with reasonable next steps.
Below
Fails to manage stakeholder tensions, accepts unverified assumptions, or produces an ambiguous outcome lacking clear ownership or risk controls.

Response time

40 min

Positive indicators

  • Structures the discussion around explicit tradeoffs: compliance risk, timeline impact, and vendor capacity
  • Asks probing questions to uncover hidden dependencies in both the security workflow and vendor engineering queue
  • Synthesizes competing constraints into a clear, actionable decision with defined rollback criteria
  • Maintains professional boundaries by preventing either party from dictating terms without mutual agreement

Negative indicators

  • Allows one stakeholder to dominate the conversation without balancing technical and compliance perspectives
  • Rushes to a compromise without validating the technical feasibility or compliance implications
  • Fails to establish clear ownership and next steps for the chosen path forward
  • Uses vague language that leaves rollback criteria or escalation paths ambiguous

Progression Framework

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

Project Governance & Delivery Management

5 competencies

CompetencyJuniorMidSeniorPrincipal
Agile Delivery & Stakeholder Engagement

Participates in sprint ceremonies, documents stakeholder feedback, and maintains backlog hygiene under guidance.

Facilitates agile ceremonies, translates business requirements into prioritized user stories, and manages communication cadences.

Scales agile frameworks across multiple teams, negotiates conflicting stakeholder priorities, and establishes continuous feedback loops.

Architects enterprise agile transformations, aligns executive vision with delivery outcomes, and mentors senior delivery leaders to scale continuous delivery practices.

Project Planning & Scheduling

Executes predefined schedules, updates task trackers, and flags basic timeline deviations to supervisors.

Creates detailed WBS and critical path schedules, manages cross-team dependencies, and adjusts plans based on scope changes.

Designs multi-phase delivery roadmaps, optimizes resource utilization across programs, and establishes organizational planning standards.

Defines enterprise portfolio planning frameworks, aligns strategic initiatives with capacity modeling, and drives predictive scheduling methodologies across the delivery ecosystem.

Quality Assurance & Testing Oversight

Executes test plans, logs defects in tracking systems, and verifies bug fixes against defined acceptance criteria.

Designs comprehensive test strategies, manages defect triage workflows, and coordinates UAT with business users.

Establishes QA governance frameworks, integrates automated testing into CI/CD pipelines, and drives quality KPIs.

Defines enterprise quality standards, leads zero-defect culture initiatives, and aligns QA strategy with business risk tolerance across delivery pipelines.

Risk Management & Procurement

Maintains risk registers, tracks vendor deliverables against SLAs, and reports on basic compliance requirements.

Conducts qualitative risk assessments, negotiates vendor terms, and implements targeted mitigation strategies.

Develops quantitative risk models, oversees complex multi-vendor contracts, and establishes organizational procurement standards.

Designs enterprise risk governance frameworks, leads strategic vendor partnerships, and optimizes procurement ecosystems to support large-scale IT investments.

Team Leadership & Resource Optimization

Supports team coordination, tracks individual assignments, and assists with onboarding and knowledge transfer processes.

Directs cross-functional teams, resolves resource bottlenecks, and implements performance tracking mechanisms.

Builds high-performing delivery teams, optimizes capacity across portfolios, and establishes leadership development programs.

Shapes organizational talent strategy, drives cross-departmental resource sharing, and cultivates executive leadership pipelines to sustain delivery capability scaling.

Systems Architecture & Compliance Integration

2 competencies

CompetencyJuniorMidSeniorPrincipal
Data Governance & Compliance Integration

Maintains data dictionaries, assists with compliance audit checklists, and monitors basic access controls and security logs.

Implements data classification schemes, conducts compliance audits, and coordinates security remediation efforts across teams.

Establishes enterprise data governance frameworks, manages cross-jurisdictional compliance requirements, and integrates privacy-by-design principles.

Defines global data strategy, leads regulatory advocacy initiatives, and architects zero-trust compliance ecosystems for enterprise-scale IT delivery.

Systems Architecture Oversight & Technical Design

Documents system configurations, assists in architecture diagramming, and tracks technical debt items in backlog tools.

Evaluates solution designs against architectural guidelines, facilitates technical review boards, and manages integration point specifications.

Defines target state architectures, leads cross-system design reviews, and establishes technical governance boards and standards.

Architects enterprise technology roadmaps, drives strategic innovation adoption, and aligns technical strategy with business transformation goals across the IT portfolio.