Electrified Transit Engineering & DeliveryExpert-built kit

Risk Manager

Facilitates risk identification workshops, maps contract risk boundaries, leads safety hazard analysis, and captures operational scenarios across electrification projects.

Buy this kit · $29.99Preview questions

Interview content for Program Risk Lead

23
What to ask. Competency and attitude questions, assigned to the right round.
140
What to listen for. Positive and negative indicators, per question.
5
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 Technical Deep Dive12 competency questions

Risk Analysis & Technical Safety

Quantitative Risk Modeling & Hazard Identification

Integrates cross-project risk data to calibrate models and prioritize systemic technical hazards across portfolios.

Expected at Program Risk Lead

Sample competency question

Walk me through how you approached sizing cost or schedule contingencies for a complex, multi-phase capital program using probabilistic methods.

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

Positive indicators

  • Describes specific distribution choices and calibration steps
  • Links model outputs directly to budget reserve decisions
  • Explains how they validated inputs with technical SMEs
  • Differentiates between aleatory and epistemic uncertainty

Negative indicators

  • Relies solely on flat percentage add-ons or deterministic math
  • Treats model outputs as absolute predictions without ranges
  • Ignores historical project variance when setting baselines
  • Cannot explain the mechanics behind their modeling choices

Requires synthesizing disparate project-level models into a coherent portfolio view, adjusting for systemic biases, and guiding project managers on calibration techniques for high-impact transit deployments.

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Picking a Program Risk Lead for our electrification rollout takes far more than just keeping a risk log updated. You need someone willing to push back to engineering when battery prices jump or charging standards break down. I have seen candidates talk a big game about spotting hazards but completely stumble when asked how they would renegotiate a supplier contract after a missed delivery. That kind of role demands clear communication and a sense of ownership that holds up under strict budget audits.

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

Level guides for Project Risk Manager, Program Risk Lead and Enterprise Risk Director.

Before you post

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

In the room

  • 12Competency interview questions
  • 11Attitude 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.

12 Competency Questions

1 of 12

  1. Discipline

    Risk Analysis & Technical Safety

  2. Job requirement

    Quantitative Risk Modeling & Hazard Identification

    Integrates cross-project risk data to calibrate models and prioritize systemic technical hazards across portfolios.

  3. Expected at Program Risk Lead

    Requires synthesizing disparate project-level models into a coherent portfolio view, adjusting for systemic biases, and guiding project managers on calibration techniques for high-impact transit deployments.

Interview round: Hiring Manager Technical Deep Dive

Walk me through how you approached sizing cost or schedule contingencies for a complex, multi-phase capital program using probabilistic methods.

Positive indicators

  • Describes specific distribution choices and calibration steps
  • Links model outputs directly to budget reserve decisions
  • Explains how they validated inputs with technical SMEs
  • Differentiates between aleatory and epistemic uncertainty

Negative indicators

  • Relies solely on flat percentage add-ons or deterministic math
  • Treats model outputs as absolute predictions without ranges
  • Ignores historical project variance when setting baselines
  • Cannot explain the mechanics behind their modeling choices

11 Attitude Questions

1 of 11

Accountability Mindset

A cognitive and behavioral orientation characterized by taking full ownership of decisions, actions, and outcomes related to risk identification, assessment, and mitigation, while transparently acknowledging errors, facilitating constructive post-incident analysis, and fostering a culture where responsibility is shared rather than deflected.

Interview round: Recruiter Screen & Alignment

A critical risk register entry remains open past its target date, and the assigned workstream owner is blaming external vendor delays. How do you step in to resolve it?

Positive indicators

  • Maps interdependencies to identify actual bottleneck sources
  • Facilitates direct vendor-owner alignment sessions
  • Updates register with documented resolution steps

Negative indicators

  • Accepts vendor blame without independent verification
  • Extends deadlines without adjusting mitigation intensity
  • Allows unilateral closure without cross-functional sign-off

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 3

Application Screen: Video Response

You are leading a workshop where engineers express unquantified concerns about battery thermal management bottlenecks, while procurement insists on meeting aggressive delivery timelines. Describe how you would facilitate this session to capture these risks accurately without dismissing either perspective, and what specific steps you take to translate their inputs into your formal risk register.

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
Experience setting program-level risk thresholds, reallocating contingency reserves across workstreams, and calibrating P50/P90 financial exposure models.
Ability to design RFP evaluation matrices weighting interoperability and supply chain risks, conduct pre-bid alignment sessions, and negotiate risk-sharing terms.
Capability to build cross-program risk dashboards, draft decision memos for steering committees, and translate quantitative outputs into strategic recommendations.
Experience aligning regional charging network deployments with utility timelines, modeling cascading failure risks, and managing multi-site infrastructure dependencies.

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

Analyze the provided case of a multi-depot charging rollout facing conflicting utility interconnection timelines, vendor delivery delays, and tight municipal budget constraints. Walk us through your approach to reallocating contingency reserves across workstreams, renegotiating vendor risk-sharing terms, and maintaining program-level risk thresholds without triggering cascading schedule delays.

