Video summary

How He Cracked 8 Internships From a TIER-3 College | 2026 SDE Roadmap | Naval Bihani | Job Recession

Main summary

Key takeaways

Educational

Main ideas / lessons conveyed

  • Internships are built on “gym consistency” (DSA + disciplined practice), not on waiting to feel ready.
  • Don’t wait for perfect readiness: start tasks immediately—capability compounds over time.
  • Rapid learning is possible via targeted “just-in-time” study:
    • Example: take a short paid course to cover AWS basics before/during an AWS-related internship.
  • Public consistency boosts networking and opportunities (especially on LinkedIn):
    • Regular posting increases reach and recruiter visibility.
  • Strong fundamentals + careful review are crucial, even with AI tools:
    • AI can improve productivity, but you must understand and debug/review thoroughly to avoid wasting time fixing foundational mistakes.
  • A structured college roadmap exists:
    • DSA → Development (Web/App) + stronger practical work → specialization → System Design + CS fundamentals → interview-ready depth
  • Off-campus recruiting is more competitive:
    • Keep applying, tailor resumes, and learn from rejections.
  • Projects matter more than vague “about me” sections or certifications in modern markets:
    • Projects + measurable impact get attention faster.
  • Build a supportive competitive environment:
    • Study/solve together for motivation, speed, and accountability.
  • Use clones carefully:
    • Present them as distinct, feature-enhanced e-commerce projects—not as “Amazon clone” (which can trigger instant rejection).
  • Market trends change (AI is one example):
    • Stay adaptable and keep building relevant skills.

Methodologies / instruction-style content

1) Internship success “secret sauce” (as described)

  • Maintain consistency in DSA (problem solving) like a gym routine.
  • Start early and keep progressing, even if you don’t feel fully ready.
  • Use internships as a learning loop:
    • Take on stretch tasks (e.g., moving backend to AWS)
    • Learn missing knowledge quickly (short courses + grinding)
    • Complete the internship after ramp-up
    • Example timeline mentioned: ~7–8 months

2) How to cover a required tech area you don’t know (example: AWS)

When an internship role needs a skill you lack:

  • Identify the service fundamentals needed
  • Take a short, focused course
    • Example mentioned: ₹300–₹400
  • Finish quickly
    • Example mentioned: ~3–4 days
  • Grind until you can confidently handle interview questions

Goal: be able to explain/operate the service when asked, not necessarily master everything before applying.

3) LinkedIn strategy for getting internships/offers

  • Get recruiters’ attention via public activity
  • Post what you’re doing—short and specific:
    • Keep posts short/concise
    • Mention personal progress/actions and results
  • Avoid overly long, generic posts
  • Consistency increases reach
    • Example claim: moved from ~800–900 followers to ~10,000 by posting consistently

4) DSA-first learning plan (roadmap across semesters)

If you’re starting in 1st year

  • Spend ~1–2 semesters on DSA
    • Solve roughly 200–250 questions
  • Then start development
    • Use summer holidays to learn web development
    • Example claim: “at least” in 2 months
  • In the next semester:
    • Make DSA + web dev both strong
  • 3rd semester:
    • Pick one specialization based on interest: cloud / AI / blockchain / DevOps
  • 4th semester:
    • Focus on HLD + LLD
    • Strengthen CS fundamentals for interview depth

If you start in 2nd semester and had fun in 1st year

  • Follow the same structure, but compress the timeline
    • Example mentioned: completing major preparation earlier than end of college

Repeated core principle:

The earlier you complete the core stack, the faster your growth. Avoid slowing down due to delayed fundamentals.

5) Off-campus job application process (general recruiting instructions)

  • Apply continuously
    • Example pattern: apply for a couple months before offers show up (learning curve)
  • Don’t reuse the exact same resume blindly
    • Tailor the resume to the Job Description (JD)
    • Add role-specific keywords for ATS
  • Don’t spam one CV across every role
    • Match skills/keywords to what the role asks for
    • Example: full-stack role → full-stack keywords
  • Learn from rejections
    • First rejection can be discouraging, but treat it as feedback and improve

6) Handling AI usage without losing fundamentals

  • Use AI to increase productivity, but:
    • Review thoroughly
    • If AI makes an error due to missing fundamentals:
      • you can’t efficiently fix it unless you understand the underlying concepts
  • Warning example (intern behavior criticized):
    • Some interns paste errors into production/cloud dependencies without understanding
    • This creates unwanted dependencies and cascading problems
  • Personal rule claimed:
    • Prefer doing fixes yourself; use AI as support, not a full replacement

7) Project selection/presentation guidance for resumes

  • Build projects that solve real problems (or convincingly product-like problems)
  • Use measurable impact:
    • Include numbers (e.g., “1000+”) and highlight key metrics
  • Remember the HR skim advantage:
    • HR decides quickly (claimed: within ~5 seconds)
  • If building clones:
    • Don’t say “Amazon clone”
    • Reframe as:
      • “E-commerce website” + modifications + additional features
    • Differentiate to avoid instant rejection

8) What to emphasize in the resume

  • Minimize/remove generic “about yourself”
  • Prioritize (in order):
    1. Skills
    2. Projects (with numbers + highlighted metrics)
    3. Certifications (lower priority than skills/projects/experience)

Key concepts mentioned

  • DSA as critical thinking + optimization foundation
    • Even with AI, full reasoning depth still matters.
  • System Design importance for fresher interviews
    • HLD is more common than LLD in interviews (as described).
  • CS fundamentals mapped to interview topics
    • OOPs → DBMS / Computer Networks → OS (framing described in narrative)
  • Cloud selection philosophy
    • AWS/SR/etc. share similarities; service names/configs differ, but practice transfers.
  • Certifications vs practical evidence
    • Open-source and internet access reduce certification advantage.
    • Resume drivers: projects + experience.

Speakers / sources featured (as named in subtitles)

People / speakers

  • Naval Bhai / Naval Bihani (main interview/podcast guest and host personality mentioned repeatedly)
  • Aditya Verma (recommended for tree/graph/DP-related learning)
  • Kunal Kushwaha (recommended Java + DSA playlist source)
  • Neso Academy (recommended for CS fundamentals via college-exam style preparation)
  • Hello Interview (recommended system design resource/channel)
  • “GPT” / ChatGPT (mentioned as a tool used to create roadmaps/learning guidance)
  • Claude (mentioned as an AI tool; discussed in the context of AI review/productivity)

Systems / platforms / tools mentioned (sources without being “speakers”)

  • LinkedIn
  • LeetCode / LeetCode style questions
  • Codeforces (CP / Grandmaster referenced)
  • AWS
  • Google-like web course (generic “web course” with a mentioned price)
  • ATS (resume screening logic)

Original video