Hey Reader,

Welcome back to Guided Growth where we talk about the skills that accelerate your career beyond just writing great code.

You spent 3 months on the analytics dashboard.

Nights. Weekends. Shipped perfectly.

Promotion cycle: Not mentioned.

Your peer wrote a design doc in 2 weeks. Got promoted to Staff.

I've reviewed 47 promotion packets. Pattern is clear:

Only 4 types of projects get you promoted.

THE 4 PROJECTS THAT MATTER

1. Multiplier Projects

Make your team 2x more effective.

Examples:

• Deployment automation (reduced release time 60%)
• Onboarding playbook (cut ramp-up from 6 weeks to 2)
• Testing framework everyone uses

Build once. Team wins forever.

2. Scope Expansion Projects

Solve problems beyond your team.

Examples:

• Cost optimization across 3 teams (saved ₹80L)
• API standards adopted org-wide
• Interview training program

Visibility beyond your manager's manager.

3. Fire Prevention Projects

Stop future incidents, not just fight current ones.

Examples:

• Load testing framework (prevented 4 outages)
• Incident runbooks (reduced MTTR 40%)
• Tech debt paydown with business case

Proactive beats reactive.

4. Teaching Projects

Your knowledge × other people = leverage.

Examples:

• Internal tech talks (30+ engineers trained)
• Mentoring 2-3 engineers formally
• Documentation that becomes team standard

Senior engineers solve problems. Staff engineers multiply problem-solvers.

WHAT DOESN'T GET PROMOTED

Sprint tasks. Bug fixes. Features only your team sees.

They're expected. You get promoted for doing the NEXT level's job.

THE TEST

Ask yourself: Will this matter in 6 months?

If no → Maintenance work. Do it efficiently.

If yes → Promotable work. Make it visible.

Busy all year. Invisible at review.

That was me. Don't be me.

YOUR MOVE THIS QUARTER

Pick ONE from each category:

Multiplier:​
□ What slows your team down weekly? Build the fix.

Scope Expansion:​
□ What problem do 3+ teams have? Solve it once.

Fire Prevention:​
□ What keeps breaking? Fix the root cause with data.

Teaching:​
□ What do you know that others need? Document it or teach it.

Start this week. Track in your brag doc.

When promotion time comes, your manager will have 4 ready examples.

What's ONE project you're starting this quarter?

Reply with what you picked—I want to hear it.

And if you want help actually executing (not just planning):

I'm running The Guided Growth community for engineers who are done being stuck.

₹499/month. No fluff. Just:

• Weekly accountability check-ins (so your projects don't die in week 3)
• Project selection feedback (before you waste 3 months on the wrong thing)
• Brag doc templates + resume reviews
• 400+ engineers who've been exactly where you are

Since you'd be among the early members, you get a more direct line to me as we shape this together.

We're keeping it small to start with. This lets me work closely with everyone.

No pressure at all. Just sharing in case this gives you the structure you need.

Either way, keep going. The effort you're putting in will compound.

– Abhishek

Small shifts. Big results.

Forward this to someone stuck at Senior Engineer for 2+ years.