Operations Data Analyst

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Hiring at this level means finding someone who can build reliable tracking models and explain them to dispatch teams that have zero patience for academic theory. The real challenge is balancing technical skill with straightforward communication. You will meet candidates who write clean Python but freeze when a maintenance supervisor asks why a schedule shift matters. Others will talk smoothly but cannot separate useful telemetry from faulty GPS drift. The right hire simply connects the numbers back to yard operations, admits what they do not know, and builds dashboards that actually change how we staff our routes.

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

    Transit Operations Data Analytics & Engineering

  2. Job requirement

    Cross-Functional Reporting & Visualization

    Designs interactive dashboards, tailors data narratives for diverse stakeholders, and automates reporting workflows.

  3. Expected at Mid

    Directly drives the >60% self-service dashboard adoption and >40% insight implementation success indicators. Requires advanced proficiency to handle diverse stakeholder needs and automate complex reporting.

Interview round: Hiring Manager Technical Assessment

Recall a project where you designed and launched a self-service reporting tool for non-technical operations staff. How did you structure the rollout and track its usage?

Positive indicators

  • Focuses heavily on usability and workflow fit
  • Establishes clear feedback loops post-launch
  • Measures active engagement, not just logins

Negative indicators

  • Assumes high technical literacy without training
  • Launches without establishing success metrics
  • Lacks plan to gather or act on user feedback

9 Attitude Questions

1 of 9

Active Listening

The deliberate cognitive and behavioral practice of fully concentrating on, comprehending, and retaining stakeholder communications while suspending immediate analytical assumptions, in order to accurately capture operational nuances, technical constraints, and qualitative insights before translating them into structured data, predictive models, or actionable operational reports.

Interview round: Recruiter Initial Screen

How would you approach a scenario where two operational departments provide conflicting definitions for a key performance metric you need to track?

Positive indicators

  • Suggests joint workshop to unpack terminology differences
  • References operational reality over theoretical definitions
  • Proposes phased transition for metric alignment
  • Focuses on shared planning outcomes

Negative indicators

  • Picks one department's definition arbitrarily
  • Escalates immediately without investigating root cause
  • Builds separate pipelines to avoid conflict
  • Assumes leadership should dictate the definition

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 have professional experience working directly with GTFS or GTFS-RT data feeds to analyze or optimize public transit operations?

Yes
Qualifies
No
Auto-decline

Video-Response Questions

1 of 2

Application Screen: Video Response

You present a newly built performance dashboard to dispatch supervisors who become confused by the statistical confidence intervals and question why certain operational delays aren't flagged as errors. Walk me through exactly how you would explain the underlying methodology and address their concerns in real-time.

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
Resume evidence of designing, building, or maintaining automated data workflows that replace manual tracking with scalable, self-service reporting.
Resume evidence of joining disparate transit datasets to analyze congestion, dwell times, or passenger loads across routes.
Resume evidence of converting operational questions into structured data models and prioritizing analytics project backlogs for assigned domains.
Resume evidence of analyzing scheduling data against contractual, financial, or operational constraints to guide service adjustments.

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

Prepare a short deck walking us through a past project where you designed or refactored an analytical pipeline to solve a recurring operational problem. Discuss how you selected your methodology, balanced rapid delivery with long-term scalability, and managed stakeholder feedback or scope adjustments.

Format

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

Audience

Analytics managers and cross-functional operations partners

What to prepare

  • 3-5 slides highlighting the problem context, your analytical approach, key tradeoffs, and measurable outcomes.

Deliverables

  • A concise deck and a 15-20 minute walkthrough of your work and decision-making process.

Ground rules

  • Use only work you are permitted to share; redact sensitive agency or proprietary data.
  • Focus on your reasoning, methodology choices, and collaboration, not just the final dashboard or report.

Scoring anchors

Exceeds
Presents a nuanced narrative linking analytical rigor to operational impact, explicitly details tradeoff management, and shows mature stakeholder alignment.
Meets
Walks through a coherent project lifecycle, explains methodology choices, and demonstrates basic stakeholder communication and delivery.
Below
Lacks clear connection between analysis and business value, glosses over tradeoffs, or cannot articulate how feedback was handled.

Response time

20 min

Positive indicators

  • Clearly articulates the business problem and how analytical methods were matched to it
  • Demonstrates awareness of scalability vs. speed tradeoffs
  • Shows how stakeholder feedback was integrated without derailing the project
  • Presents measurable impact tied to operational outcomes

Negative indicators

  • Focuses exclusively on tools/tech without explaining the analytical rationale
  • Ignores stakeholder constraints or presents a linear, unrealistic project path
  • Fails to connect the analysis to downstream operational decisions
  • Deflects questions about methodology limitations or data quality

Work Simulation Scenario

Scenario. Planning leadership has handed you a vague request: 'Find out where we're losing efficiency in block-level layover times and tell us how to fix it before union contract renewals.'

Problem to solve. Define the analytical approach, identify required data, clarify operational and compliance constraints, and outline how you'll deliver actionable scheduling insights.

Format

discovery-interview · 35 min · ~2 hr prep

Success criteria

  • Translates vague leadership request into a clearly scoped analytical problem
  • Identifies union compliance constraints, data availability gaps, and stakeholder success metrics
  • Proposes a phased methodology balancing statistical rigor with operational feasibility

What to review beforehand

  • Review sample block scheduling templates and historical layover distribution reports
  • Familiarize yourself with standard transit union contract minimum layover requirements

Ground rules

  • Approach this as a live scoping conversation, not a final deliverable
  • Ask for constraints, data sources, and timeline expectations before proposing methods
  • Focus on how your analysis will translate into real-world scheduling adjustments

Roles in scenario

Operations Planning Manager (informed_partner, played by cross_functional)

