Video summary

The Truth About Coding Jobs in 2026 (Must Watch) Crack Your First Job as a Software Engineer

Main summary

Key takeaways

Educational

Main ideas / lessons

1) Cold outreach works—but generic messages don’t

  • To get interviews/internships, customize your outreach:
    • Research the company/product/mission.
    • Explain how you can contribute specifically (not “I want a job”).
    • Include a relevant portfolio/GitHub (visibility matters).
  • Generic messages reduce response rates; tailored messages can lead to calls and fast hiring.

2) Build “visible proof” with creative projects (not just resume templates)

  • A major hiring differentiator is having a portfolio that stands out:
    • Don’t only list course projects (e.g., HTML/CSS or standard e-commerce clones).
    • Create something creative and unique to demonstrate real thinking and capability.
  • The core idea: visibility + creativity + outreach leads to opportunities.

3) Startups vs Big Tech: both are important, but they teach different things

  • Startups:
    • Provide foundation/product thinking
    • Help you learn breadth quickly
    • Expose you to real problems
  • Big Tech:
    • Offers scale
    • Builds engineering depth
    • Reinforces strong systems/process
  • Recommended balance: get a foundation first, then scale your impact.

4) Career mindset: manage AI rather than let it manage you

  • AI can help, but relying blindly is risky.
  • Avoid “vibe coding” (letting AI generate code without understanding).
  • Treat AI like an intern:
    • Supervise, validate, and decide what to do.
  • Maintain fundamentals so you don’t end up “wiped coding” (limited to AI-generated outputs).
  • AI won’t replace the need for engineers handling trade-offs, architecture, and system-level decisions.

5) Stay language-agnostic and learn fundamentals across the stack

  • Interviewers increasingly value problem-solving + depth of engineering thinking, not one framework.
  • Even if tech differs (JavaScript, React/Next.js, Java, Ruby, etc.), the theme is:
    • Learn concepts and patterns,
    • Apply them across languages.

6) Don’t ignore DSA—balance DSA + Web/system design

  • Hiring filters often still include:
    • DSA (data structures/algorithms)
    • Web development
    • Sometimes system design / product thinking
  • Practical framing: keep an equilibrium between DSA and web engineering.
  • If DSA is weak, you can fail interviews even with strong web skills.

7) Networking and persistence: opportunities don’t arrive automatically

  • Reach out regularly (e.g., monthly).
  • Expect many ignores/rejections—keep going.
  • Treat a rejection as feedback; a single reply can change outcomes.

8) Environment & “scale” matter (what Big Billion Day felt like)

  • During Flipkart onboarding, they experienced high-scale events (e.g., Big Billion Day) and highlighted:
    • Rolling deployment/testing
    • Gradual rollout (e.g., 5% → 10% → …)
    • Scale-driven engineering responsibility

Methodology / instructions presented

A) How to send internship/job outreach that gets responses

  1. Research the company
    • Understand mission, vision, and the product.
  2. Identify a specific contribution
    • Map your skills/projects to what the company is trying to solve.
  3. Write a non-generic message
    • Replace: “I want a job”
    • With: “This is how I can contribute/help you grow”
  4. Attach proof
    • Include portfolio/GitHub that supports your claim.
    • Note: a GitHub repo alone may not be enough—focus on visibility too.
  5. Choose channels
    • The speaker mentions networking via LinkedIn/WhatsApp groups and direct messaging.
  6. Expect follow-ups or callbacks
    • Tailored messages can lead to replies/calls quickly.

B) How to build “visibility proofs” for job hunting

  • Create at least one standout project
    • It should be more creative than common resume templates.
  • Make it clear why it matters
    • Show reasoning/idea—not just the UI.
  • Productize it
    • Turn your work into something presentable and shareable.
  • Share it publicly
    • Post updates and progress on professional networks.

C) How to prepare for interviews when AI tools are available

  • Use AI as support, not authority
    • Review and verify outputs.
    • Understand requirements; then implement.
  • Focus on core engineering
    • System design patterns
    • Trade-offs
    • Architecture decisions
  • Avoid “vibe coding”
    • Don’t blindly accept AI-generated solutions.

D) Balanced learning roadmap (implied by what they practiced)

  • Maintain equilibrium between:
    • DSA readiness (for algorithm rounds)
    • Web development strength (projects + frontend/backend capability)
    • System design / product thinking (architecture + deeper interview rounds)
  • Practice with real interview-style tasks:
    • Machine coding
    • DSA rounds
    • System design rounds with explicit patterns/blueprints

E) Handling the “stuck” phase (what to do when opportunities aren’t coming)

  • Keep calm and treat it as normal.
  • Build skill + visible proof
    • Projects, proof points, portfolio updates
  • Showcase publicly
    • Share progress on LinkedIn/Twitter-like platforms
  • Build opportunity via outreach
    • Reach out monthly; keep going despite ignores
  • Prepare for interviews proactively
    • Don’t wait until after applying—practice ahead of time
  • Stay confident
    • Don’t let rejection define you; use it to improve

Speakers / sources featured

  • Ajay — podcast host/interviewer (name appears repeatedly)
  • Manvinder — guest; software engineer (also discusses earlier roles and interviews)

Original video