Gemini prompts for HR job posts, interviews and onboarding
Copy-ready prompts for job posts, interview kits, policy drafts and onboarding notes. This is not legal advice. Do not invent labor law; counsel reviews any posting or policy before it goes out.
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.
Job Posts
5 promptsPosting from hiring notes
1/30✨ What it does
Builds a labelled job post from your hiring notes, with duties and must-haves taken only from what you pasted. Counsel still reviews the draft before it is published.
Turn these hiring notes into a job post draft for [ROLE TITLE] on team [TEAM NAME]. Notes: [PASTE HIRING NOTES]. Output labelled blocks: Role in one line, What the person does (5 bullets), Must-haves quoted from my notes, Nice-to-haves, How to apply using [HOW TO APPLY]. Keep the draft under 350 words. If a duty, location, work mode or must-have is missing, write [VERIFY] in that block. Do not invent a labor rule, visa, pay band, equity line or benefit I did not paste. This draft is not a legal posting.
Pro tip: Paste the intake notes, not a competitor posting you admire.
Must-have versus nice-to-have split
2/30✨ What it does
Splits a pasted posting into quoted must-haves, nice-to-haves and vague lines. Vague lines stay tagged instead of being turned into hard rules.
Split this draft posting into must-haves and nice-to-haves using only its words. Draft: [PASTE JOB POST DRAFT]. Return two quoted lists, then a third list of lines too vague to sort. Mark each vague line [VERIFY]. Never invent a degree, years of experience, clearance, lift requirement or certificate the draft never stated. Do not add a legal disclaimer or a protected-class statement I did not supply.
Pro tip: Repeated skills and required language are must-haves. Once-mentioned tools are often nice.
Work mode and location lines
3/30✨ What it does
Drafts three location and work-mode lines from the site and mode you already approved, then picks the clearest. Blank hybrid days stay tagged, not guessed.
Write the location and work-mode lines for this role from facts I already approved. Role: [ROLE TITLE]. Site: [SITE OR CITY]. Work mode: [ON SITE, HYBRID OR REMOTE]. Days on site if hybrid: [DAYS ON SITE]. Output three candidate lines of 12 to 22 words, then pick the clearest and say why in 30 words. If [DAYS ON SITE] is blank and the mode is hybrid, write [VERIFY] rather than inventing a schedule. Do not invent a relocation package, a visa, a time-zone rule or a right-to-work claim.
Pro tip: Use the same site name your facilities team uses, not a nickname.
Inclusive wording pass
4/30✨ What it does
Flags phrases that may shut people out and suggests swaps only from your style notes. It will not add a legal sentence you did not supply.
Flag wording in this posting that may shut people out, using only style notes I give, not the law. Posting: [PASTE JOB POST]. Style notes I follow: [PASTE STYLE NOTES]. Return a table with columns Phrase, Why it may shut people out in 15 words, Suggested swap from my notes. If my notes do not support a swap, write [VERIFY] in Suggested swap. Do not invent a statute, an EEO line, a disability accommodation or a pay-transparency sentence. This pass is editorial, not legal advice.
Pro tip: Paste your internal style notes. The model should not write employment law.
How-to-apply block check
5/30✨ What it does
Runs ten checks on the how-to-apply block against the process and deadline you named. Missing dates and portals stay tagged instead of being filled in.
Check the how-to-apply block on this posting against the process I named. Posting: [PASTE JOB POST]. Process I want: [APPLY PROCESS]. Deadline if any: [DEADLINE]. Output ten checks marked Ok, Fix or [VERIFY] covering where to send, what to attach, who to contact and the deadline. If I left [DEADLINE] blank, mark that check [VERIFY] and do not invent a close date. Never invent an ATS name, a portal URL or a legal notice period.
Pro tip: Paste the live apply URL only if candidates will actually use it.
Interview Kits
5 promptsQuestion kit from the posting
6/30✨ What it does
Builds eight interview questions mapped to must-haves in the posting, with a strong and a weak answer sketch. Skills you did not list stay out of the kit.
Build an interview kit of 8 questions for [ROLE TITLE] from this posting and these must-haves. Posting: [PASTE JOB POST]. Must-haves: [MUST HAVES]. Output a table with columns Question, Must-have it tests, What a strong answer names, What a weak answer skips. Use only skills in the posting or must-haves. If a must-have has no matching question, write [VERIFY] in that row. Do not invent a case study, a live coding task, a salary question or a medical question. This kit is not legal advice on what you may ask.
Pro tip: One question per must-have beats a long list that tests nothing twice.
Scorecard from requirements
7/30✨ What it does
Turns your requirements into a 1 to 4 interviewer scorecard with evidence notes. Vague requirements stay tagged instead of becoming personality scores.
Turn these requirements into a 1 to 4 scorecard for interviewers of [ROLE TITLE]. Requirements: [PASTE REQUIREMENTS]. Output a table with columns Criterion, 1 looks like, 2 looks like, 3 looks like, 4 looks like, Evidence to write down. Keep each cell under 20 words. If a requirement is too vague to score, write [VERIFY] in Criterion and skip the scale. Never invent a personality trait, a culture fit score, a legally sensitive criterion or a years-of-experience cutoff I did not paste.
Pro tip: Keep culture out of the scorecard unless you defined observable behavior.
Forty-five minute loop agenda
8/30✨ What it does
Splits a 45 minute interview into timed blocks with a first question drawn from your topics. Missing questions stay tagged rather than filled with a surprise exercise.
Fill a 45 minute interview agenda for [CANDIDATE NAME] applying to [ROLE TITLE]. Interviewer: [INTERVIEWER ROLE]. Topics I must cover: [TOPICS]. Output a table with columns Block, Minutes, Goal and First question, across Welcome, Deep dive, Candidate questions and Close. Minutes must add up to 45. Draw questions only from [TOPICS]. If a topic has no first question I can support, write [VERIFY] in that cell. Do not invent a work sample, a take-home, a panel or a legal warning I did not list.
Pro tip: Keep the close block. Interviewers who run over skip the candidate questions.
Take-home brief from role notes
9/30✨ What it does
Writes a short take-home brief from your role notes, with a time cap and score notes you supplied. Blank hours stay tagged, and no live system is added.
Write a take-home brief of 180 to 220 words for [ROLE TITLE] from these role notes. Notes: [PASTE ROLE NOTES]. Time the candidate may spend: [HOURS ALLOWED]. What to submit: [SUBMIT FORMAT]. Include the task, the time cap, what good looks like in 3 bullets and how we will score it. If [HOURS ALLOWED] is blank, write [VERIFY] and do not invent a deadline or an unpaid hours figure. Never invent customer data, a live credential or a production system the candidate must touch.
Pro tip: Cap the hours at what you would do yourself on a weeknight.
Panel debrief notes sheet
10/30✨ What it does
Sorts debrief notes into quoted evidence against the scorecard you already agreed. Missing quotes and scores stay tagged; no hire vote is invented.
Turn this debrief into a notes sheet for [ROLE TITLE]. Raw notes: [PASTE DEBRIEF NOTES]. Criteria we agreed: [PASTE SCORECARD CRITERIA]. Output a table with columns Criterion, Quote from notes, Score if stated, Open question. Keep quotes word for word. If a criterion has no quote, write [VERIFY] under Quote. Do not invent a score, a hire vote, a salary recommendation or a reason a panelist did not write. Stay inside the pasted notes.
Pro tip: Paste each interviewer's notes separately so quotes stay attached to a person.
Policy Drafts
5 promptsGap list against current policy
11/30✨ What it does
Maps each requested change to a quoted section of the current policy and names the gap. Missing sections stay tagged; no new legal rule is added.
Compare this current policy to the change leaders asked for and list the gaps. Current policy: [PASTE CURRENT POLICY]. Requested change: [PASTE CHANGE REQUEST]. Output a table with columns Section, What it says now (quote), What the request asks, Gap in 20 words. If a section is missing from the current policy, write [VERIFY] in What it says now. Do not invent a statute, a notice period, an eligibility rule or a penalty. This is a gap list, not legal advice and not a new policy.
Pro tip: Paste the policy as staff see it, including the version date at the top.
Plain-language policy paragraph
12/30✨ What it does
Rewrites one policy paragraph in plain language for a named audience, listing what was simplified. Unclear rules stay tagged, and no new leave type is added.
Rewrite this policy paragraph in plain language for [EMPLOYEE AUDIENCE] without changing the rule. Paragraph: [PASTE POLICY PARAGRAPH]. Audience: [EMPLOYEE AUDIENCE]. Return the rewrite of 80 to 120 words, then three bullets on what you simplified and what you left as-is. If a rule, date, eligibility or exception is unclear, write [VERIFY] at that point. Never invent a legal right, a paid leave type, an hours threshold or a tax treatment. Counsel must review before this goes in the handbook.
Pro tip: Rewrite one paragraph at a time. Whole-handbook rewrites hide rule changes.
Policy change FAQ for staff
13/30✨ What it does
Writes six staff FAQ pairs from the change summary, audience and date you pasted. Open items stay tagged instead of being closed with a made-up exception.
Write 6 staff FAQ pairs about this policy change from the facts I pasted. Change summary: [PASTE CHANGE SUMMARY]. Who it applies to: [WHO IT APPLIES TO]. Effective date: [EFFECTIVE DATE]. Each answer 40 to 70 words. Cover who, when, what changes, what stays, who to ask using [WHO TO ASK], and what is still open. If [EFFECTIVE DATE] or [WHO TO ASK] is blank, write [VERIFY] in that answer. Do not invent an exception, a grandfather rule, a legal deadline or a penalty.
Pro tip: Name the real inbox people should write to, not a generic HR mailbox if that inbox is ignored.
Manager talking points for a change
14/30✨ What it does
Gives five huddle talking points with a say-this and do-not-say line from approved facts. Missing figures stay tagged, and no threat language is added.
Write manager talking points for a 10 minute team huddle about [POLICY NAME]. Facts they may use: [PASTE APPROVED FACTS]. Output 5 numbered points, each with a 25 word say-this line and a 15 word do-not-say line. End with one question managers should collect. Stay inside the approved facts. If a point needs a figure, date or eligibility rule I did not give, write [VERIFY] on that line. Never invent a legal threat, a firing example or a benefit cut I did not describe. This is not legal advice.
Pro tip: Give managers the do-not-say line. That is where off-script harm starts.
What this policy does not cover
15/30✨ What it does
Lists eight topics a reader might assume are covered that the draft actually leaves out. Silent scope items stay tagged for counsel, not filled in.
List what this draft does not cover, so we do not over-claim. Draft: [PASTE POLICY DRAFT]. Scope leaders named: [NAMED SCOPE]. Output 8 bullets of out-of-scope topics a reader might assume are included, each with a 20 word why-it-is-out line. If the draft is silent on a topic in [NAMED SCOPE], write [VERIFY] beside it. Do not invent a coverage, a jurisdiction, a contractor rule or a union term. Mark the list as a briefing for counsel, not a policy.
Pro tip: Readers assume a time-off policy covers every absence. Name the ones it does not.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. Easy-to-follow tutorials inside AI Academy, and the library keeps growing.
Onboarding Notes
5 promptsFirst-week calendar from inputs
16/30✨ What it does
Lays out a Monday to Friday first week from booked meetings, tools and the named buddy. Blank start dates and missing people stay tagged.
Build a first-week calendar for [NEW HIRE NAME] starting [START DATE] in role [ROLE TITLE]. Meetings already booked: [PASTE MEETINGS]. Tools they need: [TOOLS]. Buddy: [BUDDY NAME]. Output a Monday to Friday table with columns Day, Morning, Afternoon and Owner. Place each booked meeting on its day. If a day has no meeting, write a setup or reading block only from [TOOLS] or my notes. If [START DATE] or [BUDDY NAME] is blank, write [VERIFY] rather than inventing a date or a person. Do not invent a training, a system or a legal form I did not list.
Pro tip: Paste the calendar holds first. Empty mornings are where new hires get lost.
Welcome email the day before
17/30✨ What it does
Drafts a 120 word welcome email with arrival place, greeter and what to bring. Missing logistics stay tagged, and no background-check claim is added.
Draft a welcome email of about 120 words to [NEW HIRE FIRST NAME] arriving [START DATE] for [ROLE TITLE]. Include where to arrive [ARRIVAL PLACE], who greets them [GREETER NAME] and what to bring [WHAT TO BRING]. Tone warm and plain, no exclamation marks, one question at the end. If a place, greeter or date is missing, write [VERIFY] in its place. Do not invent a badge process, a background-check status, a visa step or a benefit enrollment I did not name.
Pro tip: Send it the afternoon before start day, while the person can still ask a question.
Systems access request list
18/30✨ What it does
Turns the manager's tool list into a ticket-ready access table with approver and day needed. Unstated access levels stay blank and tagged.
Turn this role's tools into a systems access list IT can ticket. Role: [ROLE TITLE]. Tools named by the manager: [PASTE TOOL LIST]. Manager who approves: [MANAGER NAME]. Output a table with columns System, Access level if stated, Approver, Day needed. If an access level is not stated, write [VERIFY] and leave Access level blank. Never invent a production permission, an admin role, a shared password or a system the manager did not name. Do not invent a security policy.
Pro tip: Ask the manager for the exact group name, not just the product name.
Thirty sixty ninety note
19/30✨ What it does
Drafts a 30-60-90 note with three outcomes per block from the manager's goals. Empty blocks stay tagged; no quota is added.
Draft a 30-60-90 note for [NEW HIRE NAME] in [ROLE TITLE] from these goals. Goals the manager set: [PASTE GOALS]. Output three labelled blocks, 30 days, 60 days and 90 days, each with 3 outcomes and 1 check-in question. Use only outcomes in the pasted goals. If a block has no outcome I can support, write [VERIFY] in that block. Do not invent a quota, a revenue target, a headcount or a certification deadline. This is a working note, not a contract.
Pro tip: Outcomes should be visible to the new hire, not only to the manager.
Buddy intro for week one
20/30✨ What it does
Writes a 90 word day-one note from the named buddy, with channel and coffee slot if you supplied them. A blank slot stays tagged instead of a guessed time.
Write a 90 word intro the buddy [BUDDY NAME] can send [NEW HIRE FIRST NAME] on day one. Team: [TEAM NAME]. How to reach the buddy: [BUDDY CHANNEL]. First coffee slot if booked: [COFFEE SLOT]. Mention one way the buddy can help from [HELP THEY OFFER]. If [COFFEE SLOT] is blank, write [VERIFY] and do not invent a time. Never invent a team ritual, a nickname, an org fact or a benefit. Keep it human and short.
Pro tip: Give the buddy one concrete offer of help, such as walking the building once.
Offers and Close
5 promptsOffer summary from approved terms
21/30✨ What it does
Turns approved terms into a labelled one-page summary with figures copied as written. Missing pay or dates stay blank and tagged, and no new term is added.
Write a one-page offer summary from terms already approved, for [CANDIDATE NAME] and [ROLE TITLE]. Approved terms: [PASTE APPROVED TERMS]. Start date if set: [START DATE]. Output labelled lines: Role, Team, Start, Pay as written in the terms, Other terms as written, Next step [NEXT STEP]. Copy figures only from the pasted terms. If a figure or start date is missing, write [VERIFY] and leave it blank. Do not invent a bonus, equity, benefit, at-will line, noncompete or notice period. This is not an offer letter and not legal advice.
Pro tip: Paste the approved term sheet, not a prior candidate's letter.
Decline note after a kind no
22/30✨ What it does
Drafts a short decline email from the reason and future path you are willing to share. Blank reasons stay tagged; no invented later opening is promised.
Draft a 90 word decline email to [CANDIDATE NAME] for [ROLE TITLE]. Reason I may share: [SHAREABLE REASON]. What stays open if anything: [FUTURE PATH]. Thank them for [WHAT TO THANK]. Keep it warm and short. If I left [SHAREABLE REASON] blank, write [VERIFY] and do not invent a reason, a ranking or another candidate. Never invent a later opening, a salary, or a legal claim about the process.
Pro tip: If you cannot share a reason, say so plainly rather than inventing feedback.
Start-date confirmation note
23/30✨ What it does
Confirms a locked start date with arrival place and paperwork owner. Missing facts stay tagged, and no screening result is claimed.
Write an 80 word confirmation to [CANDIDATE NAME] that start date [START DATE] for [ROLE TITLE] is locked. Include where to arrive [ARRIVAL PLACE] and who owns remaining paperwork [PAPERWORK OWNER]. If any of those three facts is blank, write [VERIFY] in its place. Do not invent a background-check result, a drug-screen step, a visa, an I-9 rule or a benefit start date. This note confirms logistics, it is not legal advice.
Pro tip: Send this only after the written offer is signed, so the date is real.
Internal new-hire announcement
24/30✨ What it does
Drafts a short internal announcement from approved bio facts and a named contact. Unapproved employers, schools or quotes stay tagged.
Draft a 70 word internal note announcing [NEW HIRE NAME] joining [TEAM NAME] as [ROLE TITLE] on [START DATE]. Facts I may share: [PASTE APPROVED BIO FACTS]. Who to contact with questions: [CONTACT NAME]. Use only the approved facts. If a prior employer, school or start date is not in the facts, write [VERIFY] rather than inventing it. Do not invent a personal detail, a quote or a photo caption the person did not approve.
Pro tip: Show the draft to the new hire before it hits the team channel.
Pre-board checklist for the hiring manager
25/30✨ What it does
Builds a 12 item pre-board checklist in four groups from items you already know. Unnamed owners stay tagged, and no extra vendor or legal form is added.
Make a 12 item pre-board checklist for the hiring manager of [ROLE TITLE] starting [START DATE]. Items I already know: [PASTE KNOWN ITEMS]. Group under Desk, Access, People and First-week plan. Mark each item Owner if I named one, else [VERIFY]. Add no vendor, no background vendor, no drug screen and no legal form I did not list. Do not invent a union step or an immigration step. This checklist is operational, not legal advice.
Pro tip: Name the owner as a person, not a department, or the item will slip.
Go from copy-pasting to actually mastering AI.
AI Academy: hands-on tutorials on ChatGPT, Claude, Midjourney, and many other tools. New tutorials are added regularly.
People Ops Notes
5 promptsHeadcount request one-pager
26/30✨ What it does
Turns a manager intake into a one-page headcount request with the work that is stuck and the decision asked. Missing figures stay tagged; no revenue claim is added.
Turn this intake into a one-page headcount request for [ROLE TITLE] on [TEAM NAME]. Intake: [PASTE INTAKE]. Output labelled blocks: Why this role now, Work that is stuck, What we tried, Cost of waiting in the manager's words, and Decision asked of [DECISION MAKER]. Stay inside the intake. If a figure, date or prior attempt is missing, write [VERIFY]. Do not invent a revenue impact, a competitor hire, a legal risk or a headcount cap. This is a briefing, not a budget or legal memo.
Pro tip: Quote the manager on the cost of waiting. Paraphrase is how numbers get inflated.
Exit comment themes
27/30✨ What it does
Groups pasted exit comments into at most six themes with exact quotes and counts. Thin comments stay tagged; no legal claim is inferred.
Theme these exit comments without adding causes we did not write. Comments: [PASTE EXIT COMMENTS]. Output a table with columns Theme, Exact short quote, Times it appears, Open question. At most 6 themes. Keep quotes word for word. If a comment is too thin to theme, write [VERIFY] beside it. Do not invent a discrimination claim, a legal violation, a named manager fault or a trend the comments do not support. This is a notes sheet, not an investigation and not legal advice.
Pro tip: Paste the comments as written. Cleaning them first hides the words people used.
Skip-level agenda from themes
28/30✨ What it does
Turns named themes into a 25 minute skip-level agenda with a question and a do-not-promise line. Vague themes stay tagged instead of becoming promises.
Build a 25 minute skip-level agenda for [LEADER NAME] with [TEAM NAME] from these themes. Themes: [PASTE THEMES]. Output a table with columns Block, Minutes, Question to ask, What not to promise. Minutes add up to 25. Questions must come from the themes. If a theme is too vague to ask about, write [VERIFY] in Question to ask. Do not invent a reorg, a raise, a headcount promise or a legal commitment. This agenda is a listening plan, not advice.
Pro tip: Write the do-not-promise line first. Leaders fill silence with commitments.
Review cycle timeline from dates
29/30✨ What it does
Turns the dates you already set into a review-cycle table with owners and a short staff-facing line. Blank dates stay tagged; no rating or bonus rule is added.
Lay out the review cycle for [CYCLE NAME] from dates I already set. Kickoff: [KICKOFF DATE]. Self-review due: [SELF REVIEW DUE]. Manager due: [MANAGER DUE]. Calibrations: [CALIBRATION WINDOW]. Share date: [SHARE DATE]. Output a table with columns Milestone, Date, Owner from [OWNER LIST], and Staff-facing line of 12 words. If a date is blank, write [VERIFY] and do not invent one. Never invent a rating label, a bonus formula, a legal appeal step or a performance-improvement rule.
Pro tip: Put the staff-facing line in the calendar invite so managers say the same thing.
Org change note from approved facts
30/30✨ What it does
Drafts a 130 word org-change note from approved facts, the date and who to ask. Unapproved names and cuts stay tagged; no layoff language is added.
Draft a 130 word org-change note for [AUDIENCE] from facts already approved. Approved facts: [PASTE APPROVED FACTS]. Effective date: [EFFECTIVE DATE]. Who to ask: [WHO TO ASK]. Cover what changes, what does not, and the date. If a name, title or date is not in the facts, write [VERIFY]. Do not invent a layoff, a role cut, a legal rationale, a successor or a quote. This is an internal note, not legal advice and not a formal notice.
Pro tip: List what does not change. That is the line people read twice.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.
Related guides