Transit TechExpert-built kit

IT Director

Monitors real-time transit feeds, maintains developer APIs, and audits scheduling databases for data compliance.

Buy this kit · $29.99Preview questions

Interview content for IT Director

29
What to ask. Competency and attitude questions, assigned to the right round.
242
What to listen for. Positive and negative indicators, per question.
8
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: IT Strategy & Operational Oversight17 competency questions

Architecture, Data & Integration Systems

Predictive Mobility & Network Planning Platforms

Deploys and tunes mobility forecasting algorithms, validating outputs against operational baselines to inform network planning and resource allocation.

Expected at IT Director

Sample competency question

Give an example of how you've used predictive forecasting models to guide infrastructure capacity or network planning decisions.

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

Positive indicators

  • References baseline data for validation
  • Converts forecasts into concrete recommendations
  • Monitors model drift and accuracy over time
  • Aligns predictions with fiscal planning cycles
  • Facilitates cross-functional planning discussions

Negative indicators

  • Accepts model outputs without validation
  • Fails to translate data into actionable plans
  • Ignores accuracy tracking or KPI alignment
  • Disregards budget or resource constraints
  • Presents forecasts as absolute certainties

Predictive modeling requires specialized data science expertise; the Director needs independent proficiency to validate outputs and align forecasts with budget and operational constraints.

Ryan Mahoney

Why this role is hard · Ryan Mahoney

Finding an IT director for an operation this size means hiring someone who can sit with frustrated transit operators, absorb their daily constraints, and turn that friction into a realistic tech plan. The real test is whether they will push back on executive vanity projects when budgets are tight and vendor contracts are already locked. You need a leader who spots the actual bottleneck and tells the board plainly that keeping systems online matters more than buying the latest software. Plenty of applicants have managed spreadsheets, but very few have survived the daily grind of strict security rules, tough vendor negotiations, and keeping the dispatch network alive.

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

Level guides for Associate IT Director, IT Director, Senior IT Director and Principal IT Director.

Before you post

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

In the room

  • 17Competency interview questions
  • 12Attitude 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.

17 Competency Questions

1 of 17

  1. Discipline

    Architecture, Data & Integration Systems

  2. Job requirement

    Predictive Mobility & Network Planning Platforms

    Deploys and tunes mobility forecasting algorithms, validating outputs against operational baselines to inform network planning and resource allocation.

  3. Expected at IT Director

    Predictive modeling requires specialized data science expertise; the Director needs independent proficiency to validate outputs and align forecasts with budget and operational constraints.

Interview round: Hiring Manager: IT Strategy & Operational Oversight

Give an example of how you've used predictive forecasting models to guide infrastructure capacity or network planning decisions.

Positive indicators

  • References baseline data for validation
  • Converts forecasts into concrete recommendations
  • Monitors model drift and accuracy over time
  • Aligns predictions with fiscal planning cycles
  • Facilitates cross-functional planning discussions

Negative indicators

  • Accepts model outputs without validation
  • Fails to translate data into actionable plans
  • Ignores accuracy tracking or KPI alignment
  • Disregards budget or resource constraints
  • Presents forecasts as absolute certainties

12 Attitude Questions

1 of 12

Active Listening

A deliberate cognitive and behavioral practice of fully concentrating on, comprehending, and responding to verbal and non-verbal cues from diverse stakeholders to accurately capture underlying needs, technical constraints, and unspoken operational risks. It requires suspending immediate judgment, synthesizing fragmented or conflicting inputs, and validating understanding through reflective questioning before formulating strategic IT decisions or architectural solutions.

Interview round: Recruiter Screen: Fit & Expectations

How would you approach gathering requirements when a new vendor platform must integrate with several legacy operational systems that lack comprehensive documentation?

Positive indicators

  • Proposes structured shadowing sessions with end users
  • Maps undocumented workflows to vendor capabilities
  • Builds validation checkpoints into early project phases

