Shipmind Labs

Years back one of our engineers went quiet on a payments service for a few days. They had hit a reconciliation mismatch, assumed it was their own bug, and kept digging alone. It was not their bug. It was upstream, and the people handling customer money needed to know that morning, not later.

So the last part of every interview now is one question: tell us about something that broke in production. We barely listen to the fix. We listen for when they told someone, and who they told.

Good engineers debug quietly. The ones you can hand a live service to will say it out loud, early: they do not understand what they are seeing yet, but here is what they are seeing. That instinct is almost impossible to train in, and very easy to hear in ten minutes.

That is the one question we would never skip when hiring.

Was this useful?

Building something similar?

or email hello@shipmindlabs.com