- SCALIS EarlyCareers
- Posts
- You Passed. Now a Manager Has to Find You.
You Passed. Now a Manager Has to Find You.
The stage after the interview is a search, and the thing being searched is not your resume.
New AI tools launch every day. A few will change how you work. The rest will be forgotten by next month.
TLDR AI is the free newsletter that tells you which is which. Every morning, Anthropic and ex-Google engineers pick the new tools, updates, and open source releases worth trying, with a quick note on what each one does and who it's for.
You find the good ones early, without testing all of them.
One email, 5 minutes a day, read by 1.1M+ people. Get tomorrow's picks.
Welcome to today's SCALIS EarlyCareers newsletter! 🚀
You interviewed in October. Two weeks later an email landed saying you had moved to project search, or team matching, or the matching pool, and that rolling matching would begin in November. You read it as good news, which it is. Then you filed it and went back to applying, which is where it goes wrong.
Here is what that email means. No recruiter is advancing you anymore. You are sitting in an internal marketplace where managers with approved summer projects go shopping for interns. They browse, they filter, and if one picks you, you get a short conversation and then an offer. If nobody picks you before the pool closes, you get a rejection, after passing every interview.
Candidates in the Summer 2027 cycle report recruiter emails saying exactly this: matching starts in November, runs rolling, and a match is not guaranteed. Google's own student hiring materials describe project search as the stage where potential hosts review your application for a skill match, and note that you can update your intern project preference questionnaire at any point. That last detail is the entire issue. Most candidates fill out that questionnaire once, in a hurry, before interviews, and never open it again.
The structure is not unique to one company. Any employer that hires interns into a central class and then distributes them to teams runs a version of this, under names like team match, project match, or fit conversations. A central process qualified you. A local manager still has to claim you.
Become An AI Expert In Just 5 Minutes
If you’re a decision maker at your company, you need to be on the bleeding edge of, well, everything. But before you go signing up for seminars, conferences, lunch ‘n learns, and all that jazz, just know there’s a far better (and simpler) way: Subscribing to The Deep View.
This daily newsletter condenses everything you need to know about the latest and greatest AI developments into a 5-minute read. Squeeze it into your morning coffee break and before you know it, you’ll be an expert too.
Subscribe right here. It’s totally free, wildly informative, and trusted by 600,000+ readers at Google, Meta, Microsoft, and beyond.

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

The document being read is not the one you polished
Your resume got you past the screen and into the interviews. In matching, managers are mostly not reading it. They are filtering a structured form you filled out: skill areas, languages, domains, location preferences.
It is a job board in reverse. You are the listing. A host looking for someone useful on a data infrastructure project in Seattle is running a query, and either your answers surface or they do not.
Reopen that form today. If you cannot find it, email your recruiter for the link. That request is routine and nobody will hold it against you.
Write it like a listing, not a wish list
The most common error is describing what you want to learn. Hosts are not staffing a classroom. They have twelve weeks and a deliverable, and they are scanning for someone useful in week one.
Weak: "Interested in machine learning and eager to learn backend systems."
Strong: "Two years of Python and Go, built and shipped a REST service with Postgres, comfortable with Docker and CI pipelines, strong interest in applied ML infrastructure."
The second version is searchable. It names tools a host can match against a project. Pick the two or three things you can actually do, name them concretely, then add the adjacent areas you would be glad to work in. Too narrow and few projects can see you. Too generic and you look like filler.
Breadth on location is the cheapest lever you have
Every intern seat is attached to a team in a building with budget for it. If you selected one city, you are visible to the hosts in one city.
If you would genuinely relocate, say so and list the metros. If there are places you truly cannot go, leave them out, because matching into a seat you have to decline burns the match and the time. Same logic for domain: if you listed only the most competitive area, every strong candidate is in that same queue, while internal tooling and infrastructure teams often have open projects and far fewer people looking at them.
TLDR AI is a free daily email curated by Anthropic and ex-Google engineers: the new tools worth trying and the research worth understanding, summarized for 1.1M+ readers.
The thirty-minute chat is an interview that nobody calls an interview
When a host reaches out, you get a short call, usually framed as casual. It is not. At the end, both of you tell the recruiter yes or no, and both answers have to be yes.
Reply to the scheduling request within hours, not days. A slow response reads as low interest. Then show up having looked at what the team builds, and ask questions that sound like a colleague rather than a candidate:
"What would an intern own in the first three weeks, and what does finished look like by week twelve?"
"What constraint shapes this project most right now: latency, reliability, data quality, or developer experience?"
"What does the handoff look like if the project outlives the internship?"
Those land because they signal you are thinking about shipping something, which is the only thing the host is actually worried about.
Matching runs on a calendar, and December is a hole
Rolling matching starting in November sounds open ended. It is not. Hosts disappear over the holidays, projects get locked in planning cycles, and pools eventually close. Candidates every year describe sitting in matching for months and getting nothing.
Front load the next six weeks. Set a Friday reminder to revisit the questionnaire. Check in with your recruiter every two to three weeks, not every three days.
Give the recruiter something to forward
A check-in that says "just following up on my status" creates work for a recruiter and gets a one line reply. A check-in with new information gives them something they can actually pass along:
"Hi [Name], I am in project matching for the Summer 2027 intern class. I updated my questionnaire this week to add [specific skill or tool] and expanded my location preferences to [cities]. I am also happy to be considered for infrastructure or internal tooling teams. If any groups are still looking, I would welcome an introduction."
That note is forwardable. The other one is not.
A match in progress is not an offer
This is the part that costs people a summer. Candidates stop applying the moment they reach matching, and some decline other processes while they wait. Then the pool closes without a match and it is February with nothing open.
Keep your other applications moving until you have a signed offer. Matching is good news about your interviews. It is not news about your summer yet.
You are not in a waiting room. You are in a search, and you still control what the search finds.



