Electrified Transit Engineering & DeliveryExpert-built kit

Traction Power Engineer

Models traction power systems, sizes feeders and substations, designs switching schemes, and validates calculations against engineering standards.

Interview content for Traction Power Engineer

31
What to ask. Competency and attitude questions, assigned to the right round.
253
What to listen for. Positive and negative indicators, per question.
7
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 Dive17 competency questions

Core Power Systems & Architecture

Electrical Load Flow & Network Modeling

Develops dynamic network models to assess voltage regulation and harmonic distortion under varying operational loads.

Expected at Traction Power Engineer

Sample competency question

Describe a time when you performed load flow or harmonic distortion modeling for a traction network with multi-pulse rectifiers. How did you validate your model against IEEE standards and actual system behavior?

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

Positive indicators

  • Details model inputs, boundary conditions, and assumptions.
  • Explains harmonic spectrum analysis and compliance margins.
  • Correlates simulation results with measured field data.
  • Documents methodology for agency review.

Negative indicators

  • Uses default parameters without technical justification.
  • Cannot explain IEEE 519 application methodology.
  • Lacks validation process against physical system behavior.
  • Ignores network impedance variations.

While dynamic and harmonic analysis supports advanced design validation, it is typically applied to complex or high-impact sections rather than every standard project at this level.

Ryan Mahoney

Why this role is hard · Ryan Mahoney

At this level, you need someone who can handle load flow models and protection coordination without constant supervision. They must be able to approve design calculations and talk directly with utility representatives on their own. The real test happens when a candidate runs perfect software simulations but freezes during a live interconnection meeting. We often confuse strong software skills with actual job readiness. Genuine competence shows up as steady judgment and careful risk tracking when signing off on gear that will run heavy rail traffic for decades.

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

Level guides for Power Systems Analyst, Traction Power Engineer, Systems Integration Lead and Technical Authority.

Before you post

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

In the room

  • 17Competency interview questions
  • 14Attitude interview questions
  • 1Hands-on work simulations
  • 1Presentation prompts
  • 1Coding tests

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.

17 Competency Questions

1 of 17
  1. Discipline

    Core Power Systems & Architecture

  2. Job requirement

    Electrical Load Flow & Network Modeling

    Develops dynamic network models to assess voltage regulation and harmonic distortion under varying operational loads.

  3. Expected at Traction Power Engineer

    While dynamic and harmonic analysis supports advanced design validation, it is typically applied to complex or high-impact sections rather than every standard project at this level.

Interview round: Hiring Manager Technical Deep Dive

Describe a time when you performed load flow or harmonic distortion modeling for a traction network with multi-pulse rectifiers. How did you validate your model against IEEE standards and actual system behavior?

Positive indicators

  • Details model inputs, boundary conditions, and assumptions.
  • Explains harmonic spectrum analysis and compliance margins.
  • Correlates simulation results with measured field data.
  • Documents methodology for agency review.

Negative indicators

  • Uses default parameters without technical justification.
  • Cannot explain IEEE 519 application methodology.
  • Lacks validation process against physical system behavior.
  • Ignores network impedance variations.

14 Attitude Questions

1 of 14

Active Listening

Active Listening is the disciplined cognitive and communicative practice of fully concentrating on, comprehending, and retaining stakeholder input while consciously suspending premature judgment. In technical environments, it involves accurately decoding explicit constraints and implicit operational realities, reflecting core concerns back to contributors, and systematically integrating diverse perspectives into evidence-based decision-making to foster psychological safety, mitigate risk, and ensure alignment across multidisciplinary teams.

Interview round: Cross-Functional Integration & Collaboration

How would you approach a scenario where a maintenance supervisor raises a concern that directly contradicts your initial protection assumptions?

Positive indicators

  • Invites detailed walkthroughs of the concern
  • Compares field reality to simulation
  • Updates documentation if assumption is flawed
  • Maintains respectful technical dialogue

Negative indicators

  • Dismisses field experience as anecdotal
  • Insists on original assumptions without review
  • Escalates conflict instead of investigating
  • Ignores operational constraints

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.

Knock-out Questions

1 of 2