Motivation. Needs a reliable, contract-compliant analysis that optimizes layover times without violating union minimums or disrupting daily scheduling workflows.

Constraints

  • Must strictly adhere to union contract minimum layover requirements
  • Historical data is fragmented or missing for recently added routes
  • Analysis must be completed within a 3-week deadline to inform contract negotiations

Tensions to introduce

  • Pushes back if the proposed methodology is overly academic or ignores real-world scheduling constraints
  • Asks for quick wins but insists on statistical rigor for final recommendations
  • Questions timeline feasibility and data access limitations when probing for historical records

In-character guidance

  • Provide operational context and scheduling realities when asked
  • Share constraints about union rules and data gaps only when explicitly probed
  • Maintain focus on actionable scheduling outcomes and contract compliance

Do not

  • Do not hand over the exact union clause text or raw dataset schema unless requested
  • Do not steer the candidate toward a specific analytical tool or statistical model
  • Do not approve the candidate's plan prematurely or volunteer scheduling workarounds

Scoring anchors

Exceeds
Systematically unpacks the vague request into a scoped, compliance-aware analytical plan. Asks high-yield questions about data gaps, union thresholds, and operational constraints. Proposes a realistic, phased methodology with clear stakeholder alignment checkpoints.
Meets
Identifies key constraints and proposes a reasonable analytical approach. Asks clarifying questions about data availability and timeline. Methodology is sound but may require minor refinement on compliance or operational feasibility.
Below
Accepts ambiguity without scoping. Proposes a methodology that ignores union constraints or data quality realities. Overcommits on timeline or fails to connect analysis to scheduling outcomes.

Response time

35 min

Positive indicators

  • Clarifies success metrics, union constraints, and data availability before proposing analytical methods
  • Proposes a phased approach balancing quick diagnostic insights with rigorous baseline modeling
  • Identifies potential compliance risks and outlines mitigation strategies for missing historical data
  • Sets realistic timelines with clear stakeholder check-ins and scope boundaries

Negative indicators

  • Accepts the vague request at face value without scoping constraints or success criteria
  • Ignores union/contract compliance implications in the proposed modeling approach
  • Overpromises on delivery timeline without validating data access or cleaning requirements
  • Fails to define how analytical outputs will translate into actionable scheduling adjustments

Progression Framework

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

Transit Operations Data Analytics & Engineering

7 competencies

CompetencyJuniorMidSeniorPrincipal
Cross-Functional Reporting & Visualization

Creates routine reports and visualizations for operational teams using established templates to ensure consistent, timely stakeholder communication.

Designs interactive dashboards, tailors data narratives for diverse stakeholders, and automates reporting workflows.

Architects enterprise reporting ecosystems, standardizes visualization best practices, and ensures data storytelling aligns with strategic objectives.

Defines organizational data communication strategy, drives executive-level decision support platforms, and establishes industry reporting benchmarks.

Data Governance & Quality Assurance

Performs basic data validation checks and documents data quality issues using established protocols to maintain dataset integrity and support downstream analytics.

Implements data quality rules, manages metadata, and coordinates with engineering teams to resolve data anomalies.

Establishes comprehensive data governance frameworks, defines quality SLAs, and leads compliance initiatives for sensitive transit data.

Champions enterprise data stewardship, shapes regulatory compliance strategies, and drives industry-wide data standardization efforts.

Data Pipeline Engineering & Ingestion

Extracts and loads transit operational data using predefined scripts and established ETL tools under supervision to ensure reliable data availability for daily reporting.

Designs and maintains reliable data pipelines, troubleshooting failures and optimizing ingestion workflows for various transit data sources.

Architects scalable ingestion frameworks, establishes data contracts, and integrates real-time transit APIs into enterprise data platforms.

Defines organizational data architecture strategy, leads cross-system pipeline standardization, and drives adoption of next-generation streaming technologies.

Fleet & Asset Telematics

Processes telematics data for vehicle diagnostics and tracks basic maintenance metrics to support fleet operations and preventive maintenance tracking.

Analyzes fleet utilization and maintenance patterns to optimize dispatching and preventive maintenance schedules.

Develops predictive maintenance models, integrates IoT sensor data streams, and evaluates electrification readiness metrics.

Sets enterprise telematics strategy, leads cross-agency asset lifecycle analytics, and drives adoption of autonomous/zero-emission fleet technologies.

Operational Data Analysis & Modeling

Runs routine queries and generates basic operational reports using standard SQL and analytical tools to support daily operational tracking and service optimization.

Conducts independent exploratory analysis, builds statistical models to identify operational bottlenecks, and translates findings into actionable insights.

Develops advanced predictive models, leads complex analytical projects, and mentors junior analysts in statistical methodology and transit domain context.

Establishes enterprise-wide analytical frameworks, drives strategic decision-making through advanced simulation, and sets methodological standards for transit operations research.

Performance & Schedule Analytics

Monitors schedule adherence and basic performance KPIs, flagging deviations for review to support operational planning and timetable tracking.

Analyzes schedule reliability and on-time performance trends, recommending timetable adjustments to improve service delivery.

Designs performance evaluation frameworks, models network-wide schedule impacts, and collaborates with planning teams to optimize routing and headways.

Pioneers advanced schedule optimization algorithms, influences agency-wide performance standards, and publishes industry-leading methodologies.

Revenue & Ridership Modeling

Compiles ridership counts and fare collection data into standard dashboards and spreadsheets to support routine demand tracking and baseline reporting.

Builds farebox recovery models and analyzes ridership elasticity to support pricing and service level decisions.

Leads comprehensive revenue forecasting, integrates multi-modal fare data, and advises leadership on MaaS integration impacts.

Architects enterprise revenue analytics strategy, shapes regional mobility pricing policies, and drives innovation in fare technology evaluation.