Negative indicators

  • Assumes vendor documentation covers all operational needs
  • Relies exclusively on IT staff without consulting frontline users
  • Commits to integration scope before validating 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 have at least 3 years of direct experience managing PCI-DSS compliance audits and coordinating with Qualified Security Assessors?

Yes
Qualifies
No
Auto-decline

Video-Response Questions

1 of 3

Application Screen: Video Response

You are managing a quarterly vendor contract renewal for back-office reconciliation. The vendor requests unbudgeted scope expansions while simultaneously missing data submission deadlines. Walk us through how you would structure your next conversation with both the vendor and your internal finance lead to enforce boundaries, communicate financial risks, and align on a revised agreement.

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 managing IT P&L, optimizing software or hardware licensing costs, executing capital procurement cycles, and aligning quarterly budgets with finance operations.
Resume evidence of scheduling and overseeing major transit or dispatch platform upgrades, coordinating vendor SLAs, and executing terminal rollouts with minimal service disruption.
Resume evidence of directing monthly vulnerability audits, enforcing risk-based patching schedules, facilitating blameless post-incident reviews, and updating operational failure playbooks.
Resume evidence of automating ridership or network efficiency dashboards, synthesizing operational data into executive briefings, and establishing measurable IT performance indicators.

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 and walk us through a past initiative where you managed vendor contracts and security compliance for a core platform deployment. Discuss your approach to balancing financial constraints, audit requirements, and cross-functional stakeholder alignment, highlighting the key tradeoffs you navigated.

Format

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

Audience

CTO, Director of Finance, and Head of Information Security

What to prepare

  • 3-5 slides outlining the initiative context, your decision framework, compliance checkpoints, and financial tradeoffs
  • Prepared talking points to guide a structured walkthrough

Deliverables

  • A structured deck presentation followed by a guided Q&A on vendor accountability and compliance governance

Ground rules

  • Redact any confidential financial figures, vendor names, or sensitive security details
  • Focus on your reasoning, negotiation tactics, and governance processes rather than proprietary implementation specifics

Scoring anchors

Exceeds
Articulates a nuanced decision framework that seamlessly integrates financial, compliance, and operational constraints, demonstrating mature vendor governance and clear stakeholder alignment.
Meets
Presents a coherent initiative overview, explains key tradeoffs between cost and compliance, and shows structured vendor management and cross-functional communication.
Below
Lacks a clear decision framework, glosses over financial or compliance tradeoffs, fails to address stakeholder alignment, or relies on unstructured anecdotal evidence.

Response time

20 min

Positive indicators

  • Clearly articulates the intersection of financial constraints, audit requirements, and platform capabilities
  • Demonstrates structured negotiation tactics and boundary-setting with vendors
  • Translates technical compliance mandates into actionable business tradeoffs
  • Uses data or past metrics to justify prioritization and risk acceptance decisions

Negative indicators

  • Presents compliance or financial details without explaining the underlying decision framework
  • Avoids discussing tradeoffs or frames vendor conflicts as purely adversarial without resolution strategies
  • Fails to connect platform selection to broader enterprise budget predictability or operational impact
  • Relies on jargon without translating technical risks into business terms for finance/security audiences

Work Simulation Scenario

Scenario. You are the IT Director responsible for fare systems and business operations enablement. The monthly fare revenue reporting pipeline has produced a 3.2% discrepancy against Finance's ledger for the third consecutive month. Finance is threatening to delay automated settlement until IT guarantees 100% accuracy, while Engineering argues the variance falls within acceptable tolerance for legacy AFC hardware. You must facilitate a decision on how to reconcile the pipeline, adjust SLA thresholds, and allocate engineering resources without halting operations.

Problem to solve. Drive a multi-party discussion to resolve the reporting discrepancy, align Finance and Engineering on accuracy thresholds, and decide on resource allocation and phased remediation steps.

Format

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

