Traction Power Engineer

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Finding an engineer who can run component-level math on their own is tough. You want someone who reads through utility rules carefully and calls out a depot charger layout if it crosses safety limits. They need to choose reliable analysis methods, write straightforward reports, and still accept that they cannot approve the final drawings. Too many applicants think being comfortable with spreadsheets means they actually understand the system. That mistake usually leads us to hire vocal engineers who overlook coordination details or shy analysts who stay silent when early designs are wrong.

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

    Core Power Systems & Architecture

  2. Job requirement

    Electrical Load Flow & Network Modeling

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

  3. Expected at Junior

    Handles routine data gathering and baseline simulation execution with guidance; ensures models reflect field conditions before senior validation.

Interview round: Hiring Manager Technical

Describe a situation where you ran baseline simulations for a transit network model. How did you approach reconciling the results with field data?

Positive indicators

  • References specific tolerance bands for voltage and current
  • Describes iterative parameter tuning process
  • Maintains clear version control of simulation files
  • Flags anomalies promptly for senior review
  • Follows a documented calibration checklist

Negative indicators

  • Accepts simulation outputs without field data validation
  • Adjusts parameters arbitrarily to force a match
  • Lacks clear documentation of methodology
  • Ignores minor but systematic discrepancies
  • Does not know when to escalate modeling issues

15 Attitude Questions

1 of 15

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: Recruiter Screen

If you were joining a charrette to gather interface requirements from the vehicle and civil teams for a new substation site, how would you approach the discussion to capture their constraints?

Positive indicators

  • Prepares an interface checklist beforehand
  • Asks about spatial and clearance limits first
  • Confirms understanding before moving on

Negative indicators

  • Dominates conversation with electrical specs
  • Assumes standard interfaces apply universally
  • Skips documentation until after meeting

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.

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 foundational ability to build and run load flow, impedance, or voltage drop models for electrical components using industry-standard software or academic projects.
Shows evidence of applying electrical codes and engineering standards to draft technical calculations or design notes for review.
Demonstrates ability to identify and document spatial or electrical conflicts between traction power systems and adjacent disciplines.
Shows capability to extract, organize, and visualize operational or simulation data for maintenance or planning teams.

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

Does the resume show relevant prior work experience?

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

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

1 of 2

Live Interview · Coding Test

Without AI

Implement the function to calculate expected load per substation from the provided schedule CSV. Flag any substation exceeding 95% of its rated capacity. Focus on clear logic and correct aggregation.

Write a Python function that reads a list of train schedule records, aggregates power demand per traction substation based on train location and acceleration profiles, and returns a dictionary mapping substation IDs to lists of violation timestamps where demand exceeds 95% of the provided limit.

With AI

You may use AI to generate boilerplate parsing and aggregation code. However, you must architect a solution that handles dynamic regenerative braking feedback. Decide whether to use a deterministic worst-case model or a probabilistic Monte Carlo approach, justify your choice in comments, and implement the chosen method. Explain why your choice survives a follow-up question about grid stability during simultaneous braking events.

Extend the starter code to model load flow under peak schedules that include regenerative braking events. AI will handle the CSV parsing and basic summation. Your engineering task is to choose between a deterministic worst-case aggregation and a probabilistic Monte Carlo simulation for capturing braking feedback. Implement your chosen approach, explicitly document the tradeoff (e.g., computational cost vs. accuracy during cascading braking), and ensure the code flags substations where the chosen model predicts >95% capacity. Your solution must be defensible if an operations lead asks why you didn't use the alternative method.

Response time

20 min

Positive indicators

  • Correct aggregation of time-sliced demand
  • Accurate floating-point comparison against thresholds
  • Clean handling of missing or malformed schedule entries
  • Explicitly chooses and justifies deterministic vs probabilistic modeling
  • Modifies AI-generated boilerplate to inject braking feedback loops
  • Documents why the chosen model handles cascading braking better for the given context
  • Rejects AI suggestions that ignore grid stability constraints

Negative indicators

  • Incorrect time-window grouping
  • Hardcoded thresholds
  • Failure to handle edge cases like zero-length schedules
  • Accepts AI's default deterministic summation without evaluating braking feedback
  • Fails to document tradeoffs or justification
  • Produces mathematically correct but operationally brittle code that breaks under peak regenerative loads

Presentation Prompt

Walk us through your approach to validating a DC traction feeder sizing calculation when presented with conflicting utility metering data and legacy agency operating schedules. Discuss how you would trace assumptions back to source data, handle ambiguity, and ensure your draft deliverable withstands peer review without over-engineering. Slides are optional; you may talk through your reasoning step-by-step.

Format

approach-walkthrough · 20 min · ~2 hr prep

Audience

Senior engineers, peer reviewers, and technical hiring panel

What to prepare

  • Spend 1-2 hours reflecting on past load-flow or short-circuit analysis experiences
  • Outline your step-by-step validation workflow on paper or in a personal note-taking tool
  • Prepare to discuss how you document assumptions and communicate constraints to reviewers

Deliverables

  • A structured verbal walkthrough of your analytical approach
  • Clear articulation of how you would frame the data conflict, surface assumptions, and prepare for peer review

