Accelerated Job Search Plan — Apply and Prep in Parallel

Goal: Start applying while preparing in parallel for maximum efficiency. This is your action plan. Follow it step by step.

Mindset Reset (Read This First)

You are not starting from zero. You have:

• 5 years of real production experience as a sole backend engineer
• Stories most candidates would kill for: 2.3 billion rows in PostGIS, 5.3 TB tile service, multi-terabyte data pipelines
• Python + Rust + PostgreSQL + AWS — this is a premium stack
• Actual startup experience — you’ve worn every hat

The prep documents polish how you communicate what you already know. They don’t teach you how to do your job — you’ve been doing it for 5 years.

The #1 mistake people make: waiting until they feel “ready” to apply. You will never feel ready. Apply now. Prep in parallel. Get sharper with each interview.

The 3-Track System

You run three tracks simultaneously, not sequentially.

flowchart LR
    A["📨 <b>TRACK 1: APPLY</b><br/>3–5 apps/day<br/>Starts Day 1"] --> D["🎯 Interviews<br/>Scheduled"]
    B["📚 <b>TRACK 2: HIGH-ROI PREP</b><br/>Most-tested topics<br/>Starts Day 1"] --> D
    D --> C["🔬 <b>TRACK 3: DEEP PREP</b><br/>Remaining topics<br/>Starts when interviews<br/>are scheduled"]

Track 1: Apply Immediately (Day 1)

Step 1 — LinkedIn (30 minutes, do it today)

• Turn on “Open to Work” (recruiters only, NOT public)
• Update headline to: Backend Engineer | Python · Rust · PostgreSQL · AWS | Open to Opportunities
• Make sure your experience section mirrors your resume bullets
• Set job preferences: Backend Engineer, Software Engineer, SDE — Remote/Hybrid — India
• Connect with 10-15 recruiters who post backend/startup roles

Step 2 — Job Platforms (set up profiles)

Step 3 — Daily Application Rhythm

Target: 3-5 quality applications per day (not spray-and-pray)

For each application:

1. Read the job description for 2 minutes
2. Check if 60%+ of requirements match your skills (if yes, apply)
3. Tailor ONE line in your cover letter/intro to their product (takes 3 min)
4. Apply and log it in the tracker below
5. Move on — don’t overthink

Step 4 — Application Tracker

Create a simple spreadsheet or use the table below:

| Company | Role | Applied Date | Source | Status | Follow-up Date | Notes |
|---------|------|-------------|--------|--------|---------------|---------|
|         |      |             |        |        |               |         |

Status values: Applied → Phone Screen → Technical → System Design → Behavioral → Offer → Rejected

Step 5 — Cold Outreach Template

For startups, direct messaging founders/CTOs on LinkedIn works surprisingly well:

Hi [Name],

I'm a backend engineer with 5+ years building production systems — Python, 
PostgreSQL, AWS, and some Rust. I was the primary backend engineer at a climate 
tech startup where I built data pipelines processing multi-terabyte datasets and 
APIs serving hundreds of concurrent users.

I noticed [Company] is [something specific about their product/tech]. I'd love 
to chat about how I could contribute to your backend/infra as you scale.

Happy to share more about my work: jadhav.dev

Best,
Karan

Customize the middle line for each company. Everything else stays the same.

Track 2: High-ROI Prep (First 5 Days)

These are ordered by impact per hour of study time. This covers ~80% of what interviews actually test.

Day 1 (2-3 hours total)

Day 2 (3-4 hours total)

Day 3 (3-4 hours total)

Day 4 (3-4 hours total)

Day 5 (3-4 hours total)

After Day 5, you’re ready for most first-round interviews.

Track 3: Deep Prep (Days 6-14, While Interviews Are Scheduling)

Interview pipelines take 1-3 weeks. Use that time for deeper prep:

LeetCode Schedule (Ongoing)

Week 1: 2 problems/day (mostly Easy, some Medium)
Week 2: 2 problems/day (mostly Medium)
Week 3+: 2-3 problems/day (Medium + occasional Hard)

Focus on PATTERNS, not problem count:
1. Arrays + Hashing        → 5 problems
2. Two Pointers            → 4 problems
3. Sliding Window          → 4 problems
4. Binary Search           → 4 problems
5. Stack                   → 3 problems
6. Trees (BFS/DFS)         → 5 problems
7. Graphs                  → 5 problems
8. Dynamic Programming     → 5 problems (only Medium)
9. Linked Lists            → 3 problems
10. Heap/Priority Queue    → 3 problems

Daily Schedule Template

If You’re Currently Employed

flowchart TD
    A["🌅 <b>MORNING</b> · before work · 1 hour<br/>• 1–2 LeetCode problems<br/>• Review yesterday's notes (10 min)"]
    B["🍽️ <b>LUNCH BREAK</b> · 30 min<br/>• Apply to 2–3 jobs<br/>• Quick LinkedIn check for messages"]
    C["🌙 <b>EVENING</b> · after work · 2 hours<br/>• Study one prep document section (1.5 hr)<br/>• Practice one behavioral story out loud (15 min)<br/>• Apply to 2–3 more jobs (15 min)"]
    D["📅 <b>WEEKEND</b> · 4–5 hours/day<br/>• Deep study: system design or full topic review<br/>• Mock interview (Pramp/friend)<br/>• Batch applications"]
    A --> B --> C --> D

If You’re Between Jobs (full-time prep)