Format

case-study · 20 min · ~2 hr prep

Audience

Hiring panel including program directors, procurement leads, and utility partnership managers

What to prepare

  • Review the provided case materials (sent 48 hours prior to the session)
  • Prepare 3-5 slides outlining your risk architecture, reserve reallocation logic, escalation triggers, and stakeholder alignment strategy

Deliverables

  • A short deck (3-5 slides) framing your analysis and recommendations
  • A structured verbal walkthrough of your cross-workstream risk mitigation and reserve management approach

Ground rules

  • Do not produce new financial models or draft contract language; focus on analytical reasoning and strategic framing
  • You may reference past experiences to support your recommendations, but anchor your response to the constraints in the provided case

Scoring anchors

Exceeds
Candidate designs a cohesive risk architecture with explicit reserve reallocation triggers, demonstrates sophisticated vendor risk-sharing negotiation tactics, and outlines a clear monthly burn-down review process tied to program governance.
Meets
Candidate identifies key cross-workstream conflicts, proposes logical reserve reallocations, and describes a standard mitigation tracking process with defined escalation paths.
Below
Candidate jumps to tactical fixes without mapping dependencies, ignores vendor/utility risk-sharing constraints, or fails to establish clear thresholds for reserve reallocation and escalation.

Response time

20 min

Positive indicators

  • Surfaces hidden dependencies between workstreams before prescribing reserve shifts
  • Explicitly maps reserve reallocation to measurable milestone triggers and closure criteria
  • Demonstrates clear escalation pathways and decision-rights alignment across vendors, utilities, and municipal boards
  • Treats the risk register as a dynamic tracking tool, showing how mitigation effectiveness would be measured monthly

Negative indicators

  • Prescribes reserve shifts without defining accountability or mitigation ownership
  • Treats program risks as static silos rather than dynamically tracking cross-workstream burn-down
  • Defaults to top-down mandates without negotiating vendor risk-sharing or addressing utility queue constraints
  • Fails to articulate how cascading schedule delays would be prevented or contained

Work Simulation Scenario

Scenario. A regional charging network rollout is facing cascading delays due to grid interconnection bottlenecks. You must facilitate a 40-minute multi-party tradeoff discussion between the Utility Interconnection Manager, the Municipal Finance Director, and the OEM Vendor Liaison to reallocate contingency reserves and renegotiate vendor risk-sharing terms without derailing dependent depot schedules.

Problem to solve. Align competing incentives, establish a revised risk-sharing framework, and secure agreement on contingency reallocation that protects program-level delivery thresholds.

Format

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

Success criteria

  • Facilitate structured tradeoff discussion across all three functions
  • Propose a defensible risk-sharing mechanism that addresses grid delay exposure
  • Secure conditional agreement on contingency reserve reallocation
  • Maintain focus on cascading schedule impacts and program-level risk thresholds

What to review beforehand

  • Standard risk-sharing contract structures for infrastructure projects
  • Grid interconnection queue dynamics and utility upgrade timelines
  • Capital program contingency reserve allocation principles

Ground rules

  • You will drive the discussion, manage time, and synthesize tradeoffs
  • Each stakeholder has distinct incentives and constraints; they will not compromise without clear rationale
  • Focus on decision-making and alignment rather than exhaustive technical analysis

Roles in scenario

Marcus Vance, Municipal Finance Director (executive_sponsor, played by leadership)

Motivation. Protect the annual capital budget cap and avoid funding overruns; demands clear ROI justification for any reserve reallocation.

Constraints

  • Fixed annual budget ceiling with no mid-year appropriation flexibility
  • Requires board approval for any contingency shift exceeding 5% of total program value
  • Prioritizes short-term fiscal compliance over long-term operational resilience

Tensions to introduce

  • Pushes to cut contingency reserves rather than reallocate them
  • Questions the ROI of vendor risk-sharing clauses
  • Demands immediate, quantified financial impact before agreeing to any structural changes

In-character guidance

  • Respond to financial and governance-focused arguments with measured approval
  • Push back firmly on vague risk justifications
  • Agree to reallocation only if clear accountability triggers and reporting cadences are established

Do not

  • Volunteer budget flexibility or override procurement policy
  • Agree to reallocation without explicit financial safeguards
  • Dominate the conversation; allow the candidate to drive the tradeoff synthesis

Elena Rostova, Utility Interconnection Manager (cross_functional_partner, played by cross_functional)

Motivation. Protect grid stability and avoid peak demand charges; resists fast-tracking upgrades that strain existing infrastructure.

Constraints

  • Fixed transformer upgrade queue with 9-12 month lead times
  • Regulatory caps on demand charge exposure during pilot phases
  • Limited engineering bandwidth for accelerated site integrations

