You Cannot Run This Play on Fifty Companies

In partnership with

100+ Claude Code hacks to ship code 10X faster

Top engineers at Anthropic and OpenAI say AI now writes 100% of their code.

If you're not using AI, you're spending 40 hours doing what they do in 4.

These 100+ Claude Code hacks fix that and help you ship 10x faster.

Sign up for The Code and get:

• 100+ Claude Code hacks used by top engineers — free

• The Code newsletter — learn the latest AI tools, tips, and skills to code faster with AI in 5 minutes a day

Claim your free playbook

Welcome to today's SCALIS EarlyCareers newsletter! 🚀

Open your tracker. If you are like most people reading this, there are somewhere between eighty and four hundred rows in it, you have submitted since early September, and what came back was three instant rejections and a wall of nothing. The advice you keep getting is to widen the funnel. Send more. Cast wider.

Here is the thing nobody says cleanly. Volume is not wrong because it is lazy. Volume is weak because it is the only channel most students run, and it happens to be the channel with the worst conversion in the entire process. The fix everyone recommends, "network more," is equally useless, because it never names a unit of work. Nobody can act on a verb.

So here is the unit. We covered a while back that a referral is not a vibe, it is a form an employee fills out inside the company's system, and one of the fields on that form asks how they know you. Everything in today's issue exists to produce a good answer to that one field. "They messaged me on LinkedIn last Tuesday" is a bad answer. "She asked me a sharp question about our migration, we talked for twenty minutes, I have seen her work" is a good one. The second answer cannot be written in a day. It takes weeks to become true.

That is where your list length comes from. Not from ambition, from the calendar. And right now the calendar is unusually friendly: Wave 2 and Wave 3 run from November into March, which is where mid-size employers, healthcare systems, agencies, engineering firms, media, and government actually hire. You have runway. You do not have enough runway for four hundred rows.

Two days of free email tactics, starting Nov 12

Two full days of email marketing tips and trends, powered by Constant Contact. Famous keynotes (Molly Ringwald, Dan Levy, Amy Porterfield!), DJs, world-record breaking, rom-com fun, and networking.

• 100% Free & Virtual

• 29,000+ Marketers Joined Last Year

• November 12th & 13th

Save your spot!

4,052 BRAND NEW internship positions freshly posted today. View the full list below and start applying!

Derive your list length instead of choosing it

Price out one target honestly. You identify the two or three people who would actually touch the hiring decision. You write each of them something individual, which takes real thought, not a template swap. You wait, because people answer on their own schedule. You have a conversation. You follow up when the requisition opens. Call it four to six weeks of low-intensity calendar time, maybe ninety minutes of actual work spread across it.

Now ask how many of those you can run at once without any of them going shallow. For most students carrying a full course load, the honest answer is eight to twelve. That is your list. You did not pick the number, the sequence picked it for you, and that is exactly why it holds up when you are tired in week three.

Choose targets where a human can actually act

Concentration only pays where somebody inside the building has the power to move you. That is a structural question, not a prestige question.

At an employer running a cohort of several hundred interns, the process belongs to campus recruiting operations, the stages are fixed, and a referral is a tiebreaker at the margin. At an employer hiring two or three interns onto a specific team, the manager who needs the help is frequently the entire process, and a credible introduction is not a tiebreaker, it is the hiring decision.

So weight your list toward the second kind. Ask three things before a company earns a row: does this team hire a small number of interns, do people from my school actually work there now, and is the role either unposted or freshly posted. Three yeses is a target. One yes is a portal application.

Contact the person who needs the work done

At the small and mid-size employers where this play works, the recruiter is a coordinator and the hiring manager is the buyer. Students reflexively write to recruiters because recruiters feel official. It is the wrong desk.

Find the person whose team the intern will sit on. The posting usually names the department. From there, filter by company and function and read for who is senior enough to own headcount but close enough to the work to care. If the team publishes anything, a product changelog, an engineering post, a conference talk, a case study, a grant abstract, you now know what they are working on this quarter. That is the opening.

Learn AI in 5 minutes a day

You don't have to scroll every AI thread, track every new tool, or watch every demo. 

The Rundown AI breaks it all down for you — the latest AI news, tools, and tutorials in one free 5-minute email every morning. 

Trusted by 2M+ professionals at Apple, Google, and NASA.

Sign up to start learning.

Your first message should not contain an ask

This is the part people get wrong, and it is wrong for a mechanical reason rather than an etiquette one.

If your first contact is "would you refer me," you have asked someone to vouch for a stranger. The honest version of that form gets filled out as "does not really know this person," which is close to worthless and occasionally worse than nothing, because it burns the one connection you had.

So make the first message about the object, not about you. One specific thing they worked on, one question only someone at that company could answer, and nothing attached. No resume, no link to your portfolio, no mention of the internship. You are not being coy. You are building the thing the form asks about, and the only way to have talked to someone is to have talked to them.

Time the sequence to the requisition, not to your nerves

The sequence has to already be running when the posting goes live, because we have covered what rolling review does to a queue in the first few days. Starting outreach after you see the req means you are introducing yourself while the pile fills.

Practically: set alerts on your eight to twelve now, run the conversations through November and December, and when a role opens you are not asking for a favor from a stranger. You are sending a short note to someone you have already spoken with, with a requisition ID in it.

Keep a volume floor running underneath

Concentration is not abstinence, and I am not telling you to apply to eight things and hope. Five thousand applications is absurd, but so is eight.

Run both. Put the depth play on your eight to twelve, and keep a steady baseline of straightforward portal applications going in the background, an hour a week, no agonizing, no custom cover letters. The portal applications are the hedge. The eight to twelve are the part that converts. The mistake is not sending applications, it is believing that is the whole search.

The two messages, roughly

First contact, week one:

Second contact, when the role posts:

The second message works only because the first one happened six weeks earlier. That gap is the entire strategy, and it is the reason the list is short.