Application Screen: Knock-out

Do you currently hold an active Professional Engineer (PE) license in Electrical or Power Engineering in at least one U.S. jurisdiction?

Yes
Qualifies
No
Auto-decline

Video-Response Questions

1 of 3

Application Screen: Video Response

When coordinating grounding grid designs with signaling and track drainage teams, you encounter conflicting voltage drop requirements that clash with civil drainage grades. Describe the steps you would take to facilitate a joint alignment session, how you would translate the technical thresholds for non-electrical stakeholders, and what boundaries you would establish if external parties request additional unplanned modeling work mid-negotiation.

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
Demonstrates ownership of complete electrical architecture design for transit sites or depot charging, including equipment sizing and duty cycle alignment.
Shows experience coordinating with grid operators and conducting harmonic or power quality studies to secure interconnection approvals.
Demonstrates ability to develop and validate protective relay schemes, short-circuit analyses, and compliance documentation for high-voltage systems.
Shows evidence of authorizing technical submittals, mentoring junior staff, and validating constructability across multidisciplinary teams.

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.

Coding Test

Live Interview · Coding Test

Without AI

Implement a function that calculates the trip time for primary and backup breakers based on provided fault currents and inverse-time characteristics. Flag any coordination gaps where backup trips before primary.

Write a Python function that takes fault current values and breaker parameters (pickup, time dial). Compute trip times using standard inverse-time formulas and return a list of fault currents where the backup breaker trips faster than the primary, indicating a coordination failure.

With AI

Use AI to generate the basic inverse-time calculation. Your task is to integrate a dynamic fault-current limiter scenario. Decide whether to implement a fixed coordination scheme or an adaptive scheme that adjusts time dials based on real-time fault magnitude. Justify your architectural choice, implement it, and explain how it prevents nuisance tripping during high-inrush regenerative braking events.

Extend the coordination checker to handle a dynamic fault-current limiter. AI will handle base trip times. You must choose between a fixed coordination scheme and an adaptive time-dial adjustment scheme. Implement your choice, document why it prevents nuisance tripping during regenerative braking inrush, and modify the AI code to include a safety margin that survives a follow-up question about protection selectivity during cascading faults.

Response time

20 min

Positive indicators

  • Correct inverse-time curve implementation
  • Accurate comparison of primary vs backup trip times
  • Clear identification of coordination violations
  • Explicitly chooses fixed vs adaptive scheme with clear justification for regenerative inrush
  • Modifies AI boilerplate to inject dynamic time-dial logic or safety margins
  • Rejects AI's static threshold assumptions when they conflict with real-world inrush behavior
  • Documents selectivity preservation during cascading faults

Negative indicators

  • Incorrect formula application
  • Fails to handle edge cases like currents below pickup
  • Returns incorrect violation lists
  • Accepts AI's default fixed coordination without evaluating inrush impacts
  • Fails to document tradeoffs or justify adaptive vs fixed choice
  • Produces mathematically correct but operationally brittle coordination logic

Presentation Prompt

Walk us through a past project where you owned the complete electrical architecture for a traction power site or depot charging system. Discuss how you balanced code compliance, utility constraints, and operational margins, and how you mentored junior staff or coordinated cross-functional stakeholders during the design phase.

Format

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

Audience

Engineering leadership, utility interface managers, and senior peer engineers

What to prepare

  • Spend 1-2 hours selecting and structuring 3-5 slides around a representative project
  • Focus slides on technical tradeoffs, stakeholder coordination, and your decision rationale
  • Prepare to answer questions on protection coordination, utility interface challenges, and design validation

Deliverables

  • A 15-20 minute structured deck walkthrough highlighting your technical judgment and design rationale
  • A focused Q&A session demonstrating your ability to defend engineering tradeoffs and coordinate cross-functional teams

Ground rules

  • Use only de-identified or publicly shareable project artifacts
  • Remove sensitive utility data, proprietary vendor specs, or confidential client information before sharing
  • Focus on narrative and reasoning rather than detailed proprietary schematics

Scoring anchors

