Transit TechExpert-built kit

Transit Technology Business Analyst

Documents payment API specifications, configures fare rules, and validates daily transaction settlement logs.

Buy this kit · $29.99Preview questions

Interview content for Mid

29
What to ask. Competency and attitude questions, assigned to the right round.
238
What to listen for. Written indicators to credit and discount, per question.
7
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 Technical16 competency questions

Transit Technology Solutions

Fare Payment Systems

Configures fare products and manages vendor relationships for payment processing.

Expected at Mid

Sample competency question

Describe a time you managed requirements for a revenue collection integration involving multiple stakeholders.

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

Credit

  • Mapped out all transaction states
  • Involved finance team early
  • Addressed error handling explicitly
  • Validated settlement processes
  • Documented audit trails

Discount

  • Overlooked finance team involvement
  • Ignored settlement timing
  • No plan for failed transactions
  • Vague on security requirements
  • Failed to document audit needs

Fare payment systems represent a specialized domain where mid-level BAs coordinate vendor inputs and manage configurations under guidance, ensuring alignment with broader project goals without requiring full independent ownership. This approach prevents configuration errors and vendor coordination delays while building foundational knowledge for future revenue-focused assignments.

Ryan Mahoney

Why this role is hard · Ryan Mahoney

The hardest part of hiring at this level is finding someone who can turn messy transit rules into clean code without losing the nuance. They need to sit in a room with a city agency and understand why a fare policy exists before they write a single ticket. Most candidates know how to gather requirements, but few understand how a change in fare logic breaks the backend data pipeline. Since they work without daily oversight, they have to spot system connections on their own. We need people who listen more than they talk and see the links before they propose solutions.

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

Level guides for Junior, Mid, Senior and Principal.

Before you post

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

In the room

  • 16Competency 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.

16 Competency Questions

1 of 16

  1. Discipline

    Transit Technology Solutions

  2. Job requirement

    Fare Payment Systems

    Configures fare products and manages vendor relationships for payment processing.

  3. Expected at Mid

    Fare payment systems represent a specialized domain where mid-level BAs coordinate vendor inputs and manage configurations under guidance, ensuring alignment with broader project goals without requiring full independent ownership. This approach prevents configuration errors and vendor coordination delays while building foundational knowledge for future revenue-focused assignments.

Interview round: Hiring Manager Technical

Describe a time you managed requirements for a revenue collection integration involving multiple stakeholders.

Positive indicators

  • Mapped out all transaction states
  • Involved finance team early
  • Addressed error handling explicitly
  • Validated settlement processes
  • Documented audit trails

Negative indicators

  • Overlooked finance team involvement
  • Ignored settlement timing
  • No plan for failed transactions
  • Vague on security requirements
  • Failed to document audit needs

13 Attitude Questions

1 of 13

Active Listening

The disciplined practice of fully concentrating on, understanding, and responding to stakeholders during transit technology interactions, ensuring that operational realities, safety constraints, and user experiences are accurately captured and validated before technical solutions are formulated.

Interview round: Recruiter Screen

Share an experience when you realized mid-meeting that you had misunderstood a key operational constraint.

Positive indicators

  • Stops meeting to clarify the constraint
  • Thanks stakeholder for the correction
  • Updates notes in real-time

Negative indicators

  • Continues meeting based on wrong assumption
  • Argues against the constraint initially
  • Notes correction for later without addressing it

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 professional experience validating transit schedule data against GTFS (General Transit Feed Specification) standards?

Yes
Qualifies
No
Auto-decline

Video-Response Questions

1 of 3

Application Screen: Video Response

You discover that a critical real-time data integration will miss an upcoming launch deadline due to underlying latency constraints. How would you communicate this delay and its impact on passenger experience to the executive leadership team, and what alternative solution or mitigation would you propose?

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 end-to-end lifecycle of specific product features, prioritizing backlog items, approving minor requirement changes, and coordinating delivery without daily oversight.
Defines and documents vendor API specifications, data contracts, and system endpoints to enable seamless third-party integrations and open payment or mobility platform interoperability.
Converts real-world operational rules, fare policies, or delay codes into backend logic, system requirements, or alert triggers using structured modeling and SQL validation.
Coordinates user acceptance testing cycles, tracks defects, and partners with engineering to troubleshoot real-time data pipeline or system failures during live operations.

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

Walk us through a past project where you independently managed stakeholder requirements for a transit technology feature. Discuss how you translated conflicting operational constraints into technical specifications, prioritized the backlog, and handled scope changes.

Format

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

Audience

Product Manager and Technical Lead

What to prepare

  • 3-5 slides summarizing the project context, your decision-making process, and the outcome.
  • Talking points on stakeholder negotiation and scope management.

Deliverables

  • A short deck and a 15-20 minute walkthrough with Q&A.

Ground rules

  • Use only work you are permitted to share; anonymize sensitive agency or vendor data if necessary.
  • Focus on your reasoning and decision framework, not just the final deliverable.

Scoring anchors

Exceeds
Strong stakeholder alignment, clear tradeoff documentation, and proactive risk mitigation with measurable outcomes.
Meets
Solid prioritization framework, handles scope reasonably, and provides clear, actionable technical specifications.
Below
Poor requirement translation, reactive scope management, and unclear decision logic or stakeholder communication.

Response time

20 min

Positive indicators

  • Clearly links business constraints to specific technical specifications
  • Demonstrates explicit tradeoff reasoning for backlog prioritization
  • Shows evidence of professional boundary-setting on scope changes
  • Communicates technical impacts clearly to non-technical stakeholders

