# Follow-up email after an interview that adds real value

> Writes a short post-interview thank-you email that references the conversation, repairs a fumbled answer, adds one useful thing, and schedules a check-in.

- **Author:** [Oliver Hughes (@oliver_hughes)](https://promptabide.com/oliver_hughes)
- **Tested on:** Claude · Opus 5.5
- **You fill in:** `interviewer`, `role_and_stage`, `interview_notes`, `value_add`, `interview_date`
- **Published:** 2026-09-09
- **Updated:** 2026-09-24
- **Tags:** `job-search`, `interview-prep`, `writing`, `career`
- **Keywords:** thank you email after interview, follow up email after second interview, how to fix a bad interview answer, post interview email template, when to follow up after an interview
- **Views:** 2240
- **Likes:** 30

**Best for:** Candidates who just finished an interview, especially one where an answer went badly and they want a graceful, low-key chance to fix it.

## Prompt

```
Write my follow-up email after a job interview. It should be short, prove I listened, and add one thing of value, not just "thanks for your time".

Who I met and their role: {{interviewer}}
Role and stage: {{role_and_stage}}
Notes from the conversation (topics, what they seemed worried about, anything I fumbled): {{interview_notes}}
Something useful I can add or follow up on: {{value_add}}

Write:
1. Subject line (under 8 words).
2. The email, 90-140 words: thank them with one specific reference to our conversation; fix the one thing I fumbled, briefly and without over-apologizing; include the value-add; end without pressure.
3. A 2-line version for LinkedIn in case I don't have their email.
4. When to send it, and when to send a single polite check-in if I hear nothing. Give actual dates, assuming the interview was {{interview_date}}.

Tone: warm and plain, like a colleague. Don't use "I hope this email finds you well", "circle back" or "touch base".
```

## Variables

- `{{interviewer}}` — Name and title of the person you met. (e.g. Dana Whitfield, Engineering Manager, Platform team)
- `{{role_and_stage}}` — The job and which round this was. (e.g. Senior SRE at Kestrel Health, second-round technical interview)
- `{{interview_notes}}` — What you discussed, their concerns, and anything you'd like to redo. (e.g. I blanked on setting SLOs for a batch pipeline)
- `{{value_add}}` — A resource, better answer or follow-up you can offer. (e.g. An incident-review runbook template I wrote)
- `{{interview_date}}` — The day of the interview, with the date. (e.g. Tuesday, September 22, 2026)

## Example input

```
interviewer: Dana Whitfield, Engineering Manager, Platform team
role_and_stage: Senior Site Reliability Engineer at Kestrel Health, second-round technical interview (60 minutes)
interview_notes: We talked about their move from self-managed Kubernetes to managed EKS. She's worried about on-call load: a team of 5 handling about 2 incidents a week. I blanked on how I'd set SLOs for a batch pipeline and gave a vague answer about uptime. They use Grafana and PagerDuty. She said they'll decide by the end of next week.
value_add: I wrote an incident-review runbook template at my last job and could share a sanitized version. I've also worked out the better answer: for batch pipelines, SLOs should be about freshness and completeness, e.g. 99% of daily runs finish by 6 a.m. with all records present, not uptime.
interview_date: Tuesday, September 22, 2026
```

## Output

*Produced by Claude · Opus 5.5.*

```
**1. Subject:** Thank you, and a better SLO answer

**2. Email**

Hi Dana,

Thanks for the conversation today. I enjoyed hearing how the team is approaching the move from self-managed Kubernetes to EKS, and I understand why on-call load is on your mind with five people covering about two incidents a week.

I also owe you a better answer on SLOs for batch pipelines. Uptime is the wrong measure there. I'd set them on freshness and completeness, for example "99% of daily runs finish by 6 a.m. with all expected records," and page in PagerDuty when a run is on track to miss that.

Since on-call came up: I wrote an incident-review runbook template at my last job and would be glad to share a sanitized version if it's useful.

Best,
[Your name]

**3. LinkedIn version**
Thanks for today, Dana. I owe you a better SLO answer: for batch pipelines I'd measure freshness and completeness, not uptime. Happy to share my incident-review template if useful.

**4. Timing**
- **Send:** today, Tuesday, September 22, or by 9 a.m. on Wednesday, September 23 at the latest. It should arrive before the team compares notes.
- **Decision window:** "end of next week" is Friday, October 2.
- **Check-in:** if you've heard nothing by then, send one short note on Monday, October 5: "Hi Dana, just checking in on the Senior SRE role. I'm still very interested, and happy to answer anything else that would help." After that, leave it with the recruiter.

One note: the PagerDuty line is my addition to your answer. Keep it only if that's how you'd actually set it up.
```

## Why it works

Most follow-up emails are pure politeness. This prompt requires **one specific reference, one repaired answer and one value-add**, which is what makes a hiring manager reread it before the debrief.

**"Without over-apologizing"** matters: a fumbled answer fixed in one confident sentence reads as strength, while a paragraph of apology draws more attention to the miss. The **90-140 word limit** keeps it readable on a phone. Asking for **real dates** for sending and checking in removes the "how long should I wait?" guesswork, and the LinkedIn version covers the common case where you never got their email.

## When not to use it

Don't use the repair move for a major miss, such as failing a core technical exercise; one email won't change that. Some companies ask candidates not to contact interviewers directly; if so, send it through the recruiter. And never share anything from a previous employer that isn't yours to share: sanitize properly or offer to describe it.

---

Canonical HTML: https://promptabide.com/bides/follow-up-email-after-job-interview
Agent guide: https://promptabide.com/llms.txt · https://promptabide.com/agent-instructions.md
Sitemap: https://promptabide.com/sitemap.xml