Transit TechExpert-built kit

Director of Transit Technology

Sets strategic direction, manages teams and vendors, and advocates for rider-focused technology investment.

Buy this kit · $29.99Preview questions

Interview content for Senior Technology Director

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

Service Planning & Business Operations

Demand-Responsive Transit

Designs DRT service models and integrates them with fixed-route networks.

Expected at Senior Technology Director

Sample competency question

Recount a pilot program you managed for on-demand transit services.

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

Positive indicators

  • Data driven decision making
  • Clear communication strategy
  • Realistic budget management

Negative indicators

  • No clear success criteria
  • Ignores impact on fixed routes
  • No plan for post-pilot

The director independently oversees the strategic integration of DRT models with fixed-route networks, ensuring alignment with broader service reliability and scalable infrastructure goals. While specialized managers handle operational design, the director independently evaluates cost-per-trip benchmarks and zone integration strategies, mitigating risks of poor integration and suboptimal efficiency.

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Most candidates are good at managing vendors or writing code, but few can do both while dealing with public sector politics. You need someone who can explain why open data standards matter to a city council member without using confusing tech speak. They have to hold vendors accountable for delivery while remaining open to feedback when critical legacy systems break. The real test is finding a leader who takes responsibility when a fare payment integration fails during peak rush hour. This role demands a rare mix of technical skill and political backbone that standard resumes rarely show.

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

Level guides for Technology Manager, Senior Technology Director and Principal Transit Technologist.

Before you post

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

In the room

  • 18Competency interview questions
  • 13Attitude interview questions
  • 1Hands-on work simulations
  • 1Presentation prompts

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.

18 Competency Questions

1 of 18

  1. Discipline

    Service Planning & Business Operations

  2. Job requirement

    Demand-Responsive Transit

    Designs DRT service models and integrates them with fixed-route networks.

  3. Expected at Senior Technology Director

    The director independently oversees the strategic integration of DRT models with fixed-route networks, ensuring alignment with broader service reliability and scalable infrastructure goals. While specialized managers handle operational design, the director independently evaluates cost-per-trip benchmarks and zone integration strategies, mitigating risks of poor integration and suboptimal efficiency.

Interview round: Hiring Manager Technical & Strategy

Recount a pilot program you managed for on-demand transit services.

Positive indicators

  • Data driven decision making
  • Clear communication strategy
  • Realistic budget management

Negative indicators

  • No clear success criteria
  • Ignores impact on fixed routes
  • No plan for post-pilot

13 Attitude Questions

1 of 13

Accountability Mindset

The consistent willingness to accept ultimate responsibility for team outcomes, strategic decisions, and operational failures, characterized by transparent communication, immediate corrective action, and a focus on systemic improvement rather than blame assignment.

Interview round: Hiring Manager Technical & Strategy

What steps would you take if a vendor failed to meet a critical contract milestone?

Positive indicators

  • Enforces accountability firmly
  • Protects agency interests

Negative indicators

  • Ignores the breach
  • Absorbs the cost without challenge

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.

Video-Response Questions

1 of 3

Application Screen: Video Response

Describe a time you had to explain complex data-sharing requirements to an external mobility partner who requested expanded access beyond the agreed scope. How did you communicate your boundaries and ensure alignment without damaging the partnership?

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
Evidence of designing and directing integrated technology roadmaps across multiple transit modes, including capital budgeting and platform selection for regional networks.
Evidence of defining and negotiating transit data specifications, API schemas, and data-sharing frameworks with city agencies and private mobility partners.
Evidence of overseeing the development, deployment, and operationalization of machine learning models for arrival forecasting, battery health, or predictive maintenance using IoT data.
Evidence of managing complex vendor contracts, enforcing performance metrics, and leading engineering and operations teams through structured procurement and delivery cycles.

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.

Presentation Prompt

Prepare a short deck walking us through a past initiative where you integrated disparate data systems from private mobility partners into a regional network without compromising agency control or data sovereignty. Discuss your architectural decisions, how you navigated procurement and board dynamics, and the measurable outcomes of the integration.

Format

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

Audience

Executive hiring committee including CTO, Chief Procurement Officer, and Regional Planning Director

What to prepare

  • Select one relevant past integration or data governance project
  • Draft 3-5 slides covering context, decision framework, stakeholder alignment, and results
  • Prepare to defend your architectural and policy trade-offs during Q&A