Success criteria

  • Facilitate balanced tradeoff discussion that acknowledges both financial and technical constraints
  • Translate technical variance into clear business impact and risk exposure
  • Secure agreement on measurable SLA adjustments and phased engineering commitments

What to review beforehand

  • Review standard fare reconciliation workflows and common variance drivers
  • Understand legacy AFC hardware tolerance limits and data pipeline architecture
  • Familiarize yourself with cross-departmental SLA negotiation best practices

Ground rules

  • This is a live decision facilitation, not a written strategy document
  • You may ask clarifying questions to uncover constraints and priorities
  • Focus on steering the conversation toward actionable tradeoffs and clear ownership

Roles in scenario

Director of Finance & Revenue Assurance (skeptical_stakeholder, played by peer)

Motivation. Protect revenue integrity and ensure audit-ready financial reporting before committing to automated settlement.

Constraints

  • Cannot accept variance above 1.5% without executive risk sign-off
  • Month-end close deadline is 10 days away
  • Requires transparent data lineage for compliance auditors

Tensions to introduce

  • Finance views the 3.2% gap as a systemic control failure, not a technical tolerance
  • Willing to accept phased remediation but demands immediate manual reconciliation funding
  • Questions IT's accountability for historical data drift

In-character guidance

  • Express skepticism but remain open to data-driven compromise
  • Highlight audit risks and compliance deadlines when pressed
  • Provide clear financial thresholds and reporting requirements when asked

Do not

  • Do not unilaterally concede to IT proposals without explicit risk mitigation
  • Do not escalate hostility or threaten executive intervention unless the candidate fails to address core concerns
  • Do not provide a pre-written reconciliation plan; let the candidate drive the tradeoff discussion

Lead Data Engineering Manager (cross_functional_partner, played by cross_functional)

Motivation. Protect engineering bandwidth and prevent disruptive pipeline rewrites while maintaining system stability.

Constraints

  • Engineering team is at capacity with scheduled platform upgrades
  • Legacy AFC hardware cannot produce perfectly synchronized timestamps
  • Requires at least two sprint cycles to implement automated variance filters

Tensions to introduce

  • Argues that 100% accuracy is mathematically impossible with current hardware
  • Proposes a tolerance band adjustment but lacks immediate engineering resources
  • Resists manual reconciliation as a long-term operational burden

In-character guidance

  • Defend technical constraints but remain collaborative on phased solutions
  • Provide realistic sprint timelines and resource tradeoffs when asked
  • Acknowledge Finance's compliance needs while advocating for engineering feasibility

Do not

  • Do not dismiss Finance's compliance requirements as irrelevant
  • Do not volunteer unscheduled engineering capacity without explicit prioritization discussion
  • Do not solve the resource allocation conflict for the candidate

Scoring anchors

Exceeds
Aligns parties on phased accuracy targets, secures explicit resource commitments, and establishes a transparent escalation path that satisfies compliance without overburdening engineering.
Meets
Acknowledges both constraints, proposes reasonable threshold adjustment, and outlines basic remediation steps with shared ownership.
Below
Sides with one function without justification, leaves action items ambiguous, escalates tension, or fails to address compliance deadlines.

Response time

40 min

Positive indicators

  • Translates technical variance into clear business impact and risk exposure for non-technical stakeholders
  • Facilitates balanced tradeoff discussion that acknowledges both financial compliance and engineering feasibility
  • Proposes measurable SLA adjustments with phased remediation and clear ownership
  • Maintains professional tone while steering conflicting parties toward actionable compromise

Negative indicators

  • Defers to one function without validating the other's core constraints or compliance requirements
  • Allows conversation to become adversarial without steering toward structured tradeoffs
  • Fails to establish clear ownership, timelines, or escalation paths for pipeline fixes
  • Uses vague language or unverified assumptions to justify decisions

Progression Framework

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

Architecture, Data & Integration Systems

4 competencies

CompetencyAssociate IT DirectorIT DirectorSenior IT DirectorPrincipal IT Director
Predictive Mobility & Network Planning Platforms

