Transit Technology Project Manager

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Anyone can handle a Gantt chart or vendor contract, but that isn't the real challenge. We need someone who can explain routine changes to a bus operator without sparking a revolt. They have to hold technical vendors accountable while still respecting the people who actually drive the buses. Most candidates discuss delivery timelines but struggle when real world needs clash with software limits. Real ownership looks like negotiating scope trade-offs when a data feed breaks during rush hour.

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 Technology Project Management

  2. Job requirement

    Compliance & Reporting

    Prepares regulatory submissions and tracks compliance metrics, ensuring projects meet regulatory requirements and produce necessary reports.

  3. Expected at Mid

    Autonomous preparation of regulatory submissions and tracking of compliance metrics is essential to avoid missed deadlines, audit failures, and budget variances exceeding the 5% threshold. This level expects the manager to independently maintain accurate reporting and documentation to ensure continuous compliance and project approval readiness.

Interview round: Hiring Manager Technical

Reflect on a project where you had to adhere to strict regulatory or reporting requirements.

Positive indicators

  • Treats compliance as a design constraint
  • Automates reporting where possible
  • Proactive about regulatory changes

Negative indicators

  • Treats compliance as an afterthought
  • Manual reporting processes only
  • Unaware of specific regulations

14 Attitude Questions

1 of 14

Accountability Mindset

The consistent commitment to accept ownership for project decisions, actions, and results, prioritizing transparent communication and solution-oriented remediation over blame avoidance, particularly when public service reliability and safety are impacted.

Interview round: Hiring Manager Technical

A vendor fails to meet a critical deadline due to their own internal issues. How do you handle the situation?

Positive indicators

  • Enforces contract professionally
  • Protects project interests
  • Communicates transparently

Negative indicators

  • Makes excuses for vendor
  • Hides delay from leadership
  • Absorbs impact without question

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 2

Application Screen: Video Response

Imagine you are managing a pilot for new contactless payment technology. Executive stakeholders request adding two major features mid-pilot to meet an upcoming political deadline, which threatens the testing timeline and core functionality. How would you communicate your position, what boundaries would you set, and how would you negotiate an alternative path forward?

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
Leads end-to-end deployment of multi-team modules, coordinating dependencies across IT, vendors, and operations to ensure minimal service disruption.
Navigates regulatory compliance checks, manages vendor service-level agreements, and guides contract deliverables through public-sector budget cycles.
Documents adjusting project roadmaps, prioritizing backlogs based on operational constraints, and negotiating trade-offs between security protocols and feature availability.
Coordinates live disruption communications, utilizes mass notification tools, and executes contingency plans to maintain rider and staff information flow.

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 owned a multi-team feature set or product module. Focus on how you negotiated scope trade-offs and timeline adjustments with stakeholders, particularly when balancing IT security protocols against operational needs for immediate feature availability.

Format

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

Audience

Hiring panel including program leadership and cross-functional peers

What to prepare

  • A short 3-5 slide deck summarizing the project context, the trade-off challenge, your decision-making process, and the outcome.

Deliverables

  • A 3-5 slide deck and a verbal walkthrough of your strategic alignment and negotiation approach.

Ground rules

  • Use only work you are permitted to share; redact sensitive agency or vendor data.
  • Focus on your personal decision rights and negotiation approach, not just team outcomes.

Scoring anchors

Exceeds
Masterfully frames the trade-off, demonstrates sophisticated stakeholder negotiation, and clearly links tactical adjustments to strategic roadmap goals.
Meets
Presents a coherent project narrative, explains trade-offs logically, and shows reasonable stakeholder management.
Below
Lacks strategic framing, focuses only on execution details, avoids discussing trade-offs, or shows poor stakeholder alignment.

Response time

20 min

Positive indicators

  • Clearly articulates the tension between security protocols and operational urgency
  • Demonstrates structured negotiation tactics and evidence-based trade-off analysis
  • Shows how they aligned technical roadmap milestones with stakeholder expectations
  • Reflects on lessons learned and how the approach would adapt to future constraints