Deliverables

  • A 3-5 slide presentation deck
  • A structured verbal walkthrough of the project lifecycle and your decision-making process

Ground rules

  • Use only work you are permitted to share; anonymize sensitive partner or financial data as needed
  • Focus on narrative, judgment, and strategic alignment rather than exhaustive technical diagrams
  • Do not produce net-new strategic artifacts; ground the discussion in past experience

Scoring anchors

Exceeds
Delivers a tightly structured narrative that explicitly links architectural choices to procurement realities, demonstrates sophisticated stakeholder alignment, and quantifies outcomes with clear post-integration governance metrics.
Meets
Provides a coherent walkthrough of a relevant integration project, outlines key decisions and stakeholder interactions, and identifies reasonable success metrics.
Below
Lacks strategic framing, focuses excessively on technical implementation details, ignores governance/procurement constraints, and fails to articulate measurable outcomes or trade-offs.

Response time

20 min

Positive indicators

  • Clearly articulates the strategic problem before diving into tactical solutions
  • Demonstrates structured trade-off analysis between partner flexibility and agency control
  • Shows evidence of navigating board/procurement constraints while maintaining technical integrity
  • Uses measurable outcomes to validate architectural and policy decisions
  • Anticipates and addresses counterarguments regarding data privacy or vendor lock-in

Negative indicators

  • Presents a chronological project dump without highlighting decision points or trade-offs
  • Overlooks procurement, legal, or board approval realities in the integration narrative
  • Fails to define clear metrics for success or post-launch validation
  • Uses vague language around data sovereignty or agency control mechanisms
  • Defensive or dismissive when questioned about partner constraints or technical compromises

Work Simulation Scenario

Scenario. You are leading a cross-functional working group to establish regional open data standards for a new Mobility-as-a-Service (MaaS) integration. You must align internal engineering, external private mobility partners, and legal/compliance teams on a unified GTFS/GBFS data schema and sharing agreement. Tensions exist around data granularity, privacy, and commercial IP.

Problem to solve. Facilitate a decision-making session to agree on the core data fields, update frequencies, and privacy boundaries for the regional open data portal, ensuring compliance while enabling seamless MaaS integration.

Format

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

Success criteria

  • Navigate competing incentives to find a mutually acceptable data schema
  • Establish clear privacy and IP boundaries for shared data
  • Drive consensus on SLA and compliance enforcement mechanisms
  • Document tradeoffs and secure commitment from all parties

What to review beforehand

  • GTFS and GBFS specification differences
  • Regional data privacy regulations
  • Common MaaS integration data requirements

Ground rules

  • You are facilitating a multi-party discussion. Drive the conversation toward decisions.
  • Each participant has distinct priorities and constraints.

Roles in scenario

Private Mobility Partner CTO (external_partner, played by cross_functional)

Motivation. Protect proprietary routing algorithms and user data while gaining access to regional transit schedules for app integration.

Constraints

  • Cannot share real-time vehicle location data due to competitive IP
  • Requires high-frequency transit feed for accurate multimodal routing

Tensions to introduce

  • Push for exclusive early access to certain transit data fields
  • Resist strict latency SLAs due to internal API limitations
  • Question the agency's right to mandate data sharing formats

In-character guidance

  • Advocate strongly for partner IP and commercial interests
  • Negotiate pragmatically but protect core business assets
  • Respond to tradeoff proposals with realistic operational constraints

Do not

  • Do not concede on IP protection without clear reciprocal value
  • Do not become hostile or uncooperative
  • Do not provide solutions that bypass the candidate's facilitation

Agency Legal & Compliance Counsel (skeptical_stakeholder, played by leadership)

Motivation. Ensure strict compliance with state privacy laws and minimize liability for data misuse or breaches.

Constraints

  • Mandates anonymization of all rider-level data
  • Requires explicit data retention limits and audit rights

Tensions to introduce

  • Insist on restrictive data sharing clauses that slow integration
  • Push back on any real-time data publication without legal review
  • Demand heavy penalties for schema non-compliance

In-character guidance

  • Focus heavily on risk mitigation and regulatory alignment
  • Ask clarifying questions about enforcement and auditability
  • Remain firm on non-negotiable compliance boundaries

Do not

  • Do not override the candidate's process
  • Do not volunteer legal loopholes or easy fixes
  • Do not dominate the conversation without allowing tradeoff discussion

