|
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, Welcome back to Guided Growth where we talk about the skills that accelerate your career beyond just writing great code. Last month I hosted a meetup in Bangalore. Engineers from PhonePe, Goldman Sachs, Dell, Deloitte. Some with 2 years of experience. Some with 12. One on a career break, fighting her way back in. Different companies. Different levels. Same question. "Where should I invest my learning time?" It came in different costumes: "Should I stay or switch?" "DSA or system...
Hey Reader, Welcome back to Guided Growth where we talk about the skills that accelerate your career beyond just writing great code. Last month I interviewed someone who solved every question I asked. Clean code. Good structure. Explained the approach before writing it. I wrote "No Hire." Not because the answers were wrong.Because I couldn't tell if this person could think or just prepared well. Here's what most candidates don't know. After your interview ends, I open a form. At Google it was...
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 #3: a 4-part series where I share the career rules that exist but nobody shared them with you. What do you think matters MOST in the final interview round? Coding skills System design depth Cultural fit Communication skills Last month, I gave two candidates the same debugging problem. A piece of code with a subtle concurrency bug....