불합격 통보 메일 쓰는 프롬프트
평가 기준에 근거한 사유를 쓰되 분쟁 소지를 피합니다.
| 분류 | 사무 › 인사·채용 |
|---|---|
| 태그 | 초안작성검토직장인 |
| 갱신일 | · 변경 1회 |
Write a rejection message. First, decide what can be said: - **Can say** — a requirement the role needed that the assessment did not evidence. Stated as a gap between the role and the evidence, not as a judgment of the person. - **Cannot say** — anything about personality, fit, appearance, circumstances, or comparisons to other candidates. *These create disputes and are not what was assessed.* - **Should not say** — "we went with someone more qualified", "keep in touch", "we'll keep your resume on file" unless it is true. Then write it: 1. The decision, in the first line. No build-up. 2. One specific reason drawn from the rubric, if policy allows sharing it. 3. What was genuinely good, if there was something. One line, specific. 4. Whether to apply again and when, only if true. 5. Close. No apology beyond one sentence. Under 150 words. Then: - What to say instead if company policy forbids giving reasons. *A short honest "we cannot share details" beats a vague invented reason.* - If they ask for detailed feedback, what is safe to give. - Anything in my assessment that should not be written down at all — flag it as a process problem. Rules: - *Do not invent a reason to be kind.* An invented reason sends them to fix the wrong thing. - No false encouragement. - Send it. A candidate who hears nothing is treated worse than one who is rejected clearly. **Write it as a complete message, ready to send:** open with a greeting and end with a closing line — no subject line. ***Use the formal business register of the language it is written in*** (in Korean, 합니다체) unless I have said the relationship or the tone is casual. *Short means the point comes first — it does not mean dropping the greeting, the courtesy, or the closing.* *The greeting and the sign-off do not count toward any first-line or length rule above.*
붙여 넣으면 맨 아래에 채울 칸(지원자·전형 단계 · 평가 결과 · 회사 방침)이 나옵니다
어떤 프롬프트인가
불합격 통보는 대개 아무 내용이 없어서 지원자에게 상처만 남긴다. 이 프롬프트는 말해도 되는 것과 말하면 안 되는 것을 갈라, 짧고 구체적인 사유를 남긴다.
변경 이력
| 날짜 | 무엇이 왜 바뀌었나 |
|---|---|
| 격식 기본값(합니다체)과 완성된 메일·메시지 형식(인사·맺음말·서명) 지시를 넣었다 |
같은 분류의 프롬프트
| 연차 잔액 조정 처리 프롬프트 | |
| 이미지 출퇴근 추적 프롬프트 | |
| 대학 조직도 설계 프롬프트 | |
| 인재 개발 시스템 설계 프롬프트 | |
| 회사 보상 체계 설계 프롬프트 |