When you invite a candidate for an interview, the email they get is the first real read they have on your team. The recruiter call came earlier, but that was a conversation with someone who, from the candidate's point of view, doesn't yet represent the hiring team. The invitation email does. It's signed by someone on the team, it describes something the team actually runs, and it sets the tone for the round that's about to happen.

Most invitation emails don't take the job seriously. They're drafted as logistics: a date, a meeting link, a rough agenda, a line about who'll be on the call. The candidate reads them in 20 seconds, files them under "meetings", and shows up prepared for exactly whatever tone they've inferred from the paragraph. That inference is rarely the one the hiring team wanted to leave.

What the email ends up doing whether you mean it to or not

An invitation for an interview carries information beyond its contents. The moment it lands in the candidate's inbox, it's already telling them whether the team is organised, what the round is actually about, and whether the team respects their time.

A vague invitation is read as a vague team. Candidates make that inference automatically within the first read, and it's hard to unwind later. What the round is about matters just as much: if the email says "a technical conversation," the candidate prepares for a technical conversation. If it says "a 45-minute discussion of the take-home you submitted, focused on the trade-offs you made," they prepare for that. Vague scoping gets vague preparation, and then the hiring team complains in the debrief that the candidate didn't seem prepared.

The time signal is the quietest and the most consequential. An invitation that asks for "a 2-hour call, Thursday afternoon" and offers no flexibility says one thing. An invitation that offers three blocks across two days and asks which works best says another. Both ultimately book a meeting; the candidates arriving in them are in very different moods.

What a good invitation for an interview includes

The email should answer the questions the candidate would type into a reply if you left them out. Not all of them need long paragraphs. Most of them need a sentence:

  • What the round is called, and what it's meant to assess. "A 45-minute technical deep dive on the take-home you submitted, focused on the trade-offs you made." Better than "technical interview."
  • Who's in the room, by name and role. "Ali (engineering manager) and Priya (senior engineer)." Candidates behave differently in a room of two senior engineers than in a room with an EM and a skip-level, and they have a right to know which they're walking into.
  • What to bring, or not bring. If the candidate needs to have read something beforehand, say so, and link to it. If they don't, say so explicitly, because the default assumption for most candidates is that they should be over-preparing.
  • What's allowed. This is the one most invitations get wrong in 2026. If the candidate can use an AI collaborator, say so. If they can't, say that and explain why. Silence on this point means every candidate draws a different conclusion, and you're scoring against the conclusion rather than the work.
  • A candidate-prep line. One sentence. Not "here's a study guide." More like: "The thing we care most about is how you reason through trade-offs — there's nothing you need to memorise beforehand."

What to leave out

A good invitation for an interview is short. The candidate will read it on a phone, between meetings, while eating lunch. Fluff about the team's culture, links to the careers page, or three paragraphs about how excited you are to have them through — all of it crowds out the signal.

The thing most worth cutting is the part that sounds like marketing. Candidates can tell when an email has been run through a tone committee. The more your invitation reads like a recruiting brochure, the less they believe the specifics in it. A blunt email from a named person on the team, written in plain language, lands better than a polished template every time.

The candidate-prep question

The most common variant of "how should I prepare" is really a question about what will be scored. Tell the candidate the answer directly. "We care about how you frame the problem and the reasoning behind your trade-offs, more than whether the implementation is complete" is more useful than a generic study guide, and it's also more honest. If your round is doing the job a first technical screen ought to do, this kind of candid framing drops the performance anxiety and lets the candidate show up as themselves.

The practical move

The next time you invite a candidate for an interview, write the email as if you were emailing a new colleague about a meeting on Thursday. Specific time, specific attendees, specific agenda, honest about what's being assessed. Read it back before sending. If it reads like something you'd be comfortable receiving yourself as a candidate — clear, short, respectful of your time — it's probably doing more work for your process than the interview itself.