When to Send It
The email has to arrive before the hiring conversation happens. That is the whole reason it works.
Reads as engaged and specific. The details are still sharp, which shows in the writing.
The sweet spot. Considered but not laboured, and almost certainly before any debrief.
Still comfortably inside the window. Send it before the second night passes.
The decision conversation has usually happened. A delayed note draws attention to the delay.
The Five Parts
Under 200 words in total. Every template further down is these five parts in a different proportion.
Name the role and one thing that was genuinely useful about the conversation. 'Thank you for the time today' is fine; 'thank you for walking me through how the platform team splits ownership' is memorable.
Reference a detail only someone who was in that room could reference. This is what separates your email from the template everyone else sent.
Either strengthen the strongest reason you are right for the role, or fix the answer you were unhappy with. Pick one. Two starts to read as anxiety.
'Happy to send anything else that would help' or 'I look forward to hearing how the process goes.' No deadlines, no pressure, no asking when you will hear back.
Full name, phone number, and a link to your portfolio or LinkedIn if relevant. Make it effortless for them to reach you or to circulate your details internally.
Seven Templates
Replace every specific detail with your own. The specifics are what make it work, so do not send these as they are.
Any first or second-round interview. Send within 24 hours.
Hi Fatima,
Thank you for the time this morning. I came away much clearer on why the forecasting function sits with the regions rather than centrally — that split is unusual and it is a large part of why the role appeals to me.
One thing I did not mention: the reforecasting process I described at Halden ran on a two-week cycle at first, and moving it to weekly was what actually exposed the data quality problems. If that is the direction you are heading, I have been through the messy version of it.
Happy to share the model documentation if it would be useful. Looking forward to hearing how the process unfolds.
Best regards, Jordan Ellery 07700 900 118 · linkedin.com/in/jordanellery
One email per person, each different. Reference what that individual asked.
Hi Dev,
Thank you for making time today — and specifically for the question about how I would handle a disagreement with a regional manager over a forecast. It is the part of the job I find most interesting and I did not expect it to come up so directly.
Thinking about it since, the honest answer is that I would want the disagreement early rather than at sign-off, which is why I would push for the mid-cycle review you mentioned you are trying to establish.
I hope the rest of your week is calmer than the calendar suggested. Thank you again.
Best regards, Jordan Ellery 07700 900 118
Warmer, more direct about wanting the role. Send same day.
Hi Amara,
Thank you for a genuinely enjoyable final conversation. Meeting the wider team confirmed what I suspected from the earlier rounds — this is a group that argues about the right things.
I want to be direct: I would very much like this role. The combination of owning the model and owning the regional relationship is exactly the work I have been trying to move toward, and I am confident I could take the weekly cycle off your senior analysts within the first few months.
Whatever you decide, thank you for how considered the process has been. I am glad to provide anything else that would help.
Best regards, Jordan Ellery 07700 900 118
Repair one specific answer. Once, briefly, without apologising twice.
Hi Sam,
Thank you for the conversation today. I want to give you a better answer to your question about the rollback strategy, because I talked around it at the time.
What I should have said: we did not have a real rollback plan on the first migration, and the second attempt failed at 2am because of it. What I built afterwards was a dual-write window with a read-switch we could flip back for 48 hours. That is the approach I would bring here, and the reason I would bring it is that I have already got the first version wrong.
Thank you for the time either way — I appreciated how technical the discussion was.
Best regards, Jordan Ellery
One short nudge, after the date they gave you has passed.
Hi Fatima,
I hope the week has gone well. I wanted to check in on the Senior Analyst process — you had mentioned decisions were likely by the end of last week, so I did not want to assume either way.
Still very interested, and happy to wait if the timeline has moved. Thank you.
Best regards, Jordan Ellery
The one nobody sends, and the one that most often leads somewhere later.
Hi Amara,
Thank you for letting me know, and for the process — it was one of the more thoughtful ones I have been through.
If you have a moment at some point, I would genuinely value one line on what tipped it, so I can work on the right thing rather than guessing.
And if something opens up on the team later, I would be glad to hear about it. Best of luck with the hire.
Best regards, Jordan Ellery
Shorter and warmer. No role in play, so no pitch.
Hi Priya,
Thank you for the half hour — the point you made about forecasting teams failing on communication rather than modelling has stuck with me all afternoon.
I will look up the paper you mentioned. If it is ever useful to compare notes on how the regional split works in practice, I would be glad to.
Thanks again, Jordan
Six Subject Lines
The third one is the strongest, because it promises the reader something rather than asking for their attention.
The safe default. Clear, searchable, and obvious in a full inbox.
Fine, but generic. Add the role name if more than one candidate is in flight.
The strongest opening line there is. It promises something useful, so it gets read.
Good after a panel or an onsite. Warm without being familiar.
For the one-week nudge. Neutral and easy to reply to.
Replying in the existing thread keeps context attached. Often better than a new email.
Six Ways to Get It Wrong
They compare notes. Write one per person, each referencing something only that conversation contained.
Under 200 words. Anything longer buries the one sentence that was worth sending.
It reads as pressure and rarely gets a real answer. Save the timeline question for the one-week follow-up.
Check the spelling and the exact job title against the invitation. This is the one error that undoes the whole gesture.
One reinforcement or one repair. A point-by-point rebuttal of your own performance reads as anxious.
It is fifteen minutes, and in a close decision between two candidates it is occasionally the visible difference.