In partnership with
Hey everyone,
Quick gut check. You've sent out somewhere between 50 and 300 applications this year. How many turned into an actual human conversation?
If that number is close to zero, you're not bad at this. You're playing a version of the game that was built to reject you by default. Referred candidates land offers at roughly four times the rate of someone applying cold through a career site, and only a small sliver of applicants ever go that route. Everyone else is fighting over the leftover odds.
No news this week. No roles board. Just the actual playbook, the five things that move you from "application submitted" to an offer, and why most CS students never do any of them.
200 applications. Zero callbacks. The math was never in your favor.
One thing before section one. The difference between finishing the project in section two and abandoning it like the other seven half-built ones usually comes down to the stack you picked.
One API. 1,000+ AI Models
Change a single line of code and unlock 1,000+ AI models, smart routing for cost and performance, and persistent agent memory.
Okay. Section one.
// 01
Stop applying blind
What most CS students do: open LinkedIn, filter by "Software Engineer Intern," and blast the same resume at forty companies where they know exactly one person, that person being nobody.
What actually works: find one person who already works there before you apply.
The math isn't close. Referrals make up roughly 6 to 7 percent of all applications submitted, yet they account for 30 to 50 percent of actual hires. A referred candidate is about four times more likely to get an offer than someone who applied cold, and for specialized technical roles that gap gets even wider.
Your move: search "[Company] [your school]" on LinkedIn. Message three alumni with something specific, not "can you refer me." Try: "I'm building [specific project], applying to [specific role] there, would love five minutes on what the team actually works on." People respond to specificity, not desperation.
// 02
Build one thing, not ten half-things
What most CS students do: seven abandoned tutorial clones on GitHub. A todo app. A weather app. A clone of a clone of a clone.
What actually works: one project that solves a real problem for real people, live at a real URL, with a commit history that shows you built it over weeks instead of copy pasting a course.
The bar isn't impressive. It's finished. A recruiter skimming your resume for six seconds needs one line that makes them stop scrolling. "Built and shipped X, used by Y people, solved Z" beats five bullets about "familiarity with React."
// 03
Quantify everything or cut it
Weak: "Worked on backend systems for a class project."
Strong: "Rebuilt the query layer for a 12 person class project, cut average response time from 800ms to 140ms."
If a bullet doesn't have a number in it, find the number or delete the bullet. Vague claims read as filler. Recruiters, and the AI screening tools reading your resume before a human ever does, are both pattern matching on specificity.
// 04
The follow-up nobody sends
You apply. You hear nothing. You assume it's dead and move on. Here's what almost nobody does: seven to ten days after applying, send a short, specific note to whoever posted the role or a recruiter at the company. Not "just checking in." Reference something real, a recent launch, a specific team, an actual reason you're interested. Most applicants never follow up once. The ones who do stand out by default, because the bar is on the floor.
// 05
Apply in the first 48 hours
Roles get flooded fast. The earliest applicants get read by an actual human before the pile gets automatically filtered down. Set alerts for the 10 to 15 companies you actually want, and treat the first two days after a posting goes live as the window that matters most. Waiting a week to "perfect" your application is how you end up buried under six hundred other PDFs an ATS never opens.
The actual math
None of this guarantees anything. But stacking a referral, a real project, a quantified resume, a follow up, and early timing against each other compounds. Most people are doing zero of these five things. You only need to be doing more than the person next to you in the pile.
The market isn't getting easier this year. But most of your competition is still doing this wrong, which is good news for you if you're not.
One more newsletter worth your inbox:
Support Jobless
Forward this to a friend still refreshing their inbox for a reply that isn't coming. Drop us a line on r/csMajors if one of these five actually worked for you this week. And if you haven't checked out joblessnews.com, that's where all of this lives.
Until next time,
Team Jobless
