Safety Operations Specialist (Fleet Support)
virtual
· Dificultad 2/5
Candidates commonly report an initial phone screen covering shift availability, comfort with operational procedures, and interest in autonomous fleet support. Next steps often include virtual interviews that assess situational judgment, adherence to process, and communication under time pressure. Some processes include role-play or scenario-based questions about incident handling, escalation, and documenting actions accurately. The overall timeline is often described as relatively quick compared with engineering roles, with scheduling influenced by operational hiring needs.
- Describe a time you had to follow a strict procedure even when you believed a faster workaround existed. What did you do and why?
- If a vehicle reports an unexpected stop in service, what immediate steps would you take to assess the situation and escalate appropriately?
- How would you communicate a developing incident to multiple stakeholders while keeping details accurate and consistent?
- Given a set of event logs and timestamps, identify what information is missing to complete an incident report and what questions you would ask next.
Technical Program Manager, Vehicle Programs
virtual
· Dificultad 3/5
The process often starts with a recruiter conversation to confirm program scope fit, stakeholder experience, and comfort operating in a regulated, safety-first environment. Candidates then report one or more interviews with hiring managers or peer TPMs that emphasize structured execution, risk management, and cross-functional leadership across hardware, software, and operations. A longer panel round is commonly used to test communication, prioritization, and ability to drive decisions amid ambiguity, sometimes using scenario prompts tied to vehicle readiness or deployment milestones. Candidates frequently mention that team matching and alignment on program ownership can extend the overall timeline.
- Walk through how you would build and run an end-to-end program plan for a vehicle platform milestone, including dependencies across hardware, autonomy software, and fleet operations.
- Describe a time you uncovered a hidden risk late in a program. What signals did you use, and how did you drive mitigation?
- How do you define and track readiness metrics for a safety-critical launch when different teams optimize for different outcomes?
- How do you handle conflict when engineering leadership wants to move fast but safety and compliance partners are not comfortable with the evidence quality?
Software Engineer, Autonomy (Perception/Prediction)
virtual
· Dificultad 4/5
The process typically begins with a recruiter screen focused on role scope, location or onsite expectations, and alignment with autonomy domains. Candidates report one or two technical screens that can include core coding, data structures and algorithms, and domain-adjacent problem solving relevant to perception or ML systems. A virtual onsite often follows with multiple back-to-back interviews covering coding, system design, and collaboration scenarios, with some loops adding ML fundamentals or debugging discussions. Timelines vary, but candidates commonly describe a multiweek process with scheduling dependent on panel availability and team matching.
- Implement an efficient function to detect overlaps among time-stamped intervals and return the merged set, discussing complexity tradeoffs.
- Design a real-time data pipeline for ingesting sensor events and serving features to an on-vehicle model with latency and reliability constraints.
- How would you diagnose a sudden drop in perception recall after a model update when only limited on-road logs are available?
- Describe a time you disagreed with a safety or quality requirement and how you aligned with stakeholders to resolve it.