Video summary

If you’re a computer science student, please watch this.

Main summary

Key takeaways

News and Commentary

Summary of the video’s main arguments and guidance

Core thesis: the CS degree isn’t a guaranteed job

The presenter argues that computer science students are being misled into believing that earning a CS degree and doing well in classes will reliably lead to employment.

He claims this narrative was strongly promoted by influential tech and political figures, including references to initiatives such as:

  • Code.org and “Hour of Code”
  • “Computer Science for All”, tied to the idea that learning CS would lead to degrees and jobs

Why the “degree → job” promise no longer holds

He points to a combination of oversupply and hiring contraction:

  • CS degree output has increased sharply (he claims it roughly doubled from about 52k to 112k annually)
  • Tech layoffs have been severe, citing large job losses across 2024–2026

His main critique is that the story treats degrees as if demand is unlimited. Instead:

  • Jobs are limited and competitive
  • Entry-level roles attract not only new grads, but also laid-off experienced engineers
  • A CS degree has stopped being a differentiator because too many people hold the same credential (he compares it to majors like art history, where the degree alone doesn’t guarantee an outcome)

Framing: the degree isn’t the “finish line,” but the “starting line”—an entry ticket to compete.

Personal anecdote meant to disprove the “degree” promise

He describes applying for internships with little response and feeling something was wrong.

After a single phone call by a family friend with engineering influence, he quickly got his first real interview—suggesting that connections and visibility may matter more than the degree alone.

“What separates hired candidates” framework (top-10 sequence)

He says the rest of the video provides an ordered plan focused on practical signals that recruiters and interviewers can actually observe.

  1. Projects (but don’t overdo them)

    • Projects help mainly to get initial interviews
    • He argues they “expire” after that purpose, and students often waste time building more and more
    • Suggested approach: do 1–2 projects, then shift to real experience

  2. Research

    • Working with professors/labs is framed as more job-like than solo projects
    • He emphasizes making specific early contributions so interview stories aren’t vague

  3. Open source

    • Contributes code used by real engineers; “good first issue” tags make it approachable
    • Caveat: open source helps with credibility and skill-building, but shouldn’t be relied on if fundamentals aren’t ready

  4. Hackathons

    • Positioned as gaining time-pressured building experience, often alongside career fairs
    • He advises doing 1–2 per semester, aiming to win, and showing up prepared (as if meeting employers)

  5. Unpaid/volunteering work via the “halo effect”

    • He argues unpaid roles still count if reframed appropriately
    • He claims recruiters value relevant experience whether or not it was paid
    • Goal: use unpaid work to secure your first paid opportunity

  6. Internships (strategy, not just resume padding)

    • He claims internships can convert more directly into full-time offers due to return-offer mechanics
    • He recommends aiming for the best SWE internship in junior summer and performing well to convert
    • He suggests “stairway” progression: start with realistic targets (not only FAANG) and climb
    • He advises applying early—citing his own example of submitting nearly a year in advance

  7. University career fairs

    • Encourages attending all CS/engineering fairs
    • Dress properly and bring polished resumes
    • He uses an anecdote to argue preparedness can create unexpected opportunities

  8. Networking

    • He claims referral candidates get offers far more often than cold applicants (with percentages especially for large companies)
    • He shares a “referral generation triangle”:
      • Warm network: ask contacts if companies are hiring
      • LinkedIn volume: send many thoughtful connection requests weekly
      • Blind gambit: message verified employees on anonymous platforms for referrals
    • He stresses consistency and follow-up, rejecting the idea that using connections is “cheating”

  9. Brand building (networking compound effect)

    • Calls branding a “cheat code”: not about massive followers, but about authenticity and a clear niche
    • He claims brand-building can lead to inbound recruiter outreach

  10. LeetCode (targeted, not random grinding)

    • He argues LeetCode is essential but often done incorrectly through random problem grinding
    • Recommended fix: a focused set of the “right 50” problems (a Pareto-style list), rather than hundreds
    • He frames LeetCode as training for thinking under observation, a distinct skill from building real systems
    • LeetCode must not replace other experience-building items

Product/CTA embedded in the narrative

  • The presenter promotes a “Software Engineering Starter Pack”, claiming structured help with:
    • resumes
    • referrals
    • interviews
    • LeetCode
    • recruiting timelines
  • Positioned as timed for the fall recruiting cycle

Presenters / contributors

  • Aman (presenter)
  • Mentioned in examples/credits:
    • Hadi Partovi, Ali Partovi
    • Bill Gates, Mark Zuckerberg, Jack Dorsey
    • Barack Obama
    • Ashton Kutcher, Shakira
    • Sajad Kader (referenced as a YouTuber)

Original video