← Via Transportation Interview Insights

Via Transportation·Software Engineer·Hiring Manager Screen·Intermediate

Intermediate
Jun 2026

Summary

Interviewed for a bizops role at Via Transportation and got hit with a classic ops crisis scenario. Pretty straightforward round but the question had more layers than I expected.

Questions Asked (1)

Q1

You're launching in a new city today and none of your drivers show up. What do you do?

Adaptability & AmbiguityGo-to-Market (GTM)Root Cause Analysis
Author's notes

I jumped straight into triage mode and started listing contingency plans, but I think I missed the bigger point at first.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Show that you can stay calm, prioritize immediate customer and driver needs, and systematically diagnose the root cause while communicating transparently. Emphasize that as a software engineer, you'd leverage data and tools to understand the issue and coordinate with operations to mitigate impact.

Pro tip: Demonstrate that you think beyond quick fixes: propose a blameless post-mortem and preventive measures, and highlight how engineering can build resilience into the system to avoid similar failures.

1. Assess and Communicate

Quickly assess the situation: how many drivers are missing, impact on customers, and any immediate safety concerns. Communicate transparently with stakeholders (ops, customers) about the issue and expected delays.

2. Mitigate Impact

Implement short-term fixes: activate backup drivers, adjust pricing or incentives, or pause new ride requests. Coordinate with operations to manage customer expectations and minimize disruption.

3. Diagnose Root Cause

Investigate why drivers didn't show up: check app notifications, driver communication logs, payment systems, or external factors. Use data to identify if it's a technical bug, operational issue, or external event.

4. Implement Fix and Monitor

Once the root cause is identified, deploy a fix (e.g., push notification, bug patch) and monitor driver response. Keep stakeholders updated on progress.

5. Learn and Prevent

Conduct a blameless post-mortem to understand what happened and why. Implement preventive measures such as better driver onboarding, redundant communication channels, or automated alerts for low driver availability.

Key Points to Mention

  • Prioritize customer safety and experience while resolving the issue.
  • Use data and engineering tools to diagnose the root cause quickly.
  • Collaborate cross-functionally with operations, support, and marketing teams.
  • Communicate transparently with all stakeholders to maintain trust.
  • Implement both immediate mitigations and long-term preventive solutions.
  • Conduct a blameless post-mortem to learn and improve system resilience.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.