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]
ヒント彼らの実際の仕事歴から 1 つの具体的なことを名前を付けます。 パッシブ候補者はジェネリックアウトリーチを即座に削除します。 単一の具体的な観察はあなたが本当の宿題をしたことを信号します。
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]
ヒント彼らが達した段階を指定することは正しいトーンを強制します。 1 行のアプリケーション拒否と最後のラウンド拒否は異なる人間の状況であり、異なる読む必要があります。
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?
ヒント「主要なトレードオフ」を推奨ではなく推奨で終わることは、採用チームを決定に保ちます。 彼らは持っているコンテキストを持ってあなたはしていません。サマリーは実際のジレンマを解決するのではなく表面するときが最も有用です。