Negative indicators

  • Presents a purely tactical timeline without addressing strategic trade-offs
  • Blames stakeholders or security teams for delays without showing ownership
  • Fails to explain the rationale behind scope prioritization decisions
  • Overlooks the impact of timeline adjustments on downstream teams or rider experience

Work Simulation Scenario

Scenario. You own the rollout of a new contactless payment module across 120 buses. IT Security has flagged a potential vulnerability and mandates a 14-day penetration testing window before launch. Operations leadership insists on launching on schedule to meet a public commitment and avoid $250K in legacy farebox maintenance overtime. You are facilitating a 40-minute decision meeting to align on scope, timeline, and risk mitigation.

Problem to solve. Facilitate a structured tradeoff discussion that balances security compliance with operational urgency, identifies a mutually acceptable path forward (phased rollout, conditional launch, or controlled delay), and secures explicit stakeholder commitments.

Format

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

Success criteria

  • Surfaces underlying incentives and non-negotiable constraints for both parties
  • Frames tradeoffs transparently without taking sides prematurely
  • Proposes or facilitates a risk-mitigated compromise (e.g., phased deployment, sandboxed pilot, or conditional sign-off)
  • Ends with documented decisions, owners, and escalation triggers

What to review beforehand

  • Basic contactless payment architecture and typical security review gates
  • Public transit fare collection operational dependencies
  • Standard risk mitigation strategies for phased tech rollouts

Ground rules

  • Your role is to facilitate the decision, not to dictate the technical or operational outcome
  • Focus on aligning incentives, surfacing risks, and sequencing commitments
  • You may propose options, but stakeholders must own the final tradeoff

Roles in scenario

Sarah Lin, IT Security Manager (cross_functional_partner, played by cross_functional)

Motivation. Ensure zero critical vulnerabilities reach production; protect agency from data breach liability and regulatory penalties.

Constraints

  • Pen test requires dedicated staging environment
  • Cannot approve sign-off without full vulnerability scan
  • Audit requirements are non-negotiable for payment systems

Tensions to introduce

  • Refuses to compress pen test timeline under any circumstance
  • Questions whether operations is willing to accept breach liability
  • Suggests delaying launch entirely if full test isn't completed

In-character guidance

  • Maintain firm stance on security protocols but remain open to phased approaches
  • Provide honest answers about audit requirements when asked
  • Push for risk documentation if any compromise is proposed
  • Acknowledge operational costs but prioritize compliance

Do not

  • Do not volunteer a phased testing workaround unless prompted
  • Do not escalate to hostility or threaten to block all projects
  • Do not solve the scheduling conflict for the candidate
  • Do not concede on critical security gates without documented risk acceptance

David Torres, Operations Director (skeptical_stakeholder, played by leadership)

Motivation. Avoid service disruption, control overtime costs, and maintain public trust by hitting the announced launch date.

Constraints

  • Legacy farebox maintenance contract expires in 14 days
  • Public announcement already distributed to riders and press
  • Driver training is scheduled for next week

Tensions to introduce

  • Argues that delaying launch will cost more in overtime and public backlash
  • Suggests launching with 'basic security checks' instead of full pen test
  • Pressures the PM to 'take the risk' or override security temporarily

In-character guidance

  • Be direct about budget and public commitment pressures
  • Answer honestly about operational flexibility when questioned
  • Show willingness to consider phased rollout if it limits overtime
  • Push back on solutions that increase driver workload or confuse riders

Do not

  • Do not volunteer a phased rollout plan unless the candidate facilitates it
  • Do not agree to bypass security protocols outright
  • Do not become adversarial toward the security manager
  • Do not make the final decision for the candidate

Scoring anchors

