Back to Discover

#resume

1 prompt found

Job Seeker Prompt: Job Posting to Fit Check and Next Steps
✍️ Writing

Job Seeker Prompt: Job Posting to Fit Check and Next Steps

Ppromptstudio·Oct 11, 2026
No rating

Paste a job posting and your real experience: get must-have vs nice-to-have, an evidence map, honest gap answers, an apply or skip call, and true resume edits.

Act as a career coach and former in-house recruiter who reads a job posting line by line with a job seeker, matches each requirement to proof from their real work history, and helps them decide whether to apply without stretching a single fact. Inputs: - The full job posting, pasted: [JobPosting] - My real experience: roles, dates, tools, and results I can back up: [MyExperience] - My non-negotiables: pay floor, location, schedule: [MustHaves] - Gaps I already know about: [KnownGaps] - People I actually know at the company or in the field: [Contacts] - Posting date and any application deadline: [PostingDates] Generate: 1. Requirement split: must-have versus nice-to-have, quoting the posting's own words for each. 2. Evidence map: a table with each requirement, the matching line from MyExperience, and a rating of strong, partial, or none. Never fill a cell with experience I did not list. 3. Honest gap answers: for each partial or none, one true sentence I can say in an interview and one concrete step to close the gap. 4. Fit with MustHaves: pay, location, and schedule checked against the posting; flag anything the posting does not state. 5. Apply, ask first, or skip: one recommendation with three reasons. 6. Resume edits: three bullet rewrites that reword only facts in MyExperience to use the posting's terms where they are true. 7. Outreach note: under 90 words to one person in Contacts, asking a real question about the role, not a referral demand. 8. Questions to ask in the interview: three, each tied to a line in the posting. 9. Next three steps with dates counted from PostingDates. Rules: - Do not invent or round up years, titles, numbers, tools, or degrees. - If a requirement is unclear, list it as a question, not a guess. - Keep personal ID numbers out of every output.