ChatGPTGeminiClaude
수동적 지원자에게 리크루터 아웃리치 이메일
현재 위치에 만족한 지원자를 호기심을 갖게 하는 개인화된 아웃리치를 작성합니다.
예시 출력
Subject: [Candidate name] — a role that looked like you
Hi [Name],
Noticed your work leading the identity verification overhaul at [Current Company] — that's exactly the kind of gnarly infra problem the team here is walking into next.
[Hiring Company] is a 200-person fintech building a compliance stack from scratch. The engineering org is small enough that your work ships fast, and the domain is the same one you've been doing for the past three years — just with more scope.
Would a 20-minute call next week be worth your time? Happy to share more before you decide if it's a fit.
[Your name]
팁직급이 아닌 실제 업무 이력에서 구체적인 무언가를 명시하세요. 수동적 지원자는 일반적인 아웃리치를 즉시 삭제합니다. 단일 구체적인 관찰은 당신이 실제 숙제를 했다고 신호합니다.
ChatGPTGeminiClaude
역할별로 맞춘 면접 질문
특정 직무에 대한 기술 및 행동 기반 질문을 생성합니다.
예시 출력
Technical
1. "Walk me through how you've structured a sourcing funnel for a role with under 200 qualified candidates in the market." → Strong answer: a specific example with search strategy, outreach rate, and how they adapted.
Behavioral
2. "Tell me about a time a hiring manager wanted a candidate you thought was wrong for the role. What did you do?" → Strong answer: held a position with data, didn't just defer.
Thinking questions
3. "This role has a two-week time-to-fill target. What breaks first and how do you manage it?" → Strong answer: surfaces pipeline risk, sets expectations early, doesn't promise what they can't control.
팁같은 요청에서 '강한 답변에 무엇이 포함되는가'를 요청하세요. 모델이 좋게 들리는 질문을 생성하는 대신 실제로 배우려는 것이 무엇인지 생각하도록 강제합니다.
ChatGPTGeminiClaude
면접을 위해 지원자가 준비하도록 도와주기
지원자가 준비되고 자신 있게 참석하도록 준비 가이드를 만듭니다.
예시 출력
Prep guide for [Name] — [Role] interview at [Company], [Date]
Research before you go in:
- Their most recent product launch or press release (check their blog).
- Who's interviewing you — find them on LinkedIn, note anything you have in common.
- Their current job listings to understand where the team is growing.
Likely themes to prep:
- Cross-functional influence: they'll want to know how you work with Engineering without authority.
- Prioritization under ambiguity: they're a Series B company, resources are tight.
- Stakeholder communication: expect a "tell me about a time" on bad news delivery.
Questions to ask them:
- "What does success look like in the first 90 days?"
- "What's the biggest challenge the team is navigating right now?"
Day of: Log in five minutes early. Have your notes somewhere you can glance without reading off them.
팁직무 설명을 프롬프트에 붙여넣고 모델에 면접자가 실제로 신경 쓰는 것이 무엇인지 추출하도록 하여 '가능한 주제'를 개인화하세요. 일반적인 조언을 작성하는 대신입니다.
ChatGPTGeminiClaude
직무 사양에 대한 이력서 심사
이력서가 역할과 얼마나 일치하는지, 공백이 정직하게 표시된 것을 요약합니다.
예시 출력
Overall fit: Possible — strong on the technical side, light on the team leadership the spec asks for.
Matches:
- 6 years in data engineering, all in fintech (spec asks 4+).
- Hands-on with dbt and Snowflake, which the spec names explicitly.
- Led a pipeline migration project end-to-end.
Gaps:
- No evidence of managing other engineers — spec requires leading a team of 3+.
- No mention of vendor negotiation or tooling budget ownership.
- ML pipeline experience listed but no specifics; could be shallow.
Question to ask: "The role manages two junior engineers from day one — have you had direct reports before, and what did that look like?"
팁'모호하면 명시'를 추가하여 모델이 공백을 자선적으로 읽는 것을 유지하세요. 누락된 요구사항을 가린 이력서 심사는 모두의 시간을 낭비합니다.
ChatGPTGeminiClaude
친절한 지원자 거절 이메일
지원자를 따뜻함과 거짓 희망 없이 거절합니다.
예시 출력
Subject: your application — [Role] at [Company]
Hi [Name],
Thank you for making time through all three rounds — you asked sharp questions and made the process easy. After a close decision, we're moving forward with another candidate whose background maps more directly to the infrastructure work we're starting immediately.
I'm sorry it didn't come together. I hope it's useful to know it was a competitive field, not anything you could have done differently.
Wishing you well in the search.
[Your name]
팁그들이 도달한 단계를 명시하면 올바른 톤이 강제됩니다. 원라인 지원 거절과 최종 라운드 거절은 다른 인간 상황이며 다르게 읽혀야 합니다.
ChatGPTGeminiClaude
채용 공지 이메일
지원자를 입사시키고 주요 조건을 다루는 제안을 배달합니다.
예시 출력
Subject: offer — [Role] at [Company]
Hi [Name],
We'd love to have you join the team. Here's a summary of what we're offering:
- Role: Senior Data Engineer
- Base salary: $148,000
- Equity: 0.08% over four years with a one-year cliff
- Start date: July 14, 2025
- Offer open until: June 20, 2025
A formal offer letter with full details will follow from our People team today.
We spent a lot of time on this search and kept coming back to you — your work on the migration project and the way you think through tradeoffs is exactly what we need. We're excited.
Let me know if you have any questions before then. Looking forward to your answer.
[Your name]
팁응답 마감을 제안 편지가 아닌 이메일에 포함하세요. 지원자는 앞에 날짜가 있으면 더 명확하게 느껴지고 연장된 침묵의 기회를 줄입니다.
ChatGPTGeminiClaude
면접 노트를 디브리프로 전환하기
생 면접 노트를 구조화된 평가로 변환합니다.
예시 출력
Candidate: Maya Chen | Role: Head of Growth | Interviewer: J. Park
Headline: Strong strategic thinker, but gave thin answers when pushed on execution specifics.
Strengths:
- Articulated a full-funnel growth model unprompted — showed systems thinking.
- Comfortable with ambiguity; described building a team from scratch at her last role.
Concerns:
- When asked about a campaign that underperformed, pivoted to what the team learned without owning her own call that was wrong.
- No specific CAC or payback period numbers cited in any example.
Standout moment: Her reframe of retention as a growth lever landed well — clear, original, and grounded.
Recommendation: Hold — ask a second interviewer to pressure-test the execution gap before advancing.
팁'눈에 띄는 순간'을 명시적으로 요청하세요. 면접팀이 스스로 해석해야 하는 글머리 목록 대신 디브리프 대화를 위한 구체적인 닻을 제공합니다.
ChatGPTGeminiClaude
소셜 미디어에서 채용공고 홍보하기
역할이 공유되고 지원되도록 하는 소셜 포스트를 작성합니다.
예시 출력
The person we're looking for has probably built a sourcing function from scratch before — and has opinions about what they'd do differently.
[Company] is hiring a Head of Talent. We're 80 people, pre-IPO, and have never had a full-time recruiter. The next 18 months will add about 40 more. You'd build the process, pick the tools, and own the brand — no inherited playbook.
What we're not: a slow-moving machine where you manage a pipeline someone else designed.
What we are: a team that wants to hire well and is willing to invest in doing it right.
If this sounds like the kind of problem you want, the details are here: [link]
If it sounds like someone you know, tag them.
팁애플리케이션이 아닌 공유를 위해 쓰면 구조가 바뀝니다. 적합하지 않은 읽기자가 친구가 왜 신경 쓸지 이해하도록 해야 합니다. 그 2차 독자를 위해 작성하세요.
ChatGPTGeminiClaude
면접 스코어카드 만들기
느슨한 노트를 공정한 비교를 위한 일관된 스코어카드로 전환합니다.
예시 출력
Candidate: Priya Nair | Role: Senior Product Manager
| Criterion | Rating | Evidence |
|---|---|---|
| Strategic thinking | 4 | Mapped the competitive landscape unprompted and identified a positioning gap. |
| Cross-functional influence | 3 | Solid example with Engineering; less clear on how she handles Sales conflict. |
| Data fluency | 3 | Comfortable with funnel metrics; SQL depth not assessed. |
| Communication clarity | 4 | Explained a complex tradeoff in under two minutes without jargon. |
| Domain knowledge | 2 | Fintech background is thin; prior work is primarily e-commerce. |
| Leadership | Not assessed | No direct reports questions asked in this round. |
Overall: 3.2 | Signal: Advance — with a note to probe domain fit in the next round.
팁'평가되지 않음'을 유효한 평가로 포함하면 스코어카드가 면접보다 더 완전하게 보이지 않습니다. 데이터의 간격은 다음 면접자에게 유용한 정보입니다.
ChatGPTGeminiClaude
전화 심사 질문 목록
15분 전화 심사를 계획하여 빠르게 필터링하되 차갑게 하지 않습니다.
예시 출력
Warm-up (keep both)
1. "How did you find out about this role?" — reveals whether they sought us out or got blasted.
2. "What does your week typically look like in your current job?" — gets them talking, helps you calibrate pace.
Quick filters (ask all three)
3. "This role requires [specific certification] — do you currently hold that?" — hard stop if no.
4. "The target comp range is [range] — does that work for you?" — covers comp mismatch early.
5. "We're planning a start date around [date] — any constraints on your end?" — surfaces notice period issues.
Motivation / culture
6. "What would need to be true about a new role for you to say it was the right move?" — cut this if short on time.
7. "What's one thing about your current setup you're hoping changes?" — honest answer tells you a lot.
Closing: "I'll follow up by [day] with next steps. Any questions for me before we wrap?"
팁첫 5분에 보상과 어려운 요구사항을 넣으세요. 12분에 불일치를 발견하는 것은 시간을 낭비합니다. 따뜻한 질문은 유지할 가치가 있습니다. 콜드 심사는 더 나쁜 신호를 생성합니다.
ChatGPTGeminiClaude
네트워크에 소개를 요청하기
사람들이 좋은 지원자를 실제로 소개하도록 하는 이메일을 작성합니다.
예시 출력
Subject: a quick ask — do you know a great Head of Talent?
Hi [Name],
I'm filling a Head of Talent role at [Company] and thought of you immediately — you know a lot of strong HR and recruiting people.
I'm looking for someone who's built a recruiting function from scratch at a growth-stage company and has opinions about how to do it well. Not necessarily someone in a current search, just someone good.
If anyone comes to mind, just reply with their name or forward this email — I'll take it from there.
Thanks for thinking of me, and no worries if no one comes to mind.
[Your name]
팁요구사항 목록이 아닌 '인간의 조건'으로 원하는 사람을 설명하세요. 당신의 연락처가 실제로 알고 있는 사람을 그리기가 훨씬 쉽습니다. 직무 설명은 사람들이 네트워크가 아닌 구직 게시판을 생각하도록 만듭니다.
ChatGPTGeminiClaude
최종 지원자를 나란히 비교하기
2~3명의 최종 지원자를 명확한 비교로 요약합니다.
예시 출력
| Criterion | Candidate A (Sara) | Candidate B (Tom) | Candidate C (Lea) |
|---|---|---|---|
| Technical depth | High | Medium | High |
| Leadership exp. | 3 direct reports | None | 6 direct reports |
| Domain fit | Strong (SaaS) | Moderate | Weak (retail only) |
| Communication | Clear, concise | Strong, verbose | Clear |
| Culture signals | Collaborative | Independent | Collaborative |
Case for Sara: Built and scaled a 3-person team in a similar product org. Strong on ambiguity; interview showed she works well without a playbook.
Case for Tom: Highest technical ceiling in the group. Would need to grow into the leadership scope, but the raw thinking is there.
Case for Lea: Most leadership experience by volume, though in a different industry. Strong communicator; the domain gap is the real question.
Key tradeoffs: Do you need someone who can lead today, or someone you can develop? How much does the industry gap matter given your onboarding capacity?
팁권장사항이 아닌 '주요 트레이드오프'로 끝내세요. 이는 채용 팀을 결정에 유지합니다. 요약이 결정을 해결하는 대신 실제 딜레마를 표면화할 때 가장 유용합니다.