1 min read

Another interview question that I failed

Interview Question: "Could you describe a time where you didn't have enough data and decided to make a decision that you later regretted?"

I got stuck when I was asked this question in an interview today and couldn’t come up with an example on the spot. But reflecting on it now, I realize there have been several such instances in my career. A key theme I’ve learned over time—especially as a factory test engineer—is to trust, but always verify.

One example that stands out is from my time at Humane. I regret not voicing my concerns earlier regarding software and hardware integration. At the time, we were following Apple’s process of developing hardware and software separately, and no one really questioned whether the two would converge effectively. Because I was working on factory OQC (Outgoing Quality Control) tests, I was responsible for getting the full product working at the end of the line.

Eventually, we had to set up very manual test methods using the OOBE (Out of Box Experience) flow to validate key features of the device. But by then, it was too little, too late—it became clear the product had design flaws that could have been addressed much earlier.

  • Context: I was responsible for setting up end-of-line and OQC testing at the factory.
  • Action: I began engaging with the software team to align on software readiness and determine when we could flash a usable version of user software onto the hardware.
  • Result: We didn't get a stable image until right before MP (Mass Production), which limited our ability to influence design changes.
  • Learning: I should have pushed much earlier—ideally during EVT (Engineering Validation Testing)—to integrate and validate software on hardware. That would have given the team time to iterate on the design based on real test feedback.