Question 3 is my least favorite because I feel compelled not to lie. If I decided to lie, I'm sure I could concoct a story to sound really impressive. Most of

Question 3 is my least favorite because I feel compelled not to lie. If I decided to lie, I'm sure I could concoct a story to sound really impressive. Most of the problems I solve are along the lines of 'some edge condition that wasn't accounted for in the code, often by someone else, and I spent a day figuring it out and fixing it' and there's not generally a lot of complexity or depth to it. I'm from a systems engineering background, so most of what I do is preventing large headaches in the first place. I've worked for large companies, so we hit stupid platform bugs, you won't believe this: we actually had dev and stage environments where we caught most things. Most of the problems were 'developers new application version is crap, please fix what we broke' type of stuff. The other limiting factor to working on large orgs is you generally have actual support contracts with vendors. Oh, my packets are leaving the interface but not arriving at the destination? Well, network team looks into that, cause you know, there's an actual network team. And then when they determine everything is setup right, they forward to the vendor. And then Cisco is like 'looks like these network cards are crap, buffer overflow, new firmware' and then it's problem fixed. Anyway, writing all this has motivated me to construct something fancy about metrics and latency.