Runs predictive model simulations and prepares data for forecasting tools to support tactical network planning and service adjustments.

Deploys and tunes mobility forecasting algorithms, validating outputs against operational baselines to inform network planning and resource allocation.

Aligns predictive platforms with network planning goals, translating model outputs into actionable transit strategies.

Pioneers AI-driven mobility optimization, establishing strategic foresight capabilities and cross-agency planning integration.

Real-Time API & Integration Ecosystems

Monitors API endpoint health and assists in troubleshooting integration failures to maintain seamless third-party and internal data exchange.

Builds and secures integration middleware, implementing rate limiting and authentication protocols to enable reliable cross-system data exchange.

Architects scalable API ecosystems, enforcing governance and enabling strategic partner integrations.

Drives industry-wide interoperability frameworks, establishing open API standards and strategic data-sharing partnerships.

Transit Data Architecture & Telemetry Design

Assists in configuring data ingestion pipelines and monitoring telemetry streams under supervision to ensure continuous data flow for transit operations.

Designs modular telemetry architectures and optimizes data storage for high-throughput transit feeds, ensuring scalable data pipelines align with enterprise operational goals.

Leads enterprise data strategy, ensuring scalability, latency optimization, and cross-system telemetry alignment.

Defines future-state transit data architecture standards, driving industry-wide telemetry innovation and strategic data governance.

Transit Data Standards & Open Source Governance

Documents data schemas and assists in validating feeds against standard specifications to ensure compliance and interoperability.

Enforces GTFS/real-time compliance and evaluates open-source transit tools for operational fit, maintaining interoperability standards across the department.

Governs open-source adoption lifecycles, establishing contribution policies and vendor-neutral standards alignment.

Shapes regional and national transit data standardization initiatives, advocating for open data ecosystems and interoperability mandates.

Operations, Security & Business Enablement

4 competencies

CompetencyAssociate IT DirectorIT DirectorSenior IT DirectorPrincipal IT Director
Accessibility Standards & Universal Design Implementation

Tests interfaces against accessibility guidelines using automated and manual assistive tools to verify compliance before deployment.

Integrates WCAG and transit-specific accessibility standards into development lifecycles and conducts compliance audits to ensure equitable service delivery.

Leads inclusive design strategy, ensuring cross-platform accessibility and aligning tech with equity mandates.

Champions universal transit tech policy, driving cross-agency accessibility mandates and strategic inclusive design investments.

Fare Systems & Business Operations Enablement

Configures fare collection modules and troubleshoots ticketing hardware/software integrations to maintain revenue operations and system reliability.

Optimizes ticketing system performance, manages payment gateway integrations, and monitors transaction integrity to protect revenue streams and rider experience.

Aligns fare technology with business operations, driving revenue optimization and seamless MaaS integrations.

Transforms fare ecosystems into strategic MaaS and revenue optimization platforms, defining long-term commercialization and partnership roadmaps.

Security Compliance & Vendor Financial Management

Performs routine security audits and assists in tracking vendor contract deliverables to ensure compliance and budget adherence.

Implements compliance frameworks, manages vulnerability remediation, and negotiates vendor SLAs to secure systems and optimize technology spend.

Directs enterprise cybersecurity posture and financial risk mitigation, aligning vendor ecosystems with compliance mandates.

Defines enterprise-wide security governance and strategic vendor ecosystems, shaping budget allocation and regulatory compliance strategy.

System Reliability & DevOps Enablement

Executes CI/CD pipelines and assists in basic infrastructure provisioning and monitoring to sustain high transit system availability.

Automates infrastructure deployment, configures observability dashboards, and optimizes release cycles to sustain high availability across multi-team portfolios.

Designs resilient DevOps frameworks, establishing SRE practices and operational resilience for critical transit services.

Establishes enterprise reliability engineering strategy, driving cloud-native transformation and cross-functional operational excellence.