Search candidates, jobs, people
Interviews

Interview kit · iv-708

Onsite loop: Lukas Brandt

Senior Robotics Software Engineer · Autonomy

Date
Tue, Oct 20
Time (ET)
9:00 AM – 1:00 PM
Length
4 h
Where
Pittsburgh HQ
Status
In progress

9:00 AM – 1:00 PM · 4 h

Timing

  1. 9:00 AM1 h 15 minSystem designDev Malhotra
  2. 10:15 AM1 h 15 minCode review exerciseMei Chen
  3. 11:30 AM15 minBreak
  4. 11:45 AM1 h 15 minValues conversationHannah Becker

Interview kit

Questions by competency

Rated 1–4 on the scorecard

Onsite loop: exercises

  • System design: right-of-way between 40 robots and human pickers.
  • Code review of a real (sanitized) planner change.
  • Field-log deep dive with the Autonomy team.
  • Values conversation with the VP of Engineering.
  1. 01

    Robotics software design

    Breaks a planning problem into clean, testable modules.

    • Design right-of-way rules for 40 robots and human pickers in one aisle network.
    • How would you structure a planner so it can be tested without a robot?
  2. 02

    C++ and systems

    Writes safe, fast code; reasons about memory, threads and real-time limits.

    • Where would you expect latency in a 50 Hz planning loop, and how would you find it?
    • Walk through a memory or threading bug you shipped and fixed.
  3. 03

    Debugging on hardware

    Finds root causes from logs, bags and a robot that won't behave.

    • A robot oscillates at an aisle intersection. Walk through your debugging.
    • What do you look for first in a field log?
  4. 04

    Collaboration

    Works through disagreement; explains trade-offs to non-specialists.

    • Tell us about a design disagreement and how it was resolved.
    • How do you explain a trade-off to a customer or an operator?
  5. 05

    Ownership

    Follows problems into the field and closes the loop.

    • Describe a problem you followed from a bug report all the way into the field.
    • What did you do after the last incident you were part of?

Interview in progress

Scorecard

Submitting as Dev Malhotra

You can draft now; it submits after the interview ends. Other panelists' scorecards stay hidden until you submit.

Robotics software design
C++ and systems
Debugging on hardware
Collaboration
Ownership
1 Strong concerns2 Some concerns3 Meets the bar4 Exceeds the bar
Recommendation

Write what you saw and heard, not impressions. Stick to the competencies above.

0 of 3 in

Submitted scorecards

No scorecards yet. They appear here once each panelist submits.