One of the most thought-provoking questions came during the technical round: “How would you design a self-healing system for a high-traffic payment infrastructure, and what metrics would signal true resilience?” It wasn’t just a design question—it was a test of mindset. I spoke about proactive anomaly detection using telemetry pipelines, a fallback architecture driven by service degradation levels, and the use of SLOs mapped to customer-facing impact metrics. But beyond the engineering, I emphasized my belief in building systems that carry empathy—for users, for developers, for the edge cases that often get ignored. That question stayed with me because it wasn’t just about code—it was about the philosophy behind reliability.