Career fair follow-ups fail at the booth, hours before you type a word.
Template guides polish the sentence. The email still fails, because nothing specific got written down at the booth. The fix happens upstream, on the floor.
The email you're about to send at 11 p.m.
The fair ended at four. It's late now, the tote bag is on the floor, and there's a pile on the desk: a few business cards, a fistful of flyers with QR codes, a branded pen from a company you can't place. Thirty booths. Maybe more.
You open a blank email to the recruiter from the logistics firm. Or was that the bank? You type the line every guide told you to type: "It was great learning about your software engineering roles."
Then you send a version of it twenty-nine more times.
Every one of those emails is polite, on time and correctly formatted. And every one of them could have been written by any student who walked past that booth, which is exactly how the recruiter will read it.
The empty-buffer problem
A follow-up email has one job. It has to prove to a stranger that the conversation happened and that it mattered to you. Proof needs evidence, and the evidence is a detail only you could know: the project the recruiter said their team was hiring for, the city they mentioned, the question they asked you back.
Call the place that detail lives the buffer. At a career fair it fills during a four-minute conversation and drains fast, because the next booth writes over it. By the thirtieth handshake, the first ten have blurred into one long conversation about culture and growth.
So the follow-up fails before you write it. When the buffer's empty, no amount of phrasing can put a real detail back in, and the email falls back on the only material left: the company name and the job category printed on the booth banner. That's the empty-buffer problem. It's structural, and it's why fixing the sentence doesn't fix the email.
Why career fair follow-up email templates don't work
Search "career fair follow-up email" and you'll get a page of templates. They're competent. Subject line, greeting, a thank-you, a line restating interest, a résumé attached, a sign-off.
Look at the middle of almost any of them and you'll find a bracket, something like [mention something specific you discussed]. That bracket is the whole email. Everything around it is packaging the recruiter has already seen many times this season. The template hands you the packaging and leaves you to supply the one part it can't, on the night you're least able to supply it.
Worse, templates make the empty version feel finished. Fill in the company, fill in the role, skip the bracket or paper over it with "your team's work," and the result looks like a professional email. It reads like one too, right up until a recruiter sets it beside the other forty that opened the same way.
The template's most important line is the bracket it can't fill.
What a recruiter can tell from your first line
Career fair stakes are blunt. There's no slow relationship to build here. The email either moves you toward an interview slot or it doesn't, and a recruiter working through a full inbox after a fair has little reason to read past an opening that could belong to anyone.
Strip two follow-ups down to what the recruiter actually learns from each, and the gap stops being a matter of tone.
What the recruiter learns
Generic opener
Captured opener
The opening line
"It was great learning about your software engineering roles."
"You mentioned the warehouse-routing team wants two summer interns who've worked in Python and SQL."
Did this conversation happen?
Can't tell
Yes, and the recruiter recognizes it
Which student is this?
Any of the students who stopped by
The one who asked about the routing team
What happens next?
Nothing specific
The next step the recruiter named at the booth
Illustrative comparison written for this article. The second opener is only possible if the detail was captured at the booth.
How to follow up after a career fair: the twenty seconds after each booth
Walk through one booth. You spend four minutes with a recruiter from a mid-size engineering firm. As you step away, before you join the next line, you take twenty seconds and record three things.
Who. The name, from the card or badge, or just ask. If there's only a QR code, scan it at the booth while the recruiter can still confirm it's the right one.
One detail. Something they said that a stranger couldn't guess: a team, a project, a location, a hiring timeline, a question they asked you.
The next step they named. "Apply through the portal and email me." "We're running an info session next week." Or nothing at all.
That third item does your triage. Of thirty booths, some will have offered a real next step. Those get tonight's best emails, each opening with the captured detail. The booths that offered nothing get a short note or no note, and that's fine. Eight emails that each prove a conversation happened will beat thirty interchangeable ones.
Once the buffer's full, the email barely needs a template. "You mentioned the routing team wants someone with SQL. I built a delivery-scheduling project in it last spring, my résumé's attached, and I've applied to the summer posting." That's the whole move.
Don't invent the detail
If the buffer's empty for a booth, don't fake a specific. A made-up "you mentioned" that the recruiter doesn't recognize hurts more than a plain note. Send a short, honest line, or skip that booth.
What changes when the problem is capture
The work moves. The follow-up stops being a late-night writing assignment and turns into a floor habit, done in the hallway between booths while the detail still exists.
It also changes how you prepare. Most fair prep goes into the entrance: the thirty-second introduction, the stack of printed résumés. Some of that energy belongs to the exit, meaning a way to write down one line per booth without breaking stride. A phone note works if you'll really do it thirty times. Paper works until it's buried in a tote bag.
And the timing pressure eases. The usual advice is to follow up within a day or two. That deadline is brutal when you're reconstructing conversations from memory, and easy when you're working from notes. Our earlier piece on [the 72-hour memory cliff](/articles/72-hour-memory-cliff/) covers why recall falls off so quickly after an event. A career fair packs thirty conversations into one afternoon, which makes that slope steeper.
Where Met fits on a career fair floor
Met is a contact app built around that exit moment. Event Mode keeps the session open while you work the room, so every card or contact you capture lands in one place with its context attached, instead of in the bottom of a bag. When you sit down that evening, the follow-up draft starts from what you recorded at the booth, so the opening line is the detail you heard.
Contacts stay in your own iCloud, and there are no ads. For someone building a first professional network, that's a sensible default.
The honest test for any tool here is simple. Does it make the twenty seconds after each booth fast enough that you'll actually do it thirty times in a row? That habit decides whether next week's emails sound like you met anyone at all.
Capture the detail at the booth, then send the email that proves you were there. Get Met before your next career fair.
Met is built for the moment between conversations. Event Mode keeps capture open while you walk the floor, each contact keeps the context you recorded, and the follow-up draft starts from that detail instead of the company name. Contacts stay in your own iCloud with no ads. It's made for people whose next step depends on remembering exactly what someone said.