Tensions to introduce

  • Resists any proposal that shifts grid upgrade costs to the utility
  • Highlights that accelerated timelines compromise safety validation protocols
  • Demands explicit liability boundaries for grid-related delays

In-character guidance

  • Provide realistic grid constraints and regulatory boundaries when asked
  • Push back on proposals that ignore infrastructure validation cycles
  • Agree to conditional risk-sharing only if liability caps and phased commissioning windows are clearly defined

Do not

  • Volunteer alternative grid routing solutions
  • Agree to fast-tracked timelines without explicit safety caveats
  • Provide unverified interconnection data

David Chen, OEM Vendor Liaison (skeptical_stakeholder, played by peer)

Motivation. Maintain contract margins and avoid penalty triggers; willing to share risk only if schedule buffers are formally recognized.

Constraints

  • Fixed manufacturing lead times with limited production slot flexibility
  • Contractual penalties trigger after 60-day delivery delays
  • Requires formal change orders for any scope or timeline adjustments

Tensions to introduce

  • Pushes back on absorbing delay costs without reciprocal schedule extensions
  • Highlights that unmitigated grid delays will cascade into commissioning failures
  • Demands clear decision rights for contingency drawdown before committing to risk-sharing terms

In-character guidance

  • Negotiate based on contract terms and manufacturing realities
  • Push for explicit schedule buffer recognition in exchange for risk-sharing
  • Commit to revised terms only if accountability triggers and financial caps are mutually agreed

Do not

  • Volunteer manufacturing capacity expansions
  • Accept unilateral penalty clauses without reciprocal concessions
  • Resolve the negotiation without candidate facilitation

Scoring anchors

Exceeds
Masterfully navigates competing incentives, synthesizes a balanced risk-sharing framework with clear accountability triggers, and secures conditional agreement while maintaining program-level delivery thresholds.
Meets
Facilitates a structured discussion, identifies key tradeoffs, and proposes a workable risk-sharing mechanism with minor gaps in stakeholder alignment or contingency triggers.
Below
Struggles to manage cross-functional tensions, fails to propose a defensible risk-sharing structure, or allows the discussion to fragment without clear decisions or accountability.

Response time

40 min

Positive indicators

  • Structures the discussion to explicitly map competing incentives and program-level risk thresholds
  • Proposes a clear, defensible risk-sharing mechanism that balances grid, financial, and vendor constraints
  • Drives the group to conditional agreement on contingency reallocation with explicit accountability triggers
  • Maintains focus on cascading schedule impacts and prevents any single stakeholder from derailing the tradeoff synthesis

Negative indicators

  • Allows one stakeholder to dominate the conversation without synthesizing cross-functional tradeoffs
  • Fails to quantify or frame the financial and schedule impacts of proposed reallocations
  • Avoids making a decision or establishing clear accountability boundaries
  • Proposes risk-sharing terms that ignore contractual constraints or regulatory caps

Progression Framework

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

Risk Analysis & Technical Safety

3 competencies

CompetencyProject Risk ManagerProgram Risk LeadEnterprise Risk Director
Quantitative Risk Modeling & Hazard Identification

Executes quantitative risk models and identifies baseline technical hazards using established methodologies.

Integrates cross-project risk data to calibrate models and prioritize systemic technical hazards across portfolios.

Establishes enterprise modeling standards, defines hazard tolerance thresholds, and oversees advanced risk analytics strategy.

Risk Data Management & Analytical Tooling

Maintains project-level risk datasets, configures analytical tools, and ensures data integrity for reporting workflows.

Orchestrates standardized data pipelines across programs and optimizes tooling configurations for portfolio-wide analysis.

Governs enterprise risk data architecture, selects strategic analytics platforms, and mandates data quality standards.

Technical Safety Evaluation & Systems Risk Assessment

Conducts system-level safety evaluations, applies FMEA/HAZOP techniques, and documents technical failure modes.

Coordinates multi-system safety reviews, evaluates interface risks, and aligns mitigation strategies across interdependent projects.

Defines enterprise safety governance frameworks, oversees cross-domain risk assessments, and sets technical compliance baselines.

Risk Governance & Strategic Value

2 competencies

CompetencyProject Risk ManagerProgram Risk LeadEnterprise Risk Director
Enterprise Risk Strategy & Procurement Alignment

Identifies vendor and procurement risks, aligns contract terms with project risk tolerance, and tracks financial exposures.

Integrates risk criteria into program procurement strategies, optimizes resource allocation, and manages cross-vendor risk dependencies.

Defines enterprise risk appetite, aligns strategic investments with organizational value objectives, and governs procurement risk frameworks.

Lifecycle Risk Register & Mitigation Tracking

Maintains the project risk register, logs mitigation actions, and tracks compliance with reporting cycles.

Synthesizes program-level risk registers, monitors mitigation efficacy across projects, and ensures alignment with governance standards.

Directs strategic risk oversight, establishes enterprise register governance, and reports risk posture to executive stakeholders.