|
Hey Reader, Welcome back to Guided Growth where we talk about the skills that accelerate your career beyond just writing great code. This is The Unwritten Rules #4: a 4-part series where I share the career rules that exist but nobody shared them with you.
I wait until the last 10 minutes of every interview. The candidate has done their coding round. Their system design. They're mentally tired. Guard is down. Then I ask: "Tell me about a time you were wrong about something at work. What happened?" Simple question. No trick. And it's the most revealing question I've ever used. I hear four types of answers: 🔴 The Deflector:"I can't think of a specific time." This tells me they'll hide problems on my team. 🟡 The Blamer:"A deployment broke production, but QA didn't catch it and the requirements were unclear." Takes credit for wins, passes blame for losses. 🟡 The Performer:"I chose React when Vue would've been better." Safe. Rehearsed. The interview-prep version of a mistake. I learn nothing real. 🟢 The Real One:"I pushed hard for a full rewrite of a legacy service. My tech lead said refactor incrementally. I argued. We went with my approach. Three months in, it was blocking other teams. We scrapped it. I wasted the team's time because I was too attached to my solution." That last answer tells me everything. Here's why it works:
I'm not hiring someone who never makes mistakes. That person doesn't exist. I'm hiring someone who handles mistakes well. That one question tells me which type you are. In 2 minutes. This was the final Unwritten Rule. If this series helped you, forward the issue that helped you most to a friend who's interviewing. That's the best way to help them and to grow this newsletter. Thanks, Abhishek The Guided Growth |
Ex-Google | Stanford LEAD | Ex-Founder | Sr. Engineering Manager. Career systems for engineers who want FAANG offers, faster promotions, and leadership roles. 650+ interviews conducted, 1,100+ engineers mentored. Read by 178,000+ engineers across platforms.
Hey Reader, I study every single day. You might assume I have a free hour somewhere. I don't. My workday is full, and my evenings have calls. So I don't look for a free hour. A book I am reading right now says it in one line. You don't need more time. You need better systems. The book is How to Be Good at Life, by my friend Ben Meer. I am part way through it, and it has 40+ systems like the one I am about to show you. You can get it here. Here is my system. It has 3 slots. The gap after...
Hey Reader, Two weeks ago I posted: build your exit on day one. This is the day it paid off for me. I had joined Flipkart a few months earlier. I was not looking. I was still learning where things were. A Google recruiter messaged me on LinkedIn. Then called. Would I interview? They offered me two months to prepare Most people take it. I had a reason not to. I had a medical procedure booked about three and a half weeks out. Recovery would take time, and I was not going to cut it short for...
Hey Reader, Over the last two weeks I posted how WhatsApp works, in four blocks. This is what I see when I ask someone to build it in an interview. I sit on the other side of that table often. What follows is a composite. Not one person. A pattern. It does not matter what I ask Design WhatsApp. Design a parking lot. Design a URL shortener. The question changes. The failure does not. The candidate nods. Then, inside the first two minutes: load balancer. Database. Cache. Queue. Each word is...