Where should I invest my learning time?" (my honest answer)


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 design?"
  • "Should I go deep on AI tools or fundamentals?"

Underneath, it's the same anxiety. I'm working hard. But am I working on the right thing?

Here's what I told them.


Stop asking "what should I learn?" Start asking three filters.

Filter 1: Does it compound?

Some skills reset to zero. A framework you learn today is legacy in 3 years. Some skills stack. Every system you understand makes the next one easier.

Filter 2: Does it survive AI?

AI writes code faster than you. It doesn't know your system's edge cases, your users, your production limits. Skills AI can do are getting cheaper. Skills that direct AI are getting expensive.

Filter 3: Can you show it?

A skill nobody sees in an interview or a promo discussion might as well not exist.


Now run the usual options through the filters.

The newest framework. Doesn't compound. Doesn't survive AI. Expires.

⚠️ DSA. You need it to clear screens. But it stops paying after that. AI solves LeetCode better than both of us.

System design. Compounds with every system you touch. AI can't do it for you — it doesn't know your constraints. And it shows up everywhere: senior interviews, design reviews, promo packets.

In 8+ years of hiring, I've rejected far more engineers for shallow design thinking than for failing to code.

Not because they couldn't build. Because they couldn't explain why: why this database, why this queue, what breaks at 10x.

That's the skill the market is repricing upward. Right now.

I put the three filters into one cheatsheet. Save it. Run your next "should I learn X?" decision through it.


Which filter does your current learning plan fail? Hit reply and tell me. I read every response.

P.S. Next Thursday's issue is the biggest one I've sent all year. Keep an eye out.

Thanks,

Abhishek

The Guided Growth

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.

Read more from The Guided Growth
What happens after your interview ends?

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 #4: 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 I wait until the last 10 minutes of every interview. The candidate has done their coding round. Their system...

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....