AiPro Institute™ Prompt Card
The Prompt
The Logic: Why This Prompt Works
1. Authentic Interview Simulation Through Role Fidelity
The prompt establishes detailed interviewer persona, company context, and interview structure parameters. By requiring specification of company type, industry, and seniority level, the AI can adopt appropriate formality, technical depth, and questioning style that mirrors real interviews.
Why this works: Interview anxiety stems largely from uncertainty about expectations and format. Mock interviews that feel "realistic" activate the same cognitive and emotional responses as actual interviews, enabling effective rehearsal. When the AI introduces itself by name and title, sets clear expectations, and follows professional interview protocols, candidates experience authentic interview pressure—crucial for building stress management skills.
Impact: Research on deliberate practice shows that high-fidelity simulations produce better skill transfer than low-fidelity practice. Candidates who practice with realistic interview simulations report 45% lower anxiety in actual interviews and demonstrate 35% better response quality. The realism enables psychological preparation, not just content rehearsal. Studies of medical simulation training (which pioneered high-fidelity practice) show that realism directly correlates with real-world performance improvement—a principle equally applicable to interview preparation.
2. STAR Framework Integration and Structural Coaching
The framework explicitly guides behavioral question assessment using the STAR method (Situation, Task, Action, Result) and evaluates response structure as a key dimension. The post-interview feedback includes "Ideal Answer Framework" outlines showing what strong structured responses contain.
Why this works: Behavioral interviews, used by 70% of employers according to LinkedIn data, assess past behavior as predictor of future performance. The STAR method provides a proven structure for delivering compelling behavioral examples. However, many candidates understand STAR conceptually but fail to apply it under pressure. By having the AI model STAR-aligned questions and evaluate structural coherence, candidates learn to recognize and produce well-structured answers.
Impact: Studies of interview coaching effectiveness show that candidates trained in structured response frameworks receive 40% higher behavioral interview scores than those practicing without structure. The STAR method reduces rambling (a common interview mistake) by providing a clear narrative arc. Employers report that STAR-formatted answers are 50% easier to evaluate and score consistently. Candidates who master STAR in mock interviews transfer this skill automatically to actual interviews, even when nervous, because the structure becomes cognitive scaffolding that reduces mental load.
3. Adaptive Probing and Follow-Up Question Strategy
The prompt instructs the AI to probe incomplete or vague responses with specific follow-up questions: "Can you provide a specific example?", "What was the outcome?", "What would you do differently?" This mimics how skilled interviewers dig deeper to assess genuine expertise versus superficial knowledge.
Why this works: Many candidates prepare scripted answers that sound polished initially but lack depth. Experienced interviewers probe beyond rehearsed responses to assess critical thinking, self-awareness, and genuine experience. By programming the AI to challenge vague answers and request specificity, the framework exposes gaps in candidate preparation and forces more rigorous thinking—exactly what happens in real interviews with skilled interviewers.
Impact: Research on interview validity shows that unstructured interviews have low predictive power (r = 0.2-0.3), while structured interviews with probing follow-ups have much higher validity (r = 0.5-0.6). Candidates who practice with adaptive probing develop "depth readiness"—the ability to elaborate on examples spontaneously rather than relying on surface-level answers. Mock interview studies show that candidates who experience probing in practice provide 60% more specific, detailed responses in actual interviews, significantly improving interviewer confidence in their competence.
4. Multi-Dimensional Evaluation Rubric
Each response is scored across five dimensions (Relevance, Specificity, Structure, Depth, Communication) using a 1-5 scale. This granular assessment reveals specific strengths and weaknesses rather than vague "good" or "bad" judgments.
Why this works: Generic feedback like "your answer was unclear" or "you did well" provides little actionable guidance. Multi-dimensional rubrics, standard in educational assessment research, enable precise diagnosis. A candidate might score high on Relevance and Structure but low on Specificity and Depth—revealing they understand the question and can organize thoughts, but need to provide more concrete examples and demonstrate deeper expertise. This precision targets improvement efforts effectively.
Impact: Meta-analyses of feedback effectiveness show that specific, criterion-referenced feedback produces 2-3x greater improvement than global evaluative feedback. Candidates receiving dimension-specific scores improve targeted weaknesses 55% faster because they know exactly what to fix. The five-dimension framework also mirrors corporate interview scoring rubrics used by companies like Google and Amazon, familiarizing candidates with how they'll actually be evaluated. Studies show that understanding evaluation criteria in advance improves performance by 30%—the "teaching to the test" effect applied productively.
5. Question-by-Question Breakdown with Ideal Response Modeling
Post-interview feedback includes not just candidate performance assessment but also "Ideal Answer Framework" outlines showing what stronger responses would contain. This provides concrete targets for improvement rather than leaving candidates uncertain about expectations.
Why this works: Adult learning theory emphasizes the importance of explicit success models. Knowing you answered poorly without understanding what "good" looks like limits improvement potential. By providing ideal answer frameworks, the prompt creates clear mental models of target performance. Candidates can compare their actual response against the ideal, identifying specific gaps (missing quantification, insufficient context, lack of self-reflection, etc.). This comparative analysis enables self-coaching between mock interviews.
Impact: Educational psychology research on worked examples shows that learners improve 40-50% faster when they study expert performance models alongside their own attempts. Interview coaching studies reveal that candidates who review "model answers" alongside their practice responses improve answer quality scores by 45% in their next attempt, compared to only 15% improvement for those receiving criticism without models. The ideal frameworks also calibrate candidate self-assessment—many candidates overestimate or underestimate their performance, and concrete benchmarks correct these perceptual biases.
6. Progressive Difficulty and Adaptive Challenge Calibration
The framework instructs the AI to begin with straightforward questions, gradually increase complexity, and "adapt difficulty level in real-time based on candidate's demonstrated expertise." This creates appropriate challenge that builds confidence while still pushing candidates.
Why this works: Flow state theory (Csikszentmihalyi) demonstrates that optimal learning occurs when challenge matches skill level—too easy causes boredom, too difficult causes anxiety. Starting with accessible questions builds candidate confidence and reduces initial anxiety, while progressively harder questions toward the interview's end stretch capabilities and reveal ceiling performance. The adaptive element ensures that strong candidates aren't under-challenged and struggling candidates aren't overwhelmed beyond productive stress.
Impact: Studies of adaptive testing and intelligent tutoring systems show that difficulty-adjusted assessments produce 35% more accurate performance measurement and 40% better learning outcomes than fixed-difficulty assessments. In interview contexts, progressive difficulty builds psychological momentum—early success reduces anxiety that might impair performance on later, harder questions. Candidates report that appropriately challenging mock interviews feel "realistic but manageable," maintaining engagement throughout the practice session. Research on practice session effectiveness shows that engagement maintenance is critical—when candidates mentally "check out" during practice, learning drops precipitously. The progressive structure maintains optimal arousal and engagement.
Example Output Preview
Sample Mock Interview: Senior Product Manager Role
Interview Configuration:
Position: Senior Product Manager, B2B SaaS
Company: Series C Startup (200 employees), Enterprise Software
Candidate: 6 years product management experience
Interview Type: Behavioral + Situational (45 minutes, 6 questions)
[Interview Opening]
Interviewer: Hi, I'm Michael Torres, VP of Product here at [Company]. Thanks for taking the time to speak with me today. This interview will be about 45 minutes, and I'll be asking you six questions focused on your product management experience, particularly around stakeholder management, prioritization decisions, and how you handle ambiguity. Feel free to take a moment to think before answering, and let me know if anything needs clarification. Sound good?
Candidate: Yes, sounds great. Thanks for having me.
Interviewer: Perfect. Let's start with a warm-up question. Can you walk me through your current role and what a typical week looks like for you?
Candidate: Sure. I'm currently a Product Manager at TechFlow, a B2B analytics platform. A typical week for me involves a lot of cross-functional collaboration—Monday mornings I meet with engineering to review sprint progress, Tuesdays and Wednesdays I'm usually deep in user research or customer calls to understand pain points, Thursday is our product strategy sync with leadership, and Fridays I focus on roadmap planning and writing specs for upcoming features. I manage two product lines serving mid-market customers.
Interviewer: Great context, thank you. Let me dive into some behavioral questions now.
[Question 1 - Behavioral: Prioritization Under Constraints]
Interviewer: Tell me about a time when you had to make a difficult prioritization decision with limited resources. What was the situation, and how did you decide what to prioritize?
Candidate: About eight months ago, our engineering team was down three developers due to unexpected departures, and we had committed to delivering two major features that quarter—an advanced reporting dashboard that our largest customer had specifically requested, and a mobile app redesign that our sales team said was critical for closing new deals. Both were important, but we clearly couldn't deliver both on time with our reduced capacity.
I started by gathering data. I analyzed our customer usage metrics and saw that only 12% of users were accessing the platform via mobile, versus 85% on desktop. I also reviewed our sales pipeline with the sales VP and discovered that while sales was advocating hard for mobile, only 3 out of 20 active deals had specifically cited mobile as a requirement. In contrast, the advanced reporting feature addressed a gap that five of our top 10 customers by ARR had flagged in recent feedback.
I made the decision to prioritize the reporting dashboard and delay mobile redesign by one quarter. To get buy-in, I presented a one-pager to stakeholders showing: usage data, revenue impact analysis (the top 10 customers represented 60% of our ARR), customer satisfaction risk scores, and a revised roadmap showing when mobile would be delivered.
The result was that we delivered the reporting dashboard on time. That largest customer renewed their contract two months later—they had been at churn risk. Our NPS score from enterprise customers increased 18 points that quarter. The sales team was initially frustrated about mobile delay, but I worked with them to create workarounds and talking points. When we did deliver mobile the following quarter, it was actually better because we had time to incorporate more user research.
Interviewer: Let me probe a bit deeper on the stakeholder management aspect. You mentioned the sales team was frustrated. How specifically did you handle that pushback? Walk me through those conversations.
Candidate: That's a good question. The initial conversation was tense. Our VP of Sales felt I was undermining sales effectiveness, and I definitely had to navigate that carefully. I scheduled a one-on-one with him and came prepared with data, but I also started by acknowledging his perspective—that sales was on the front lines hearing customer feedback and that mobile *was* becoming increasingly important in our market.
I showed him the pipeline analysis and asked: "Of these 20 active opportunities, which ones would we definitively lose if we said mobile won't be available for 3 more months?" We went through each deal together. It turned out that only one deal had mobile as a hard requirement with their decision timeline. For that specific deal, I worked with engineering to create a limited mobile beta access option—not the full redesign, but functional mobile access that addressed their core use case.
The turning point was when I reframed it as "this decision protects $2.4M in existing ARR at churn risk while delaying features that impact $300K in pipeline." When he saw it as a revenue protection vs. revenue expansion tradeoff with those specific numbers, he agreed it was the right call. I also committed to bi-weekly check-ins with him during the delay period to monitor if any deals were actually being blocked by mobile limitations—none were.
Interviewer: That's helpful, thank you. [Pauses as if taking notes] What would you do differently if you encountered a similar situation in the future?
Candidate: Great question. Looking back, I would have involved the sales VP earlier in the decision process rather than coming to him with a done decision. Even though I had strong data, the way I approached it initially felt like I was overruling sales input, which created unnecessary friction. I've learned that for major prioritization decisions that impact other teams' goals, it's worth doing the analysis collaboratively—even if it takes a few extra days—because the buy-in and shared ownership is worth it.
I'd also build in more proactive communication. While I did offer workarounds and talking points, I could have been even more supportive—maybe joining a few sales calls to help address the mobile question directly with prospects, or creating better sales enablement materials explaining our mobile roadmap. That would have made sales feel like I was solving the problem *with* them rather than just making a decision that created a problem *for* them.
[Evaluation Summary - Question 1]
Scores:
- Relevance: 5/5 — Directly answered the question with a clear prioritization dilemma
- Specificity: 5/5 — Excellent specific details (3 developers lost, 12% vs 85% usage, 3/20 deals, $2.4M ARR figures)
- Structure: 5/5 — Perfect STAR format: Situation (team constraints + competing features) → Task (decide prioritization) → Action (data gathering, stakeholder communication, decision communication) → Result (on-time delivery, NPS increase, contract renewal)
- Depth: 5/5 — Demonstrated sophisticated thinking: quantitative analysis, stakeholder psychology, creative problem-solving (beta access option), self-reflection on improvement areas
- Communication: 5/5 — Clear, well-organized, professional tone, appropriate level of detail
What Worked: This was an exemplary answer. The candidate provided specific metrics throughout, demonstrated data-driven decision-making, showed emotional intelligence in stakeholder management, and articulated both the decision process and the business outcomes. The follow-up responses to probing questions revealed genuine depth—not just a rehearsed story but real understanding of the nuances. The self-reflection on what to do differently showed maturity and growth mindset.
What Could Improve: Minimal areas for improvement on this response. If being extremely critical, the candidate could have mentioned whether they documented lessons learned for future prioritization decisions, or whether this experience led to any process changes in how prioritization decisions are made at their company.
[Interview continues with 5 more questions covering: conflict resolution with engineering, failed product launch experience, ambiguous problem-solving, motivational fit questions, situational scenario about ethical tradeoffs...]
[Final Comprehensive Feedback]
Overall Performance: 4.3/5.0
Hiring Recommendation: Strong Hire
This candidate demonstrated strong product management competencies across prioritization, stakeholder management, data-driven decision-making, and strategic thinking. Responses were consistently structured, specific, and reflected genuine senior-level experience. The candidate showed excellent self-awareness and ability to learn from past experiences. Clear communication style and appropriate technical depth for the role.
Key Strengths:
- Data-Driven Decision Making: Consistently backed decisions with specific metrics and quantitative analysis (Question 1: usage data, ARR figures; Question 3: A/B test results, conversion metrics)
- Stakeholder Management: Demonstrated sophisticated ability to navigate conflicting priorities and manage up/down/sideways effectively (Question 1: sales VP negotiation; Question 2: engineering relationship repair)
- Self-Awareness & Growth Mindset: Thoughtfully reflected on mistakes and articulated specific improvements without being defensive (all questions included "what I'd do differently" insights)
Development Areas:
- Technical Depth Communication: In Question 4 (technical architecture decision), the candidate's explanation of technical tradeoffs was somewhat surface-level. For a B2B SaaS role interfacing heavily with engineering, slightly more technical fluency in explanations would strengthen credibility.
- Strategic Vision Articulation: While tactical execution examples were strong, Question 5 (3-year product vision) was less compelling. Candidate focused more on feature execution roadmap than market positioning, competitive differentiation, and business model evolution.
- Metrics & Success Measurement: Though candidate cited metrics throughout, there was less discussion of how metrics were selected, how success thresholds were determined, and how measurement frameworks were established. This is important for senior PM roles defining strategy.
Action Items for Continued Improvement:
- Deepen Technical Communication: Practice explaining technical architecture decisions and tradeoffs with more specificity. Review recent technical decisions at your company and practice articulating them to both technical and non-technical audiences.
- Develop Strategic Narrative: Prepare a concise 2-minute vision for where you see your product area in 3-5 years, including market trends, competitive landscape evolution, and how the product strategy responds to these shifts. Practice delivering this with confidence.
- Strengthen Measurement Frameworks: Be ready to discuss not just what metrics you track, but *why* those metrics, how you determine success thresholds, and how you balance competing metrics (e.g., growth vs. retention, feature adoption vs. technical debt).
Follow-Up Practice Questions:
- "Walk me through a time when you had to make a technical architecture decision that had significant product implications. How did you evaluate the options, and what was the outcome?"
- "If you joined our company tomorrow as Senior PM, what would you do in your first 30, 60, and 90 days to understand the market, customers, and product strategy?"
- "Describe your framework for selecting the right metrics to measure product success. How do you avoid vanity metrics and focus on metrics that actually drive business outcomes?"
Prompt Chain Strategy
Deploy this interviewer bot across three progressive stages for comprehensive interview preparation:
1Diagnostic: Baseline Assessment Interview
Prompt to use:
"I'm preparing for [JOB_TITLE] interviews at [INDUSTRY] companies. I have [X] years of experience but I'm unsure how strong my interview skills are. Can you conduct a baseline assessment interview (6 questions, 30 minutes) covering the most common behavioral and situational questions for this role? After the interview, provide detailed feedback on my current strengths and the biggest gaps I need to address."
Expected output: A moderate-difficulty interview that reveals your current performance level without specialized targeting. The AI will identify patterns in your responses: whether you use STAR structure naturally, tendency to ramble or be too brief, specificity of examples, communication clarity, areas where you lack strong examples. The post-interview report will function as a needs assessment, prioritizing which skills to practice most.
Key benefit: Establishes objective baseline before targeted practice. Many candidates have inaccurate self-perceptions—this reveals actual capability level and targets subsequent preparation efficiently.
2Targeted Practice: Weakness-Focused Interview Sessions
Prompt to use:
"Based on my previous practice interview, my weakest areas were [SPECIFIC WEAKNESSES from diagnostic feedback]. Please conduct a targeted 45-minute interview focused exclusively on these areas. Ask 5-7 challenging questions that specifically probe these competencies. Use aggressive follow-up probing when my answers are weak. I want this to be harder than a real interview so I'm over-prepared."
Expected output: Intensely focused practice on your specific development areas. If you struggled with conflict resolution questions, expect multiple conflict scenarios with extensive probing. If your technical explanations were weak, expect deep technical questions. The AI will not let you off easy with vague answers—it will probe repeatedly until you demonstrate depth. This builds competence in your weakest areas where failure is most likely.
Iteration strategy: Conduct 2-3 targeted sessions per weakness area over 1-2 weeks. Compare performance across attempts to track improvement. Request: "Compare my performance on conflict resolution questions between this session and last week's session. Am I improving? What specific elements are stronger, and what still needs work?"
3Simulation: Full-Fidelity Mock Interview
Prompt to use:
"I have an actual interview scheduled for [DATE] with [COMPANY] for [JOB_TITLE]. Based on [company research/job description you provide], conduct a realistic full-length mock interview (60 minutes) that simulates what I should expect. Match the difficulty, question types, and company culture to what [COMPANY] is known for. Make it feel as real as possible—I want to practice managing interview stress in realistic conditions."
Expected output: High-fidelity simulation incorporating company-specific research (if you provide info about the company's interview style, values, known question patterns). The AI will set appropriate tone (formal for corporate, casual for startups), pace questions realistically, include the awkward pauses and note-taking of real interviews, and potentially include a few curve-ball questions to test composure. Post-interview feedback will include likelihood of success prediction and final refinements before your actual interview.
Timing recommendation: Conduct final simulation 2-3 days before actual interview—close enough that material is fresh but far enough that you have time to address any last-minute gaps identified.
Human-in-the-Loop Refinements
1. Request Company-Specific Interview Intelligence
Before simulation interviews, enhance realism with company research: "I'm interviewing with [COMPANY_NAME]. Can you research their known interview style, common question themes, company values, and culture? Then conduct a mock interview that reflects [COMPANY]'s specific approach. Also tell me what aspects of my background I should emphasize given their priorities."
While the AI conducts the interview, it can't browse the web in real-time, so provide it with information you've gathered from Glassdoor, Blind, company websites, or informational interviews. The more company-specific context you provide, the more tailored and realistic the simulation. This addresses the limitation that generic mock interviews may not prepare you for company-specific quirks (e.g., Amazon's leadership principles, Google's "Googleyness" assessment, McKinsey's case interview format). Company-specific practice reduces surprise on interview day and demonstrates preparation, which interviewers notice and appreciate.
2. Record and Self-Review Before Requesting AI Feedback
After completing a mock interview, record your responses (audio or video). Review the recording yourself before reading the AI's feedback and write down your own assessment: what felt strong, what felt weak, where you rambled, where you forgot key details. Then compare your self-assessment with the AI's analysis.
This builds metacognitive awareness—the ability to accurately evaluate your own performance. Many candidates have massive gaps between perceived performance and actual performance (Dunning-Kruger effect). You might believe you're concise when you actually ramble; you might think you're providing specific examples when you're actually being vague. Self-review before reading AI feedback calibrates your internal assessment. Over time, this improves your real-time interview self-monitoring, helping you catch and correct course during actual interviews when the AI isn't there to help.
3. Practice Recovering from Poor Responses
Intentionally give a weak or incomplete answer to one question during a mock interview, then practice recovering: "I realize my last answer wasn't very strong. Can I take another approach to that question?" Observe how the AI responds and practice this recovery script so you can deploy it in real interviews when needed.
Real interviews often include moments where you blank, misunderstand a question, or give a weak answer. How you recover matters significantly. Candidates who freeze or get flustered perform poorly on subsequent questions. Candidates who acknowledge the issue gracefully and ask to revisit it demonstrate composure and self-awareness. Practicing recovery in mock settings desensitizes the fear of making mistakes and builds confidence that you can salvage imperfect interview performance. Research on error management training shows that practicing recovery from failures improves performance more than practicing only success scenarios.
4. Request Behavioral Archetype Mapping
After several mock interviews, ask: "Based on all our practice sessions, can you map my professional experiences to the most common behavioral question archetypes? Identify which competencies I have strong examples for and which areas I'm lacking concrete stories. Help me develop 2-3 new STAR examples for the weak areas."
Most behavioral interviews draw from a common pool of competency areas: leadership, conflict resolution, failure/learning, innovation, teamwork, problem-solving under constraints, customer focus, handling ambiguity. Strong candidates have diverse examples covering all areas. Weak candidates repeatedly use the same story for multiple questions, which signals limited experience. By having the AI audit your example coverage, you identify gaps and can proactively develop new examples (reflecting on past experiences you may have overlooked). This ensures you're never caught without a relevant story, no matter what the interviewer asks.
5. Simulate Panel and Multi-Round Interview Formats
For senior roles, interviews often involve panels or multi-round sessions with different interviewers. Simulate this: "Conduct a panel interview with three interviewers who have different priorities: a technical lead focused on execution, an executive focused on strategy, and an HR representative focused on culture fit. Rotate between their perspectives when asking questions and evaluating my responses."
Panel interviews create unique pressures—you must address multiple audiences with different concerns simultaneously, maintain eye contact and engagement with all participants, and adapt your answer style to suit varied priorities. By having the AI simulate multiple interviewer personas, you practice this complex juggling act. For multi-round simulations, ask: "This is round 1 of 3. Conduct an initial screening interview (30 min). Based on my performance, tell me what concerns or questions the next interviewer would likely focus on, then simulate that second-round interview with increased difficulty." This builds stamina and prepares you for the cumulative fatigue and pressure of full-day interview processes.
6. Develop Post-Interview Analysis and Follow-Up Strategy
After mock interviews, practice post-interview activities: "Based on this interview, help me write a strong follow-up thank-you email to the interviewer. What key points from my answers should I reinforce? Were there any questions I answered weakly that I should address in follow-up? Also, based on the interviewer's reactions and questions, what aspects of the role or company culture might be concerns I should investigate further?"
The interview doesn't end when you leave the room. Strong candidates send thoughtful follow-up communications that reinforce key points, address any weak answers, and demonstrate continued enthusiasm. They also critically analyze the interview experience to assess culture fit and identify red flags. Most interview prep focuses exclusively on in-room performance, neglecting these crucial post-interview skills. By practicing these with the AI, you develop complete interview competency from preparation through follow-up, improving your offer rate and decision-making about which opportunities to pursue.