Ground rules

  • Focus on your reasoning process and decision-making framework rather than producing a final calculation
  • Slides are entirely optional; talking through your logic is sufficient
  • Use only methods, templates, or frameworks you are permitted to share

Scoring anchors

Exceeds
Systematically frames the data conflict, proposes a transparent validation workflow, clearly articulates how to balance precision with practical constraints, and demonstrates strong peer-review readiness.
Meets
Identifies key variables and proposes a reasonable validation path, acknowledges data conflicts, and outlines a basic documentation approach for review.
Below
Ignores conflicting data, jumps to conclusions without framing, struggles to articulate assumptions, or provides a fragmented, unstructured approach.

Response time

20 min

Positive indicators

  • Asks high-information clarifying questions about data sources before proposing a validation path
  • Explicitly maps out how conflicting inputs would be reconciled using traceable engineering principles
  • Surfaces assumptions about peak loads and schedule variability with clear risk boundaries
  • Explains a structured documentation approach that prepares the deliverable for rigorous peer review

Negative indicators

  • Jumps to a single calculation method without framing the underlying data conflict
  • Ignores the constraint of legacy operating schedules or dismisses them as irrelevant
  • Over-complicates the solution without justifying tradeoffs or referencing standards
  • Fails to articulate how they would handle reviewer pushback or document rationale

Work Simulation Scenario

Scenario. You are tasked with developing a load flow model for a new single-site transit charging depot. The project manager has provided a folder containing legacy agency operating schedules, recent utility metering exports, and a draft site layout. The utility data shows peak demand 15% lower than the agency's historical projections, and the operating schedules contain overlapping shift handoffs that create ambiguous dwell times.

Problem to solve. Walk us through how you would construct a defensible load profile and select calculation methods. Identify what information you need, how you would validate conflicting data sources, and how you would document your assumptions for peer review.

Format

discovery-interview · 45 min · ~2 hr prep

Success criteria

  • Clearly articulate a structured approach to data reconciliation before running models
  • Ask targeted questions to resolve schedule ambiguity and metering discrepancies
  • Define audit-ready documentation standards for assumptions and calculation methods
  • Demonstrate awareness of IEEE 141/399 compliance boundaries without over-engineering

What to review beforehand

  • Basic principles of AC/DC traction load flow modeling
  • Common utility metering data formats and typical transit agency scheduling constraints
  • IEEE 141 and IEEE 399 standards overview for industrial and commercial power systems

Ground rules

  • This is a discussion of your approach, not a request to produce a deliverable or run calculations live.
  • You will interact with a single informed partner who will answer your questions honestly.
  • Focus on clarifying questions, assumption surfacing, and methodology selection.
  • You have 45 minutes; pace your inquiry to cover data validation, modeling strategy, and documentation.

Roles in scenario

Senior Traction Power Engineer (informed_partner, played by hiring_manager)

Motivation. Ensure the candidate can independently structure an analytical workflow that withstands peer review and avoids costly rework from flawed baseline data.

Constraints

  • Can only provide information explicitly requested by the candidate.
  • Must maintain realistic technical accuracy but cannot volunteer context.
  • Time-constrained; expects focused, high-information questions.

Tensions to introduce

  • If asked about metering discrepancies, reveal that the utility meter was calibrated two years ago and has known drift during extreme temperature events.
  • If asked about schedule ambiguity, clarify that dispatchers manually override shift logs during peak turnover, creating undocumented load spikes.
  • If asked about documentation standards, state that the agency recently updated its peer review checklist to require explicit traceability for all load factors.

In-character guidance

  • Answer questions directly and factually.
  • Acknowledge the candidate's methodological choices neutrally.
  • Provide technical details only when specifically prompted.
  • Maintain a professional, collaborative tone throughout.

Do not

  • Do not volunteer information about meter calibration, dispatch overrides, or peer review checklists unless explicitly asked.
  • Do not steer the candidate toward a specific modeling software or calculation method.
  • Do not solve the load reconciliation problem for them or validate their approach prematurely.

Scoring anchors

Exceeds
Systematically deconstructs ambiguous data, asks high-leverage questions to resolve conflicts, and articulates a peer-review-ready documentation protocol aligned with IEEE standards.
Meets
Identifies key data conflicts, asks reasonable clarifying questions, and outlines a standard modeling and documentation approach with adequate assumption tracking.
Below
Assumes data is accurate without verification, struggles to structure a methodology, or fails to address traceability and compliance requirements.

Response time

45 min

Positive indicators

  • Asks targeted questions to isolate the root cause of data discrepancies before modeling
  • Surfaces assumptions about temperature effects, shift overlaps, and meter calibration
  • Proposes a clear documentation framework that maps every load factor to a verifiable source
  • Demonstrates awareness of IEEE standards boundaries and peer review expectations

Negative indicators

  • Guesses load profile parameters without asking clarifying questions
  • Freezes or defaults to generic modeling steps when presented with conflicting data
  • Ignores auditability and traceability requirements in documentation strategy
  • Over-engineers component specs without justifying them against validated baselines

Progression Framework

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

Core Power Systems & Architecture

3 competencies

CompetencyJuniorMidSeniorPrincipal
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

CompetencyJuniorMidSeniorPrincipal
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

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