Transit UX Designer

Ryan Mahoney

Why this role is hard · Ryan Mahoney

It is hard to find designers who can own a feature without constant handholding in this sector. Designers need to understand that a pretty interface means nothing if the bus data is late or incorrect, so they must balance rider frustration with the hard limits of our legacy ticketing systems. Strong candidates show they have listened to actual commuters, not just stakeholders in a boardroom, and prove they can integrate design into the messy reality of transit operations without breaking the service. Too many candidates focus on visual polish instead of how the system works, so we look for people who know when to push back on a product request because the underlying data cannot support it.

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 UX & Service Design

  2. Job requirement

    Fare Payment & Ticketing UX

    Designs secure and intuitive payment interfaces for web and mobile channels.

  3. Expected at Mid

    Rated as independent because secure payment flows are critical revenue-generating features requiring autonomous ownership. Mid-level designers must independently design intuitive, compliant ticketing interfaces to prevent transaction failures, security risks, and revenue loss.

Interview round: Hiring Manager Portfolio Review

Give me an example of a payment or ticketing flow you designed or improved.

Positive indicators

  • Mentions reducing dwell time at gates
  • Designs for high-stress environments
  • Tests with diverse payment capabilities

Negative indicators

  • Adds unnecessary confirmation steps
  • Ignores hardware read-range limitations
  • Assumes all users have credit cards

14 Attitude Questions

1 of 14

Active Listening

The disciplined cognitive and behavioral practice of fully concentrating on, understanding, and responding to stakeholders, users, and technical teams to ensure safety, feasibility, and user needs are accurately captured, validated, and integrated into transit design solutions without distortion or assumption.

Interview round: Hiring Manager Portfolio Review

During a requirements gathering meeting, how do you ensure you've captured the core need versus the requested solution?

Positive indicators

  • Distinguishes problem from solution
  • Validates understanding aloud
  • Documents the 'why'

Negative indicators

  • Accepts requests at face value
  • Starts designing immediately
  • Doesn't ask clarifying questions

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 designing digital interfaces that strictly comply with WCAG 2.1 AA (or equivalent) accessibility standards?

Yes
Qualifies
No
Auto-decline

Video-Response Questions

1 of 3

Application Screen: Video Response

Describe how you would facilitate a workshop with regional transit partners who are resistant to adopting new open fare payment UX standards. What specific talking points do you use to address their legacy infrastructure concerns while maintaining your design integrity?

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
Independently manages the full lifecycle of a specific product area or rider journey from problem definition to delivered solution.
Ensures consistency between digital interfaces and physical transit touchpoints such as kiosks, signage, or station displays.
Designs interfaces that gracefully handle data latency, connectivity loss, or delayed updates in passenger information systems.
Plans and executes usability evaluations or field measurements, using quantitative or qualitative data to drive design refinements.

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?

Does the resume show relevant prior work experience?

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

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 discussing your approach to designing an end-to-end routing experience. Walk us through how you prioritized trade-offs between real-time data accuracy, low-bandwidth performance, and multilingual support, and how you resolved conflicts independently.

Format

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

Audience

Design manager, product lead, and engineering partner

What to prepare

  • 3-5 slides outlining a past routing or journey-planning project
  • Notes on trade-off decisions, data latency handling, and stakeholder alignment

Deliverables

  • A structured deck presentation
  • Verbal walkthrough of your prioritization framework and independent decision-making

Ground rules

  • Focus on your personal contributions and decision rights within the project
  • You may use anonymized or redacted materials from prior work; do not build net-new strategy documents

Scoring anchors

Exceeds
Clearly maps trade-offs to user impact, demonstrates strong autonomous prioritization, and shows sophisticated handling of technical and operational constraints.
Meets
Presents a coherent end-to-end design, explains trade-offs clearly, and shows independent decision-making within feature scope.
Below
Lacks clarity on prioritization, defers decisions inappropriately, or ignores technical/user constraints in the routing experience.

Response time

20 min

Positive indicators

  • Articulates clear criteria for balancing data freshness, performance, and user needs
  • Demonstrates ownership of end-to-end flow without over-escalating decisions outside scope
  • Shows structured reasoning for handling technical constraints like latency or bandwidth limits

Negative indicators

  • Relies heavily on others for decisions within their defined autonomous scope
  • Fails to address how technical limits shaped the UX or rider expectations
  • Presents a linear process without acknowledging trade-offs, conflicts, or iteration

Work Simulation Scenario

Scenario. You are designing the UX for a new routing engine feature that calculates multi-modal journeys (bus, train, bike-share, walking) with real-time disruption handling. Riders frequently complain about anxiety when transfers are delayed or when the app shows conflicting arrival times. You are meeting with a senior engineering lead to scope the problem before drafting your solution.

