آماده‌سازی سریع مصاحبه رفتاری: از آگهی شغلی تا داستان‌های STAR که زیر فشار فراموش نمی‌کنی
چرا این پرامپت اهمیت دارد
Behavioral interviewers aren't scoring general competence — they're scoring specific, structured stories mapped to the competencies the role actually needs. Candidates without a pre-mapped story set tend to repeat the same safe anecdote for every question, ramble past the two-minute mark while hunting for the right ending, or realize mid-answer they picked a story that doesn't actually answer what was asked. None of that is a knowledge gap. It's a retrieval problem under pressure, and the fix is doing the retrieval in advance — not practicing interviews in the abstract.
ما از آن برای چه استفاده می‌کنیم
You have a final-round interview in three days for a senior role. You have 12+ years of relevant experience, but when you try to recall specific stories under time pressure, you blank, or you default to the same two anecdotes for every question regardless of what's actually being asked.
پرامپت
Role: Act as an experienced behavioral interview coach who has sat on both sides of the hiring table — conducting interviews as a hiring manager and prepping candidates for them — and knows what interviewers are actually listening for versus what candidates think they're being asked.
Context: I have an interview for [JOB TITLE] at [COMPANY NAME] on [INTERVIEW DATE]. Here is the job posting: [PASTE JOB DESCRIPTION]. Here is my resume or career background: [PASTE RESUME OR CAREER SUMMARY]. The interview format is [NUMBER OF ROUNDS AND TYPE, e.g. "one 45-minute behavioral round with the hiring manager"].
Task:
1. Identify the 6 to 8 competencies this specific role is most likely to probe for, based on the job posting — not a generic list, but ones tied to language actually in the posting (e.g. "cross-functional influence" if it mentions working across teams, "ambiguity" if it mentions a fast-changing environment).
2. For each competency, write the single most likely behavioral question an interviewer would ask to probe it.
3. Mine my background for the single best story that answers each question. If one story can answer multiple competencies, use it for all of them and tell me which ones overlap, so I don't memorize more stories than I need.
4. Write each answer in full STAR format (Situation, Task, Action, Result), quantifying the Result wherever my background gives you a number to work with.
Constraints:
- Keep each STAR answer to roughly 150-200 words — long enough to be substantive, short enough to deliver out loud in under two minutes.
- Do not invent facts, numbers, or outcomes that aren't in my background. If a detail is missing, flag it as [NEED DETAIL: what's missing] instead of making something up.
- Favor stories that show judgment under ambiguity over stories that only show technical competence, unless the role is purely technical.
- Avoid generic corporate language ("synergy," "leverage," "move the needle") in the answers themselves.
Output Format:
For each competency:
**Competency:** [name]
**Likely question:** [question]
**Story used:** [one-line label]
**STAR answer:** [Situation / Task / Action / Result, clearly broken out]
**Overlaps with:** [other competencies this same story could answer, if any]
End with a "Story Inventory" section listing each distinct story once and every competency it covers, so I know the minimum set I actually need to have ready.نتیجه
**Competency:** Leading Through Ambiguity **Likely question:** "Tell me about a time you had to make a significant decision without complete information." **Story used:** Q3 vendor migration **STAR answer:** Situation: Six weeks before a major product launch, our primary data-processing vendor announced a pricing change that would have tripled our monthly costs, with only 30 days' notice before the new terms took effect. Task: As the PM owning the launch timeline, I had to decide whether to absorb the cost, delay the launch to migrate vendors, or find a third option — without knowing how disruptive a mid-cycle migration would actually be to engineering. Action: I ran a 48-hour spike with two engineers to test whether our data layer could be abstracted enough to swap vendors without a full rebuild. In parallel, I negotiated a 60-day extension from the vendor by reframing the conversation around our contract renewal value rather than the price increase itself. When the spike confirmed a clean swap was feasible, I made the call to migrate instead of delaying the launch. Result: We launched on schedule, cut vendor costs by 40% against the new pricing, and the abstraction layer we built became the standard pattern the team used for its next two vendor evaluations. **Overlaps with:** Cross-functional Influence, Negotiation
**Competency:** Cross-functional Influence **Likely question:** "Describe a time you had to get buy-in from a team you didn't manage." **Story used:** Q3 vendor migration (same story — the engineering buy-in and vendor negotiation threads) **Overlaps with:** Leading Through Ambiguity
بیشتر تمریناتِ مصاحبه نه به خاطر کمبودِ محتوا، بلکه به خاطر مشکلِ بازیابی شکست می‌خورن. داوطلب‌ها تجربه‌ی درست رو دارن؛ فقط نمی‌تونن توی اون دو ثانیه‌ای که بین شنیدنِ سوال و دادنِ جواب هست، به‌طورِ مطمئن داستانِ درست رو از حافظه بکشن بیرون. تا سوالِ سوم، راحت‌ترین کار اینه که همون داستانی رو تعریف کنن که دفعه‌ی پیش جواب داد — چه به سوال بخوره چه نخوره.
چرا بخشِ Role هر دو طرفِ میز رو مشخص می‌کنه
بخشِ Role یه مربی رو تعریف می‌کنه که هم خودش مصاحبه گرفته هم داوطلب‌ها رو آماده کرده، چون مهارتِ موردنیاز فقط داستان‌گویی نیست — بلکه اینه که بتونی پیش‌بینی کنی مصاحبه‌گر پشتِ یه سوالِ کلیشه‌ای دنبالِ چی می‌گرده. «یه موقعیت بگو که توش تیم رو از میانِ ابهام هدایت کردی» و «یه موقعیت بگو که مجبور شدی بدون اطلاعاتِ کامل تصمیم بگیری» اغلب همون شایستگیِ زیربنایی رو می‌سنجن، حتی اگه فرق داشته باشن — و مربی‌ای که روی صندلیِ استخدام‌کننده نشسته، این تداخل رو فوری می‌بینه.
بخشِ Task چه چیزی رو اجباری می‌کنه
مرحله‌ی ۱ صریحاً شایستگی‌ها رو به زبانِ آگهیِ شغلی گره می‌زنه، نه به یه لیستِ کلی — چون آگهی‌ای که «محیطِ پرتغییر» و «بین‌وظیفه‌ای» رو تکرار می‌کنه، داره تقریباً دقیقاً بهت می‌گه چی رو می‌سنجه. دستورِ مرحله‌ی ۳ برای پیدا کردنِ تداخل‌ها، هسته‌ی ساختاریِ کلِ Prompt هست: بیشتر داوطلب‌ها فکر می‌کنن برای هشت شایستگی باید هشت داستانِ جداگانه داشته باشن، در حالی که دو سه داستانِ درست‌انتخاب معمولاً همه‌شون رو پوشش می‌ده — اگه سوال رو درست بپرسی.
محدودیتی که کار اصلی رو انجام می‌ده
قانونِ «واقعیت اختراع نکن» به همراهِ پرچمِ صریحِ [NEED DETAIL] وجود داره چون وقتی از یه مدل بخوای جوابِ STAR شیکی بنویسه، اگه بذاریش، جاهای خالی رو آروم با جزئیاتِ قانع‌کننده‌ای تکمیل می‌کنه که خودت اصلاً نگفتی — و این توی مصاحبه خطرناکه، چون یه سوالِ پیگیری می‌تونه یه عددی رو لو بده که نمی‌تونی پشتش وایسی. علامت‌گذاری روی جاهای خالی به جای ماستمالی کردن‌شون، دقیقاً بهت می‌گه کدوم بخش‌های سابقه‌ات هنوز به یه مثالِ واقعی نیاز دارن — قبل از مصاحبه، نه بعدش.
چرا فهرستِ داستان‌ها وجود داره
بخشِ Story Inventory در انتها، همون چیزیه که توصیه‌های کلیشه‌ای آماده‌سازیِ STAR نادیده‌ش می‌گیرن. این بخش یه لیست از جواب‌ها رو به یه لیستِ کوتاه از داستان‌هایی تبدیل می‌کنه که واقعاً باید حفظ بشن — و این تنها چیزیه که یه داوطلب می‌تونه واقع‌بینانه توی سرش نگه داره وقتی داره وارد اتاق می‌شه. اگه این فهرست یه خلأ نشون بده — یه شایستگی که هیچ داستانی پوشش‌ش نمی‌ده — این مفیدترین چیزیه که این Prompt می‌تونه سه روز قبل از مصاحبه بهت بگه: دقیقاً باید دنبالِ چه مثالی بگردی، به جای اینکه امیدوار باشی اون سوال مطرح نشه.