What should I do this summer if I didn't get an internship?
Stop treating the rejection like a verdict. It is a logistics problem, and you can route around it. The best use of a summer without an internship is to build proof of work: pick the role you want, do a few real tasks from it, and get them scored against a professional standard. By September you have a small body of scored work in your target field, which is the exact thing an internship was supposed to leave behind. Nobody has to give you permission to build it.
- An internship is valuable for one reason: the proof it leaves behind. You can produce that proof without the offer letter.
- The stakes are not small. Completing an internship cuts underemployment risk by 48.5% (Strada and Burning Glass, Talent Disrupted).
- And the first job compounds: graduates who start out underemployed are about 3.5 times more likely to still be underemployed a decade later.
- The fix for a missing internship is the same thing that made internships matter: real, scored work in the role you want.
- Aim for a few strong, relevant, scored pieces, not a pile of half-finished projects nobody will ever open.
- Then put the work where recruiters can actually see it, instead of letting it rot in a folder.
Why does a blank summer actually hurt?
Because the market reads a gap as missing evidence, and the timing is unforgiving. The Talent Disrupted research found that graduates who start their careers underemployed are about 3.5 times more likely to still be underemployed ten years later. The early signal you build does not just decide your next application, it bends the next decade. An internship is the traditional way to build that signal, and the same data shows it lowers underemployment risk by nearly half.
So no, a summer without an internship is not a catastrophe. But waiting one out is a wasted shot at producing the one thing recruiters want most from someone with no track record, which is evidence they can do the work. Here is the part the doom-scrolling misses: that evidence is reproducible. The internship was never magic. It was a structured way to do real work and have someone judge it. You can build that structure yourself.
What is the best use of the summer, then?
Run it like a production sprint, not a waiting room. The reason an internship helps is not the line on the resume, it is that you did real work, someone qualified evaluated it, and now there is something concrete a recruiter can look at. You can manufacture that outcome directly. Spend the summer doing the actual work of the role you want, on real scoped problems, and get each piece scored so its quality is established instead of assumed.
This is also where most "do something productive this summer" advice quietly fails you. A pile of options will tell you to keep learning, and learning is good, but be honest about where each one stops. A Coursera or Udemy course, a Skillshare class, a LinkedIn Learning track: those end in a certificate that says you watched the videos. A Forage simulation lets you try a company-shaped task, then hands you a completion badge, not a score a recruiter trusts. A bootcamp teaches you to build; a career accelerator like Pathrise coaches you to apply. All of them are real, and most of them are fine. They just stop at the moment that matters. None of them put a scored sample of your actual work in front of someone who is hiring. That gap is the whole game.
How do you choose what to work on?
Narrow hard before you start. Pick one role, the one you would take an entry-level job in tomorrow, and do the work of that role instead of sampling five fields to keep your options open. Options-open is how people reach September with nothing finished. Choose tasks that leave a real artifact: a positioning brief, a product spec with trade-offs and a metric, an analysis that ends in an actual recommendation. Then aim for three to five strong pieces, not a dozen weak ones, because a recruiter is trying to answer one narrow question, can this person do this specific job, and a focused body of relevant work answers it cleanly.
We learned this the hard way building zero. The students who improved fastest were not the ones we tried to teach the most. The hand-holding tutorial that works in education products got in the way. They wanted to do something real within the first ninety seconds, and the thing that pulled them back was not another lesson, it was specific feedback on the exact piece of work they had just submitted. Generic skill advice got ignored every time. So the loop is simple: pick the role, do a real piece, get it scored, fix it, do the next one.
How do you make the summer count for hiring?
Get the work in front of people who hire. A summer of scored work only changes your odds if recruiters can find it and trust the score, which is why a folder of personal projects nobody asked for rarely moves anything. Build it somewhere that puts evaluated talent in front of the people doing the hiring. That is what zero is for: you take on company-shaped tasks, your work is scored against a professional bar, and the scored result becomes proof recruiters can open and judge in the time it takes to skim a resume bullet, except they are judging your actual work instead of a claim about it. It is free for students, because recruiters pay for the access. Run a summer that way and you can walk out with more hiring signal than the internship you did not get.