flowchart TD
    A["9:00–10:00 · <b>Applications</b> (3–5 jobs)"]
    B["10:00–10:15 · Break"]
    C["10:15–12:15 · <b>Study prep documents</b>"]
    D["12:15–1:15 · Lunch + walk 🚶"]
    E["1:15–2:45 · <b>LeetCode</b> (2–3 problems)"]
    F["2:45–3:00 · Break"]
    G["3:00–4:00 · <b>System design practice</b>"]
    H["4:00–4:30 · <b>Behavioral story rehearsal</b>"]
    I["4:30–5:00 · Review + notes"]
    J["🌙 Evening: REST. Watch something. Talk to people.<br/><i>Burnout is your enemy. Protect your energy.</i>"]
    A --> B --> C --> D --> E --> F --> G --> H --> I --> J

Pre-Interview Checklist (Night Before)

Use this checklist before every interview:

• Researched the company: what they build, tech stack, recent news, funding stage
• Prepared 2-3 questions to ask THEM (shows genuine interest)
• Reviewed the job description — mapped your experience to their requirements
• Rehearsed your “tell me about yourself” (90 seconds, practiced out loud)
• Rehearsed 3 STAR stories relevant to this role
• Reviewed power keywords from 11-interview-power-keywords.md
• Tested audio/video/internet if it’s a video call
• Have water, pen, paper ready
• Portfolio site (jadhav.dev) and GitHub are presentable
• Slept well (seriously — a rested brain performs 2x better than a crammed one)

The 90-Second “Tell Me About Yourself”

Memorize this structure. Customize for each company:

"I'm Karan, a backend engineer with over 5 years of experience.

I've spent my career at a climate tech startup called Intensel, where I was 
the primary backend engineer. I owned everything from API design to database 
architecture to AWS infrastructure.

Some highlights: I built data pipelines processing multi-terabyte climate 
datasets, optimized PostgreSQL queries on 2.3 billion spatial records — 
bringing latency from seconds to milliseconds — and designed a tile delivery 
service handling 5.3 terabytes of geospatial data at scale.

My core stack is Python and PostgreSQL, but I also work with Rust — I'm 
building an open-source HTTP API for Redis called RediServe.

I'm now looking for my next challenge at a [startup/company] where I can 
[one thing specific to THEIR product/mission — customize this line].

I'd love to tell you more about any of these projects."

Practice this 5 times out loud before your first interview.

Handling Tough Questions

”Why are you leaving your current role?”

NEVER badmouth your employer. Use one of these:

“I’ve had an incredible run — built the platform from the ground up over 5 years. I’m now looking for a new challenge where I can apply what I’ve learned at a different scale and in a new problem domain.”

“After 5 years of deep ownership on one platform, I want to broaden my impact. I’m excited about what [this company] is building and the engineering challenges that come with it."

"Why only one company in 5 years?”

“I stayed because the work was genuinely complex — multi-terabyte data, distributed systems, performance-critical services. There was always a harder problem to solve next. But now I’ve reached a point where I want to take that depth and apply it in a new context."

"What if you’ve only worked in one way / one codebase?”

“Fair question. Inside Intensel, I effectively built multiple systems from scratch — the API layer, the data pipeline architecture, the tile service, the geospatial query engine. Each was its own design challenge with different constraints. I also stay current with the ecosystem through open-source work in Rust and continuous learning — I’m currently working through Designing Data-Intensive Applications.”

Salary & Negotiation Quick Guide

Know Your Numbers Before You Start

• Research ranges on: levels.fyi, Glassdoor, LinkedIn Salary Insights, AmbitionBox (India)
• For startups: base may be lower but equity + growth potential matter
• With 5 YOE + your profile, you’re at Senior / SDE-2 level — don’t undersell

When They Ask “What’s Your Expected CTC?”

Delay if possible:

“I’d love to understand the full scope of the role first. I’m flexible and looking for the right fit — happy to discuss compensation once we’ve both determined there’s a good match.”

If pushed:

“Based on my research and experience level, I’m looking in the range of [X to Y]. But I’m open to discussing the full package including equity, benefits, and growth.”

Golden Rule

• Get the offer first, negotiate second
• Never accept on the spot: “I’m very excited about this. Can I have 2-3 days to review the full offer?”
• If you have multiple offers, say so (politely) — it’s powerful leverage

Weekly Review Checklist

Every Sunday, spend 30 minutes on this:

• How many applications sent this week? (Target: 15-25)
• How many responses/callbacks received?
• Which topics felt strong this week?
• Which topics need more work?
• Any interviews scheduled? What should I prep for them?
• Am I taking care of myself? (Sleep, exercise, social time)
• Update application tracker

Rejection Resilience

This is a numbers game. Here’s what’s normal:

Applications sent:     100
Callbacks/screens:     15-20    (15-20% response rate)
Technical rounds:      8-10     (50% pass screen)
Finals:                4-5      (50% pass technical)
Offers:                1-3      (25-50% conversion)

Every rejection means you’re closer to an offer, not further. The math works in your favor if you keep the pipeline full.

After every rejection:

1. Ask for feedback (most won’t give it, some will — and it’s gold)
2. Note what went wrong
3. Review the relevant prep document
4. Move on to the next one

Emergency Contacts & Resources

The One Thing to Remember

Your situation feels urgent, but your profile is strong. Five years of sole backend ownership at a startup, with real performance optimization stories and production distributed systems experience — that’s exactly what growing startups need.

The interview prep makes you articulate better. The applications create opportunities. The combination lands the job.

One step at a time. Start today.

Next step right now: Open 11-interview-power-keywords.md and read for 30 minutes. Then send 3 applications. That’s your Day 1.