Exceeds
Delivers a compelling narrative that explicitly ties technical decisions to operational and regulatory outcomes, demonstrates mature stakeholder management, and shows deep systems-level judgment.
Meets
Provides a coherent project summary with clear technical tradeoffs, adequately explains design rationale, and answers questions with reasonable technical depth.
Below
Lacks focus on personal decision-making, relies heavily on team outcomes without specifying individual contributions, struggles to articulate constraints, or fails to justify technical choices.

Response time

20 min

Positive indicators

  • Clearly articulates the problem space, constraints, and personal decision points
  • Demonstrates how tradeoffs were evaluated (e.g., safety vs. schedule vs. cost) with defensible rationale
  • Shows evidence of mentoring junior staff or proactively aligning cross-functional stakeholders
  • Handles technical Q&A with structured, confident reasoning and acknowledges limitations when appropriate

Negative indicators

  • Presents a generic project overview without highlighting personal decision-making or ownership
  • Glosses over utility or compliance conflicts and fails to explain resolution strategies
  • Relies on team outcomes without specifying individual contributions or technical rationale
  • Becomes defensive or evasive when challenged on design tradeoffs or code compliance choices

Work Simulation Scenario

Scenario. You are leading the electrical architecture for a new traction substation. Early coordination reveals a conflict: the utility's feeder fault current limit is lower than the peak train acceleration requirement, creating a protection relay coordination gap. The project schedule is fixed, and safety margins cannot be compromised.

Problem to solve. Discuss your approach to resolving this paralleling station switching conflict. Identify what technical data you need, how you would evaluate protection scheme alternatives, and how you would communicate tradeoffs to utility and operations stakeholders.

Format

discovery-interview · 45 min · ~2 hr prep

Success criteria

  • Elicit critical fault current, impedance, and relay timing data before proposing solutions
  • Frame protection zone overlaps and breaker interrupting ratings as key decision variables
  • Propose a structured evaluation of alternatives (e.g., relay grading adjustments, BESS buffering, utility feeder upgrades)
  • Demonstrate assertive boundary-setting on safety standards while maintaining stakeholder alignment

What to review beforehand

  • Protective relay coordination principles and time-current curve (TCC) analysis
  • Traction substation switching schemes and utility interconnection constraints
  • Breaker interrupting rating specifications and fault current calculation basics

Ground rules

  • Focus on your decision-making framework and information-gathering strategy.
  • You are not expected to produce final relay settings or TCC plots.
  • Ask clarifying questions to uncover constraints; the partner will answer honestly.
  • Balance technical rigor with stakeholder management and schedule realities.

Roles in scenario

Lead Protection Engineer (informed_partner, played by peer)

Motivation. Assess whether the candidate can independently navigate protection coordination conflicts, prioritize safety margins, and structure a defensible technical approach.

Constraints

  • Will only provide system parameters, utility limits, and schedule constraints when asked.
  • Cannot suggest specific relay models or grading intervals unprompted.
  • Expects the candidate to drive the technical scoping conversation.

Tensions to introduce

  • If asked about utility feeder capacity, confirm that upgrading the feeder requires a 6-month permitting delay.
  • If asked about relay grading flexibility, note that existing downstream relays have fixed inverse-time curves that cannot be adjusted.
  • If asked about operational impact, state that dispatchers cannot tolerate more than 50ms of additional fault clearance time during peak hours.

In-character guidance

  • Respond factually to technical queries about system limits and relay constraints.
  • Acknowledge tradeoff discussions neutrally.
  • Maintain engineering rigor without coaching the candidate toward a solution.
  • Keep responses concise to allow the candidate to control the pacing.

Do not

  • Do not volunteer feeder upgrade timelines, relay curve limitations, or dispatch tolerance thresholds unless explicitly asked.
  • Do not recommend a specific protection scheme or relay setting adjustment.
  • Do not validate the candidate's proposed solution or reduce the technical complexity of the scenario.

Scoring anchors

Exceeds
Systematically isolates protection constraints, asks high-leverage technical questions, and constructs a defensible tradeoff framework that preserves safety margins while navigating utility and schedule pressures.
Meets
Identifies key relay coordination variables, asks reasonable clarifying questions, and outlines a standard approach to evaluating protection alternatives with adequate stakeholder communication.
Below
Guesses relay settings without data, ignores downstream constraints, or fails to balance technical safety with project schedule realities.