Problem to solve. Define how to communicate routing uncertainty, manage rider expectations during disruptions, and design a fallback flow when real-time data is stale.

Format

discovery-interview · 35 min · ~2 hr prep

Success criteria

  • Clarify data latency thresholds and engine limitations
  • Identify key user anxiety triggers in multi-modal transfers
  • Outline a strategy for transparent communication of uncertainty without causing panic

What to review beforehand

  • Multi-modal transit routing basics
  • Common UX patterns for handling system uncertainty

Ground rules

  • Drive the conversation to uncover technical and user constraints
  • Discuss your approach to framing the problem and prioritizing tradeoffs
  • No deliverables expected, focus on reasoning

Roles in scenario

Senior Engineering Lead (informed_partner, played by hiring_manager)

Motivation. Wants a UX strategy that aligns with backend data capabilities and reduces support tickets caused by routing confusion.

Constraints

  • Routing engine updates every 30-90 seconds
  • Third-party bike-share APIs have 5-minute latency
  • Budget limits custom map rendering

Tensions to introduce

  • Explain that exact arrival times are mathematically impossible during peak disruption
  • Note that showing 'delayed' increases rider stress, but hiding it causes missed connections
  • Mention that the engineering team can only support 3 fallback states before performance degrades

In-character guidance

  • Provide precise latency numbers when asked
  • Be honest about what the backend can and cannot guarantee
  • Validate the candidate's focus on user psychology and transparency

Do not

  • Suggest specific UI copy or animation patterns
  • Volunteer API rate limits unless prompted
  • Steer the candidate toward a specific error-handling pattern

Scoring anchors

Exceeds
Deeply investigates data constraints, maps them directly to user anxiety triggers, and proposes a robust communication strategy that balances transparency with system limits.
Meets
Asks solid questions about latency and fallbacks, identifies key tradeoffs in uncertainty communication, and outlines a viable UX approach.
Below
Relies on idealized real-time scenarios, fails to ask about technical constraints, or proposes solutions that ignore rider stress and data limitations.

Response time

35 min

Positive indicators

  • Probes for exact data latency, API limits, and engine fallback behaviors
  • Surfaces assumptions about rider psychology and trust during disruptions
  • Articulates a clear framework for communicating uncertainty vs guaranteeing accuracy

Negative indicators

  • Assumes real-time accuracy is feasible without asking
  • Proposes complex UI states that exceed engineering constraints
  • Ignores the psychological impact of delayed or conflicting information

Progression Framework

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

Transit UX & Service Design

7 competencies

CompetencyJuniorMidSeniorPrincipal
Fare Payment & Ticketing UX

Tests fare payment flows and documents errors in ticketing transactions.

Designs secure and intuitive payment interfaces for web and mobile channels.

Integrates fare policies into UX flows and manages cross-platform payment consistency.

Leads strategy for account-based ticketing and multi-modal fare integration ecosystems.

Open Transit Data Standards

Implements predefined data schemas and validates feeds against standard specifications under supervision.

Independently configures data pipelines and resolves schema compliance issues for static and real-time feeds.

Designs data exchange protocols for new service types and ensures interoperability across agency systems.

Establishes organizational data governance policies and contributes to industry-wide standard evolution for transit information exchange.

Passenger Information Systems Design

Creates wireframes and visual assets for standard passenger information displays following style guides.

Develops interactive prototypes and conducts usability testing for information display interfaces.

Leads the design system strategy for multi-channel passenger information consistency and accessibility.

Defines the vision for integrated passenger information ecosystems across regional networks.

Transit Data Science & Analytics

Generates standard reports on user engagement metrics and design performance.

Interprets complex datasets to identify UX friction points and opportunities for improvement.

Designs data collection strategies to validate design hypotheses and measure ROI.

Establishes organization-wide metrics frameworks for design success and user value.

Transit Operations Management Support

Assists in documenting operational workflows and creating basic UI mocks for internal tools.

Designs interfaces for operational dashboards and incident management systems.

Optimizes operator workflows to reduce cognitive load and improve response times.

Defines the strategy for integrated operations control systems and human-machine interfaces.

Transit Planning & Policy Integration

Applies established policy guidelines to design artifacts and documents compliance requirements.

Translates planning constraints into functional design specifications and user flows.

Advises planning teams on user impact of policy changes and integrates feedback loops.

Aligns design strategy with long-term transit policy goals and regulatory frameworks.

Transit Routing Engines UX

Tests routing outputs for accuracy and documents user errors in trip planning scenarios.

Designs interface controls for routing preferences and optimizes search result displays.

Collaborates with engineering to tune routing parameters based on user behavior data.

Defines strategy for multi-modal routing integration and algorithmic transparency.