Negative indicators

  • Vague on prioritization criteria or decision rationale
  • Accepts scope creep without documented pushback or tradeoffs
  • Uses technical jargon without translating to business impact
  • Fails to document or explain stakeholder alignment steps

Work Simulation Scenario

Scenario. You are leading the rollout of a new mobile wallet integration for fare payments. The agency's operations manager is pushing back on the proposed UAT timeline, citing staff shortages and a recent system upgrade that disrupted training cycles. You need to align on a feasible testing plan that ensures compliance and user readiness without derailing the launch.

Problem to solve. Negotiate a realistic UAT schedule and scope that satisfies compliance requirements, addresses the operations manager's capacity constraints, and maintains launch readiness.

Format

stakeholder-roleplay · 35 min · ~2 hr prep

Success criteria

  • Secure agreement on a phased UAT approach that respects operational limits
  • Define clear success metrics and escalation paths for testing blockers
  • Maintain compliance boundaries while demonstrating flexibility on non-critical items

What to review beforehand

  • UAT best practices for transit payment systems
  • Stakeholder negotiation frameworks
  • Compliance requirements for fare technology rollouts

Ground rules

  • You will drive a 1:1 conversation with the operations manager
  • Focus on active listening, clear communication, and boundary setting
  • Do not produce a written plan; instead, discuss your approach and reach verbal alignment

Roles in scenario

Agency Operations Manager (skeptical_stakeholder, played by cross_functional)

Motivation. Protect frontline staff from burnout and avoid repeating past training failures while still meeting agency payment modernization goals.

Constraints

  • Only 15 staff members available for testing over the next 4 weeks
  • Mandatory compliance audit occurs 2 weeks post-launch
  • Recent system upgrade consumed 60% of available training hours

Tensions to introduce

  • Resist any request for weekend or after-hours testing without overtime approval
  • Push for a reduced test scope to prioritize critical payment flows
  • Express frustration over past projects that ignored operational feedback

In-character guidance

  • Acknowledge the candidate's points but emphasize capacity limits
  • Agree to phased testing if core compliance requirements are explicitly addressed
  • Remain professional but firm on non-negotiable staffing boundaries

Do not

  • Do not concede on overtime or staffing limits without a clear operational justification
  • Do not provide a pre-written UAT schedule
  • Do not escalate hostility or dismiss the candidate's compliance concerns

Scoring anchors

Exceeds
Successfully aligns operational reality with compliance needs, secures a phased UAT agreement with explicit boundaries, and establishes a clear communication cadence for ongoing testing.
Meets
Listens to constraints, proposes a reasonable phased plan, and maintains compliance boundaries while showing flexibility on non-critical testing elements.
Below
Ignores operational capacity limits, communicates ambiguously about compliance, or capitulates to scope changes without adjusting expectations or resources.

Response time

35 min

Positive indicators

  • Actively listens to operational constraints and reflects them back before proposing solutions
  • Clearly communicates compliance requirements and distinguishes them from flexible scope items
  • Sets firm, respectful boundaries on timeline and resource expectations
  • Proposes a phased, risk-based UAT approach that aligns with available capacity

Negative indicators

  • Dismisses operational pushback as resistance to change
  • Uses vague language about compliance deadlines or testing success criteria
  • Yields to scope creep without adjusting timeline or documenting tradeoffs
  • Fails to establish clear escalation paths or decision authority

Progression Framework

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

Transit Technology Solutions

7 competencies

CompetencyJuniorMidSeniorPrincipal
Fare Payment Systems

Supports fare table configuration and troubleshoots basic payment terminal issues, ensuring transaction processing accuracy and revenue system integrity.

Configures fare products and manages vendor relationships for payment processing.

Designs fare policy integration into technology systems and oversees security compliance.

Defines regional fare integration strategies and negotiates enterprise payment contracts.

Mobility-as-a-Service

Supports partner onboarding and tracks service level agreements, monitoring subscription usage and integration performance across mobility services.

Coordinates integration projects with external mobility providers.

Designs MaaS ecosystems and negotiates complex partnership contracts.

Drives regional mobility strategy and defines interoperability standards for partners.

Quality & Compliance

Executes test cases and documents compliance evidence for audits, ensuring system quality, security protocols, and regulatory adherence.

Develops test plans and monitors security protocols for system updates.

Leads quality assurance strategy and manages regulatory risk assessments.

Establishes enterprise governance frameworks and ensures industry compliance standards.

Route Optimization

Assists in updating route schedules and mapping changes based on supervisor direction, supporting schedule maintenance and geospatial data updates.

Analyzes route performance metrics and proposes schedule adjustments.

Leads network redesign projects and implements optimization algorithms.

Sets long-term network strategy and integrates multimodal optimization frameworks.

Transit Analytics

Generates standard reports and cleans datasets for analysis using established templates, supporting operational monitoring and KPI tracking activities.

Conducts trend analysis and identifies operational anomalies using statistical methods.

Develops predictive models and dashboards to guide operational improvements.

Architects enterprise analytics strategies and defines key performance indicators for the organization.

Transit App Development

Tests app features and documents user feedback for the development team, supporting QA testing and accessibility validation activities.

Manages app release cycles and coordinates UI/UX improvements.

Defines app architecture and integrates third-party mobility services.

Sets digital product vision and aligns app strategy with organizational goals.

Transit Data Standards

Documents data requirements and validates entries against existing standards under supervision, ensuring GTFS feed accuracy and compliance with established specifications.

Independently manages data specification updates and ensures compliance across project modules.

Designs data architectures and establishes standards for new transit technology integrations.

Defines industry-wide data strategies and governs complex multi-vendor standardization efforts.