Response time

45 min

Positive indicators

  • Requests fault current data, impedance values, and existing relay curve parameters before proposing alternatives
  • Surfaces protection zone overlaps and breaker interrupting limits as primary constraints
  • Structures a clear evaluation matrix comparing relay adjustments, utility upgrades, and operational impacts
  • Demonstrates professional boundary-setting by refusing to compromise safety margins for schedule compression

Negative indicators

  • Assumes relay settings can be arbitrarily adjusted without verifying downstream constraints
  • Ignores utility feeder limitations or proposes unvalidated workarounds
  • Fails to articulate a structured tradeoff framework for stakeholder alignment
  • Concedes to schedule pressure at the expense of fault clearance safety margins

Progression Framework

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

Core Power Systems & Architecture

3 competencies

CompetencyPower Systems AnalystTraction Power EngineerSystems Integration LeadTechnical Authority
Electrical Load Flow & Network Modeling

Gathers field data and runs baseline load flow simulations to verify model accuracy under supervision.

Develops dynamic network models to assess voltage regulation and harmonic distortion under varying operational loads.

Oversees large-scale network modeling initiatives and integrates real-time operational data for predictive analysis.

Pioneers advanced simulation methodologies and sets industry benchmarks for traction network performance metrics.

Protective Relaying & Substation Coordination

Assists in setting relay parameters and drafting coordination studies using standard templates under guidance.

Designs and validates relay coordination schemes to ensure fault isolation and system reliability.

Architects comprehensive protection philosophies and leads commissioning testing for critical substation upgrades.

Defines next-generation protection strategies integrating adaptive relaying and cyber-physical resilience.

Traction Power System Analysis & Design

Conducts basic load calculations and reviews single-line diagrams under supervision to support reliable traction power delivery.

Independently performs detailed power flow studies and specifies equipment ratings for traction substations.

Directs multi-disciplinary power system studies and optimizes network configurations for complex rail corridors.

Establishes enterprise-wide power architecture standards and evaluates emerging high-capacity traction technologies.

Quality, Compliance & Operations

1 competencies

CompetencyPower Systems AnalystTraction Power EngineerSystems Integration LeadTechnical Authority
Engineering QA/QC & Regulatory Compliance

Reviews design documentation against code requirements and supports routine quality inspections.

Leads QA/QC audits, ensures compliance with NEC/NFPA/AREMA standards, and manages non-conformance reports.

Develops organizational quality management frameworks and oversees regulatory submissions for major infrastructure projects.

Sets enterprise compliance strategies, influences industry standards development, and drives continuous improvement in safety culture.

Smart Infrastructure & Integration

3 competencies

CompetencyPower Systems AnalystTraction Power EngineerSystems Integration LeadTechnical Authority
Depot Electrification & Charging Systems

Conducts site surveys and assists in layout planning for depot charging infrastructure under supervision.

Engineers depot power distribution networks and selects charging equipment to meet fleet operational demands.

Manages end-to-end depot electrification projects and coordinates utility upgrades for high-power charging demands.

Establishes depot design standards and evaluates future-ready charging ecosystems for autonomous and high-capacity fleets.

Energy Storage & Grid Integration

Supports feasibility studies for battery energy storage systems and evaluates basic interconnection requirements.

Designs BESS integration schemes and manages utility coordination for grid-tied traction power applications.

Directs the deployment of hybrid energy solutions and optimizes charge/discharge cycles for peak shaving and regenerative braking.

Shapes strategic energy storage roadmaps and establishes cross-sector integration frameworks for sustainable transit grids.

SCADA & Digital Twin Implementation

Configures HMI screens and monitors basic telemetry data for system health and alarm management.

Develops SCADA architecture specifications and implements digital twin models for real-time operational visibility.

Integrates disparate control systems and leads data analytics initiatives to enhance predictive maintenance capabilities.

Defines enterprise digital transformation strategies and standardizes data interoperability protocols across transit networks.