Internal Data Engineering Lead (peer, played by peer)

Motivation. Deliver a technically feasible, scalable data pipeline that minimizes custom middleware and maintenance overhead.

Constraints

  • Limited engineering bandwidth for custom API transformations
  • Legacy database architecture struggles with high-frequency writes

Tensions to introduce

  • Argue against real-time feeds due to infrastructure costs
  • Push for standardized, batch-based data exchange instead
  • Highlight the technical debt of supporting multiple partner schemas

In-character guidance

  • Provide clear technical constraints and capacity limits
  • Advocate for simplicity and standardization in the data pipeline
  • Support feasible compromises that reduce long-term maintenance

Do not

  • Do not solve the architecture for the candidate
  • Do not agree to technically impossible SLAs
  • Do not disengage from the negotiation process

Scoring anchors

Exceeds
Expertly facilitates a structured tradeoff discussion, aligns all parties on a compliant and technically feasible data standard, and secures clear commitments on SLAs, IP boundaries, and enforcement mechanisms.
Meets
Guides the group toward a workable data schema, acknowledges legal and technical constraints, and reaches a baseline agreement on sharing protocols and compliance.
Below
Fails to structure the discussion, allows stakeholders to talk past each other, or proposes an unenforceable standard that ignores key legal or technical constraints.

Response time

40 min

Positive indicators

  • Structures the discussion to surface priorities before debating specifics
  • Translates technical constraints into business and compliance tradeoffs
  • Drives explicit agreements on data fields, SLAs, and enforcement
  • Maintains neutrality while facilitating competing stakeholder interests

Negative indicators

  • Allows one stakeholder to dominate the conversation
  • Fails to capture or document agreed-upon boundaries and SLAs
  • Proposes solutions that ignore legal or technical constraints
  • Escalates tension instead of mediating tradeoffs

Progression Framework

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

Service Planning & Business Operations

4 competencies

CompetencyTechnology ManagerSenior Technology DirectorPrincipal Transit Technologist
Demand-Responsive Transit

Monitors DRT algorithm performance and adjusts service zones to optimize flexible transit service delivery.

Designs DRT service models and integrates them with fixed-route networks.

Evaluates DRT viability as a core service model and secures funding.

Micromobility Integration

Coordinates dock placement and manages vendor compliance for bikes, scooters, and last-mile mobility solutions.

Develops micromobility policies and integrates data feeds.

Shapes urban mobility policy and secures right-of-way for micromobility.

Mobility as a Service (MaaS)

Coordinates API connections with third-party mobility providers to enable integrated multi-modal transportation options.

Develops partnership agreements and manages the MaaS user experience.

Defines the regional MaaS ecosystem strategy and revenue sharing models.

Service Planning & Strategy

Analyzes ridership data to recommend schedule adjustments that optimize service delivery and meet passenger demand.

Designs network redesigns and manages public engagement processes.

Sets long-term service vision and aligns operational goals with regional land use.

Transit Technology & Infrastructure

5 competencies

CompetencyTechnology ManagerSenior Technology DirectorPrincipal Transit Technologist
Accessibility Tech

Tests digital and physical interfaces for ADA compliance to ensure technology systems are accessible for all passengers.

Leads accessibility audits and integrates feedback into product roadmaps.

Establishes organizational accessibility policies and champions inclusive design culture.

Fare Payment & Ticketing

Oversees daily fare system operations and resolves transaction disputes to maintain revenue security and customer satisfaction.

Leads fare policy implementation and integrates new payment methods.

Defines long-term revenue collection strategy and open payment ecosystem partnerships.

Fleet Management & Telematics

Monitors fleet health dashboards and coordinates maintenance scheduling via telematics systems for operational efficiency.

Integrates telematics data with operational planning systems and manages vendor contracts.

Drives fleet electrification strategy and long-term infrastructure investment planning.

Open Data Standards

Executes data publishing workflows and ensures compliance with GTFS/GTFS-RT standards for public and partner consumption.

Designs data governance frameworks and manages API ecosystems for third-party developers.

Defines organizational data strategy and influences regional or national open data policies.

Transit Signal Priority

Configures TSP equipment and monitors intersection performance metrics to improve transit reliability.

Negotiates signal priority agreements with municipal traffic departments.

Advocates for regional signal priority standards and smart city integration.