Risk Manager

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Picking a risk manager for our electrified transit projects goes against the usual playbook since this job requires both the guts to make hard calls and the technical sense to back them up. The right person will stop a faulty charger rollout before it tanks the schedule and keep tabs on every fix without bogging the crew down in admin work. I have seen experienced analysts panic when reserve funds get cut, which is why we skip the polished speakers and hire people who prove themselves with lean tracking sheets and straightforward warning signs.

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

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

  3. Expected at Junior

    Project Risk Managers must independently run probabilistic models and identify hazards to establish accurate schedule/cost baselines and contingency reserves for discrete capital initiatives.

Interview round: Hiring Manager Technical

Walk me through a recent capital project where you sized cost or schedule contingency. How did you approach it?

Positive indicators

  • Mentions specific probability distributions used
  • Describes SME validation of input data
  • Connects sensitivity drivers to budget/schedule decisions
  • Shows clear audit trail from model to approved reserves
  • Explains how uncertainty ranges were communicated

Negative indicators

  • Relies solely on deterministic flat rates
  • Cannot trace contingency sizing back to data
  • Ignores input validation or sensitivity testing
  • Uses jargon without explaining underlying logic
  • Treats model as static rather than iterative

12 Attitude Questions

1 of 12

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

How would you handle a situation where a near-miss event reveals a gap in your initial risk assessment model?

Positive indicators

  • Prioritizes model accuracy over defending original work
  • Uses near-miss data to drive proactive adjustments
  • Maintains transparent communication with project teams

Negative indicators

  • Dismisses near-misses as statistical noise
  • Attempts to justify the original model despite contradictory data
  • Fails to communicate model adjustments to stakeholders

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

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
Demonstrated use of Monte Carlo or P50/P90 simulation tools to quantify project budget contingencies and schedule float for infrastructure deployments.
Ability to translate engineering, maintenance, or field feedback into structured risk registers, FMEA databases, or safety compliance records for ZEV and charging systems.
Evidence of facilitating risk identification workshops, assigning mitigation ownership across teams, and tracking action completion through burn-down reviews.
Experience modeling utility queue timelines, grid capacity constraints, or vendor lead times to protect project milestones from external bottlenecks.

Does the resume show relevant prior work experience?

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?

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 a past project where you developed a quantitative risk model (e.g., Monte Carlo cost or schedule simulation) and translated its outputs into actionable contingency reserves or mitigation strategies. Discuss how you validated assumptions with engineering and procurement leads, handled stakeholder pushback on probabilistic ranges, and ensured the model actively guided daily trade-off decisions rather than sitting in an archive.

Format

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

Audience

Hiring panel including senior risk leaders and project delivery directors

What to prepare

  • Review 1-2 past projects where you built, calibrated, or led a quantitative risk model
  • Prepare 3-5 slides highlighting the model structure, key risk drivers, validation steps, and how outputs influenced tactical decisions

Deliverables

  • A 3-5 slide deck summarizing the project context, modeling approach, and operationalized outcomes
  • A 15-minute verbal walkthrough with 5 minutes for Q&A

Ground rules

  • Use only work you are permitted to share; anonymize client or proprietary data as needed
  • Focus on your reasoning, assumption validation, and decision-making process, not just the final model outputs

Scoring anchors

Exceeds
Candidate demonstrates sophisticated calibration techniques, explicitly links P50/P90 outputs to specific contingency triggers, and shows how stakeholder pushback was resolved through transparent assumption mapping.
Meets
Candidate clearly explains the model structure, identifies key cost/schedule drivers, and describes a straightforward process for translating outputs into reserve allocations and mitigation tracking.
Below
Candidate cannot articulate how assumptions were validated, treats outputs as absolute, or fails to connect the quantitative work to actual project trade-offs or decision rights.

Response time

20 min

Positive indicators

  • Clearly articulates model inputs, confidence intervals, and their operational limitations
  • Demonstrates how ground-truth constraints were integrated to prevent garbage-in/garbage-out outputs
  • Effectively communicates statistical ranges to non-technical stakeholders without oversimplifying or overcomplicating
  • Shows evidence of closing the loop by updating risk registers and adjusting mitigation actions based on model burn-down

