67 lines
3.3 KiB
Markdown
67 lines
3.3 KiB
Markdown
# Thank-you and follow-up notes
|
|
|
|
Drafts only. The owner sends them himself. Nothing is emailed, messaged or submitted from the chat.
|
|
|
|
## Shared rules
|
|
|
|
- **No new claims.** Every substantive statement comes from the submitted CV, cover letter or posting. A note that introduces a skill or experience not on the paper is a fabrication vector. The one addition allowed is something the interviewer actually said, as the owner reports it.
|
|
- Check the draft against the pitfalls document before presenting it.
|
|
- Match the application's language and the register of the submitted cover letter.
|
|
- Style: warm but direct, no em-dashes, no clichés, no pressure, no "just checking in", no apology for writing.
|
|
- Address the named contact person if known; otherwise the team, in the application's language.
|
|
- Iterate until the owner is happy. Then remind him of the date sent, since the chat keeps no record.
|
|
|
|
## Channel shape
|
|
|
|
| Channel | Shape |
|
|
|---|---|
|
|
| Email | Subject line reusing the application's headline or reference ID, greeting, body, sign-off |
|
|
| LinkedIn message | Shorter, no subject, no formal sign-off |
|
|
| Portal message | Plain text, no formatting, no subject unless the form asks |
|
|
|
|
Ask which channel if it is not clear from the inputs.
|
|
|
|
## Thank-you note (after an interview)
|
|
|
|
Offer one whenever the owner reports a completed round. Send the same day or the next.
|
|
|
|
- 2-4 sentences, or up to about 100 words for email.
|
|
- Thank the interviewer for the time and one specific thing discussed.
|
|
- One sentence connecting that topic to a fact from the submitted materials.
|
|
- Optional: one line restating interest in the role.
|
|
- One note per interviewer when there were several, each referencing something different.
|
|
|
|
## Follow-up (quiet application)
|
|
|
|
Qualifies when the application was sent 10 or more days ago (or 10+ days after the last follow-up) with no reply, and fewer than two follow-ups have been sent. Ask the owner for the date applied, the dates of any earlier follow-ups, and whether the employer gave a timeline. If the employer stated a timeline that has not passed, advise waiting.
|
|
|
|
Draft, 60-120 words:
|
|
|
|
1. One sentence restating interest in the specific role, with the reference ID if there is one.
|
|
2. One concrete value reminder drawn from the submitted materials (a result or skill that matches a stated requirement).
|
|
3. One polite question about the timeline or next step.
|
|
|
|
Example (generic, email):
|
|
|
|
```
|
|
Subject: Platform Engineer (ref. 2041): follow-up
|
|
|
|
Dear Ms Novak,
|
|
|
|
I applied for the Platform Engineer role on 12 May and remain very interested. The posting's focus on reducing deployment friction matches the work I described in my application, where I cut release time from 40 to 8 minutes for a team of twelve.
|
|
|
|
Could you tell me where the process stands and when you expect to decide on interviews?
|
|
|
|
Kind regards,
|
|
Alex Example
|
|
```
|
|
|
|
## Limits
|
|
|
|
- At most two follow-ups per application. After the second goes unanswered, do not draft a third; say so and suggest treating the application as closed unless the employer writes.
|
|
- If the owner mentions an actual reply (invitation, rejection), drop the follow-up and help with that instead: a pack for the new stage, or a short thank-you to a rejection if he wants one.
|
|
|
|
## Closing blocks
|
|
|
|
If drafting surfaced a fact the owner added or corrected, or a new kind of mistake, end with the blocks from SKILL.md.
|