Students ask a reasonable question and then freeze. Recruiter, hiring manager, team lead, or the founder. The wrong answer is “whoever’s email you can find.” Cornell ILR’s CAHRS brief of 3 September 2026, from conversations with early-career recruiters at large employers, says application volume is higher because AI makes mass applying easy. One employer in the brief, Medtronic, screens more than 40,000 early-career applicants with AI matching, and humans make the final decisions. Employers in the group, including Medtronic, said career fairs and information sessions remain important despite that automation. The brief is a small set of employers. It is not a census. The mechanism is the part you can use. A flood of applications makes a random note cheaper to ignore and a specific human contact more valuable.
The 40,000 figure is Medtronic’s early-career volume as reported in that brief. Do not divide your self-worth by 40,000. Do notice that a matching system will see the application, and a person will see the finalists. A note has to be aimed at a person who still has a reason to open it. A note aimed at “the company” is another application with worse formatting.
Four readers, four different notes
A recruiter who posted the role, or who staffs your campus, can tell you whether the role is open and how students are reviewed. Ask them the process question. Do not ask them to be your hiring manager. Their job is the pipeline. A short note that says you applied, names the date, and asks one process question respects that job.
A hiring manager can talk about the work. They are the right reader when you have a specific question or a specific artifact, and a bad reader when you want a status update on an application the recruiter owns. If you write to them, lead with the work. “I applied on this date” can be the second sentence. It should not be the only sentence.
A team lead or a future coworker is the right reader when they do the task the posting describes and you have done a smaller version of it. Ask whether your example is the kind of work the team does. Accept a no. A founder at a small company may be the only person who hires, in which case the founder is the hiring manager and the recruiter at once. At a large company the founder is the wrong reader for an internship, and the note will be forwarded into the same pool as everyone else, if it is forwarded at all.
@BukolaSalau2 asked a version of this in public on 16 July 2026: recruiter, hiring manager, team lead, or the chief executive at a startup. The replies are opinions. Cornell’s brief is the employer-side account. Use the brief to pick a lane, then write the note that lane can answer.
Bring something they can recognize
On 19 October 2026, @tyler_agg argued for picking a company, building a project for it, and then reaching out personally. That is one person’s method. Cornell did not prescribe a project. It fits the brief’s world, where mass applications are cheap and human attention is not. A project is a reason for a team lead to care. It is not required for a recruiter note that only asks how the process works. Match the artifact to the reader. A recruiter does not need a repository to answer a deadline question. A hiring manager might need the repository to answer “is this the work.”
Build the project only when you can finish it. A half-built demo that exists to justify an email is visible. A finished, small, specific thing is the version of this advice that survives contact with a busy reader. If you cannot finish it this month, send the recruiter the process question and put the project on the plan for later. Waiting for a perfect demo while the posting closes is how the Cornell volume eats your week. The posting’s deadline is a fact. Your demo’s ambition is not an excuse to miss it.
Fairs and information sessions, which the brief says still matter, are the other way to choose a reader. You leave with a name. The note the next day has a person because you stood in front of one. That is a better origin for an email than a guess at a chief executive’s address.
A rule for the send list
One role, one reader, one note. If you truly need both a process answer and a technical opinion, send the process note to the recruiter and wait. Do not send four notes into the same company on the same afternoon. From inside the firm it looks like the mass-applying behavior the brief says they are already drowning in. From outside, it feels like hustle. The inside view is the one that decides.
If you do not know the name, use the address the posting gives. Inventing a better recipient is how notes go to the wrong desk. A public staff page can be right when the posting is vague and the person clearly owns the work. A scraped list of every director is the mass behavior again, done by hand.
Keep a record of whom you wrote and what you asked. The second note, a week later, should not ask a different person the same question the first person has not answered. Give the first reader the week.
How Flightpath helps
Companies and people sit together, so the recruiter and the role are not three unrelated rows. Pin the posting. Flightpath can suggest a public contact or give you a search link. You choose the reader. The draft should change when the reader changes. A process question and a project question are different drafts, and you approve whichever one you mean to send.
The tracker holds the date. The weekly check-in shows if you have written four people at one company and none at the next. Eligibility labels stay on the role, including when a flood of applicants does not change the fact that you cannot take the job. Cornell’s brief stays a 2026 account of a group of employers, with Medtronic’s volume named as theirs. The reader of your note stays someone you picked on purpose.