|
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. Here's what most candidates don't know. After your interview ends, I open a form. At Google it was a structured doc. At other companies, similar versions. The form doesn't ask "did they solve it?" It asks things like:
That last one is the real question. Everything else builds toward it. I've seen candidates who struggled with the optimal solution but got a "Strong Hire." Because when they got stuck, they talked through it. They said "I'm not sure, but here's how I'd think about it." They treated the interview like a conversation, not a performance. And I've seen candidates who nailed everything but felt like they were reciting. Perfect answers. Zero signal on how they think under pressure. The debrief is where it gets interesting. Four interviewers sit in a room. Sometimes two say hire, two say no. What happens then? The hiring manager looks for signal, not consensus. One interviewer saying "they asked me a question I hadn't thought of" weighs more than four people saying "they solved it." Interviewers don't remember your code after a week. They remember how you handled the moment you didn't know something. That's the part nobody preps for. Because no YouTube video teaches you how to be stuck gracefully. If you're interviewing soon, then stop optimising for answers. Start optimising for the 30 minutes after you leave the room. That's where the decision happens. I'm hosting a small in-person meetup in Bangalore next weekend. 6-10 people. No slides, no panels. Just real conversations about careers, interviews, and the stuff you don't post about online. If you want in: https://forms.gle/7hNw34F3GmjmVjYG7 Either way, keep going. 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...