Negative indicators

  • Treats probabilistic model outputs as deterministic facts without acknowledging variance
  • Fails to explain how frontline operational feedback was validated against the model
  • Uses excessive technical jargon without checking for stakeholder comprehension
  • Presents the model as a static reporting artifact rather than a living decision tool

Work Simulation Scenario

Scenario. You are stepping into a pilot depot charging rollout where engineering leads have raised fragmented, qualitative concerns about thermal management bottlenecks and aggressive OEM delivery timelines. You have 40 minutes to conduct a discovery interview with the Lead Electrical Engineer to extract the necessary parameters, clarify assumptions, and define hazard boundaries required to build a defensible Monte Carlo cost contingency model.

Problem to solve. Determine what data, constraints, and probabilistic assumptions are needed to transition from unstructured engineering concerns to a quantitative risk model that can command executive confidence for contingency allocation.

Format

discovery-interview · 40 min · ~2 hr prep

Success criteria

  • Surface hidden dependencies between OEM delivery promises and thermal supply chain realities
  • Identify specific probability distributions or data sources needed for the Monte Carlo simulation
  • Establish clear hazard boundaries and escalation triggers for thermal runaway scenarios
  • Translate qualitative concerns into structured risk statements without over-promising model precision

What to review beforehand

  • Basic principles of Monte Carlo simulation for project cost contingency
  • Common thermal management failure modes in high-density battery storage
  • OEM contract penalty structures and delivery milestone dependencies

Ground rules

  • You will drive the conversation by asking targeted, high-information questions
  • The partner will answer honestly but will not volunteer information or coach you
  • Focus on framing tradeoffs and surfacing assumptions rather than solving the mathematical model live

Roles in scenario

Dr. Aris Thorne, Lead Electrical Engineer (informed_partner, played by cross_functional)

Motivation. Wants a realistic risk model that protects the pilot schedule but resists being bogged down by excessive data requests that delay deployment.

Constraints

  • Historical performance data for this specific battery chemistry is sparse
  • OEM contracts impose heavy penalties if delivery milestones slip past 60 days
  • Thermal management component lead times have fluctuated by 30-40% in the last quarter

Tensions to introduce

  • Pushes back if questions feel overly academic or disconnected from field realities
  • Hints at unverified supplier capacity constraints but won't name them unless directly asked about supply chain bottlenecks
  • Emphasizes that engineering teams are already operating at capacity for pilot validation

In-character guidance

  • Answer questions directly with factual, realistic constraints
  • Provide technical context only when explicitly asked about thermal dynamics or OEM timelines
  • Acknowledge gaps in data honestly when probed about historical failure rates
  • Maintain a collaborative but time-conscious tone

Do not

  • Volunteer missing parameters, probability distributions, or hazard thresholds the candidate has not asked for
  • Coach the candidate on Monte Carlo methodology or statistical tools
  • Steer the candidate toward a preferred risk rating or contingency percentage
  • Provide unrealistic or perfectly clean data sets

Scoring anchors

Exceeds
Systematically maps the problem space with precise, high-yield questions; surfaces critical hidden assumptions; structures a clear path from qualitative concerns to a defensible quantitative model while maintaining stakeholder alignment.
Meets
Asks relevant clarifying questions, identifies key data gaps and hazard boundaries, and establishes a workable framework for the Monte Carlo model with minor gaps in assumption validation.
Below
Relies on guessing or generic templates; fails to probe for critical constraints; becomes overwhelmed by ambiguity or focuses excessively on theoretical modeling over actionable risk translation.

Response time

40 min

Positive indicators

  • Asks targeted, high-information questions to map data availability, probability distributions, and hazard boundaries
  • Surfaces and validates hidden assumptions about OEM delivery penalties and thermal supply chain volatility
  • Translates qualitative engineering concerns into structured, testable risk statements without guessing
  • Maintains focus on actionable model inputs rather than theoretical perfection, aligning with executive decision needs

Negative indicators

  • Guesses at probability distributions or contingency percentages without asking for underlying data
  • Freezes under ambiguity or defaults to generic risk frameworks without tailoring to the depot context
  • Over-indexes on technical modeling details while ignoring contractual and supply chain constraints
  • Accepts vague qualitative inputs without probing for measurable thresholds or escalation triggers

Progression Framework

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

Risk Analysis & Technical Safety

3 competencies

CompetencyJuniorMidSenior
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

CompetencyJuniorMidSenior
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.