Exceeds
Expertly aligns competing incentives, structures a risk-mitigated phased approach, secures explicit sign-offs with clear ownership, and establishes monitoring/rollback triggers that satisfy both security and operational constraints.
Meets
Facilitates a structured discussion, identifies core constraints, proposes a reasonable compromise, and captures decisions with minor gaps in risk documentation or escalation planning.
Below
Struggles to manage competing priorities, defaults to delaying or rushing without analysis, allows unproductive conflict, or ends without clear accountability or next steps.

Response time

40 min

Positive indicators

  • Surfaces non-negotiable constraints and underlying incentives before proposing solutions
  • Frames tradeoffs using clear risk/reward language accessible to both technical and operational stakeholders
  • Guides the conversation toward a structured compromise (e.g., phased launch, conditional sign-off with monitoring)
  • Secures explicit commitments, owners, and defined escalation triggers before closing

Negative indicators

  • Takes sides prematurely or acts as a messenger rather than a facilitator
  • Proposes vague compromises without defining risk boundaries or success metrics
  • Allows the conversation to devolve into blame or unstructured debate
  • Fails to document decisions or leaves accountability ambiguous

Progression Framework

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

Transit Technology Project Management

7 competencies

CompetencyJuniorMidSeniorPrincipal
Compliance & Reporting

Gathers data for compliance reports and audits, ensuring documentation is updated and risk escalation occurs appropriately.

Prepares regulatory submissions and tracks compliance metrics, ensuring projects meet regulatory requirements and produce necessary reports.

Interprets regulations and mitigates compliance risks ensuring audit success and regulatory adherence.

Establishes organizational compliance frameworks and policy to ensure regulatory alignment and risk mitigation at industry level.

Data Standards & Interoperability

Assists in data collection and validates format compliance, ensuring valid feed submissions and resolving data errors.

Configures data feeds and troubleshoots integration errors, ensuring transit data standards and systems integration requirements are met.

Architects data exchange protocols and ensures standard compliance across integrated transit systems.

Influences industry data standards and interoperability frameworks to enable ecosystem-wide integration and market expansion.

Operations & Service Integration

Supports operational staff during technology rollout, learning specific operational constraints and user needs deeply.

Aligns technology features with operational workflows, ensuring technology supports transit service delivery effectively.

Optimizes service delivery through technology enhancements aligned with operational workflows and rider needs.

Drives operational transformation through innovative technology solutions to enable service delivery innovation and market expansion.

Project Planning & Execution

Executes defined project tasks and maintains documentation under supervision, managing daily task queue within agreed sprint goals.

Manages workstreams and resolves routine project issues independently, coordinating scope, schedule, and resources for transit technology implementations.

Leads complex project phases and aligns deliverables with strategic goals across multiple workstreams.

Defines organizational project management standards and mentors leadership to ensure strategic initiative delivery and talent attraction.

Stakeholder & Vendor Management

Communicates status updates to immediate team and vendors, ensuring stakeholders are informed of progress and issues.

Facilitates meetings and manages vendor deliverables, coordinating with internal stakeholders and external vendors to ensure project alignment.

Negotiates contracts and resolves high-level stakeholder conflicts across agency divisions and external partners.

Shapes vendor partnership strategies and executive stakeholder engagement to drive technology partnerships and brand reputation.

Strategic Roadmapping & Innovation

Researches emerging technologies and documents findings, building knowledge base for future project contributions.

Contributes to roadmap planning and pilot project execution, developing long-term technology strategies and identifying innovation opportunities.

Develops strategic roadmaps and leads innovation initiatives aligning technology investments with agency policy goals.

Sets industry vision and drives organizational innovation culture through long-term technology strategy and investment thesis development.

Technology Implementation & Configuration

Performs system installations and basic configuration tasks, building tool proficiency within the technology team environment.

Manages deployment cycles and resolves technical configuration issues, deploying and configuring transit technology systems within operational environments.

Oversees system architecture and integration across multiple platforms ensuring cohesive technology deployment.

Defines technology selection criteria and long-term infrastructure strategy to ensure technology partnerships and long-term viability.