Common questions and recruiter screens
These questions establish a coherent professional story, mutual interest, and candidate decision-making. Use the evaluation method; numeric anchors are our proposals. Suggested answer shapes are adaptable, not scripts. Routine availability, location, travel, and authorization are profile/checklist inputs, not preparation cards. C08 is retired; stable IDs are not recycled.
C01 — Tell me about yourself
Variants: Walk me through your background. What should I know about you?
Intent: Understand the candidate's relevant experience and direction quickly.
Strong answer target: Start with the work you do now and the problems you are good at solving. Select one or two relevant experiences, explain your actual contribution, and connect them to the next role. A roughly one-to-two-minute version is useful for rehearsal, not a scoring requirement. Avoid narrating every job or listing unsupported adjectives.
Profile inputs/adaptation: Current role, two evidence-backed episodes, target responsibilities, and user-stated direction. IC: technical contribution and collaboration. EM: team delivery and people development. Executive: business problem, organizational responsibility, and peer partnership. Do not merely replace the title while reusing the same claims.
Acceptable alternatives: A career changer can lead with the connecting capability and acknowledge the transition. A nonlinear career need not be apologized for. Personal context is optional.
Probes: Which part was your responsibility? Why is this the right next step?
Failure modes: Resume recitation, inflated scope, generic “results-driven” branding, or an impressive example unrelated to this role.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Relevance | Listener cannot identify a connection to the role | Selects experience that explains the proposed contribution |
| Credible ownership | Attributes broad results to self without a contribution | Distinguishes personal work from the team's accomplishment |
| Coherent direction | No understandable reason for this next move | Connects experience, interests, and target responsibilities |
Provenance: Editorial synthesis; R01 supplies screening context, not this introduction formula. Worked versions: examples.
C02 — Why this role and this company?
Variants: Why us? Why this position now?
Intent: Establish informed motivation and mutual fit.
Strong answer target: Name a concrete feature of the role or company, explain why it matters to you, and connect a relevant capability to that need. Separate public facts from hypotheses you want to test. For an executive, explain why the business challenge and responsibility appeal, beyond the title. For any role, financial stability and work arrangements can be legitimate motivations too.
Profile inputs/adaptation: Target job description, dated company research, user priorities, and a relevant episode. A first-time leader can explain both the interest and what they need to learn; do not invent management success.
Acceptable alternatives: Early in a recruiter conversation, state what is promising and what remains unknown. Joining for a specific mission, domain, technical challenge, or working arrangement can all be defensible.
Probes: What would you need to learn before accepting? Which experience would help with the problem you described?
Failure modes: Praise copied from marketing, invented insider knowledge, or treating prestige as evidence of understanding the role.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Specific interest | Could apply unchanged to any employer | Identifies a concrete attraction and why it matters |
| Contribution | Offers only desire or status seeking | Connects actual capability to a plausible role need |
| Calibrated knowledge | Presents guesses as known company problems | Distinguishes facts, hypotheses, and useful questions |
Provenance: Direct executive interview-preparation context in L05; extension to other roles and anchors are editorial.
C03 — Why are you leaving, or why did you leave?
Variants: Why are you searching? What happened at your last company?
Intent: Understand the transition and whether the new opportunity addresses the candidate's needs.
Strong answer target: Give an accurate, bounded explanation and describe what you want next. Distinguish a layoff, a voluntary change, and a performance termination when the user chooses to discuss those facts. For a difficult exit, acknowledge your contribution where relevant and avoid speculative accusations. There is no obligation to make a negative experience sound positive.
Profile inputs/adaptation: User-confirmed departure facts, disclosure boundaries, and next-role priorities. Managers and executives should avoid disclosing employee or business confidences. A move between IC and management tracks can be an intentional professional choice.
Acceptable alternatives: A short factual explanation can be sufficient. Compensation, relocation, caregiving, health, scope, values, or stability can be legitimate reasons. Private details need not be offered.
Probes: What are you looking for that was missing? What have you learned about selecting the next environment?
Failure modes: Fabricated exit story, extended blame without useful context, or a reason that contradicts the stated target without explanation.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Comprehensibility | Transition remains unintelligible after clarification | Gives enough chosen context to explain the move |
| Professional boundaries | Explanation substitutes accusations or unnecessary private details for context | Gives a bounded explanation and distinguishes facts from interpretations |
| Forward direction | Cannot connect the search to a next-role preference | Explains what the next role should make possible |
Provenance: Editorial synthesis; J01 informs the legitimacy of track changes. No author-prescribed exit script.
C04 — What is a strength you would bring here?
Variants: What are you particularly good at? Why should we hire you?
Intent: Understand a relevant capability and the evidence supporting it.
Strong answer target: Name a specific capability, show it in one episode, and explain how it would help in this role. Describe the mechanism: what you noticed, decided, or did differently. Define a useful boundary rather than claiming the strength works in every situation.
Profile inputs/adaptation: Accepted capability evidence and role need. IC: technical diagnosis, execution, or collaboration. EM: team practices or people development. Executive: judgment or systems with an actual business connection. Match the strongest truthful example, not the most prestigious employer.
Acceptable alternatives: A quieter strength such as dependable follow-through or clear written reasoning can be valuable. No heroic or numerical result is required if the effect is concrete.
Probes: When has this strength been less useful? What would a collaborator say you contributed?
Failure modes: Unsupported superlatives, a skill unrelated to the role, or crediting a team outcome without showing personal contribution.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Relevant capability | Only vague positive adjectives | Names a capability that matters for this role |
| Demonstration | No example or action after a probe | Shows the capability through a concrete contribution |
| Self-knowledge | Claims unlimited competence | Explains useful conditions or a meaningful limit |
Provenance: Practice extrapolation from R02, which is reflection guidance rather than a grading instrument.
C05 — What are you working to improve?
Variants: What is a weakness? What development feedback have you received?
Intent: Understand self-awareness and active development.
Strong answer target: Name a real, work-relevant pattern, explain its effect, and show what you have changed. Describe how you check progress and what remains difficult. “I care too much” without a real cost or behavioral change is weak. Do not invent a strategically harmless weakness or demand private disclosure.
Profile inputs/adaptation: User-selected growth area, episode, received feedback, and actual experiment. IC: e.g. surfacing risk earlier. EM: e.g. delegating decisions. Executive: e.g. inviting dissent before committing. These are possibilities, never inferred weaknesses in the user's profile.
Acceptable alternatives: A capability the candidate has not yet learned can be discussed honestly, with a credible plan. Progress can be qualitative; claiming to have eliminated the weakness is unnecessary.
Probes: What would someone observe you doing differently? Where is the change still unreliable?
Failure modes: Disguised compliment, scripted confession without action, or asserting that an improvement worked without any observation.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Real development need | Supplies only a flattering label | Names a meaningful behavior or knowledge gap and its effect |
| Action | Intends to “try harder” without a change | Describes a specific practiced change or learning plan |
| Progress awareness | Declares success without an observation | Identifies progress evidence and remaining uncertainty |
Provenance: Practice extrapolation from R02. Lopp does not supply a right answer or score.
C06 — Help me understand this career transition or gap
Variants: Why did you change fields? Why the shorter tenure? What connects these different roles?
Intent: Understand relevant continuity and current direction, without turning private life into an assessment.
Strong answer target: Provide the professional context you choose to share, identify transferable experience, and explain what you want now. Clarify dates only when needed. For a new field, distinguish demonstrated abilities from domain skills still to develop. A gap does not need a productivity story.
Profile inputs/adaptation: Confirmed chronology, disclosure preference, transferable episodes, and current readiness/logistics as the user states them. No inference about medical history, motivation, or capability from a gap alone.
Acceptable alternatives: “I took personal time and am now looking for X” can provide enough context. Repeated short roles may reflect contracting or company changes. Do not presume a career problem that needs defending.
Probes: Which experience transfers most directly? Which part of this role would be new to you?
Failure modes: Invented chronology or credentials, or claiming experience in the target domain merely because a previous role was adjacent.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Professional continuity | Relevant timeline or transition is still unclear | Explains the connection with as much context as needed |
| Transfer boundary | Equates adjacent exposure with expertise | Identifies transferable skills and what is still new |
| Current direction | Cannot explain what is sought now | Connects next-role goals to current interests and experience |
Provenance: Editorial synthesis; J01 is a limited reference for track changes. Privacy and gap criteria are ours.
C07 — What are your compensation expectations?
Variants: What range are you considering? What are you making now? We need your number before we can continue. What matters in the package?
Intent: Clarify practical alignment; this is not a competency question.
Strong answer target: First seek the employer's budgeted range for this role and level before volunteering your own number. Ask firmly and professionally; if they redirect, repeat the request with its purpose: establishing whether the scope and package can fit before anchoring expectations. Clarify base, variable pay, equity, currency, location basis, and level as relevant. A vague “competitive” answer is not a range; a very broad band needs clarification about this hire. Do not reveal your private minimum or salary history by default. If disclosure is refused, make the next step explicit: defer numbers, continue by choice, give a deliberately chosen position, or stop. Persist in seeking the range, while leaving that final tradeoff with the candidate. A disclosed band is information to assess, not an instruction to accept its lower end. Do not invent market ranges, competing offers, or the user's willingness to walk away.
Profile inputs/adaptation: User-confirmed expectations, location, currency, package structure, and boundaries. Executive or startup packages may need more components clarified; no assumed preference for equity over cash.
Acceptable alternatives: If a usable employer range is already disclosed, clarify its meaning instead of mechanically asking again. A candidate may choose to state a researched target or a genuine hard boundary; this is an explicit departure from the range-first default. Do not grade their need to keep a process moving or their ultimate compensation preference.
Probes: They say “it depends on the candidate”; what do you ask next? Is this the range for this level and location, and is it base or total? What will you do if they continue to refuse? How would you respond to a band below your own requirements without revealing your minimum unnecessarily?
Failure modes: Volunteering a low anchor before seeking their range; revealing salary history or a private minimum unnecessarily; accepting a vague band as useful information; ambiguous package units; bluffing about offers or walk-away intent; or treating repeated deflection as a reason to bargain against yourself.
| Coaching dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Information and anchoring | Volunteers an unconsidered number without seeking available employer information | Firmly seeks a useful employer range first, or explains a deliberate candidate-chosen exception |
| Package meaning | Treats an ambiguous band or component as understood | Clarifies applicable level, currency, period, base/total, and material components |
| Response to pressure | Repeats deflection without a plan or invents leverage | Protects boundaries, persists professionally, and chooses a truthful next step if disclosure is refused |
Provenance: Applicant-side negotiation synthesis, following the requested range-first policy. N01 argues against naming a number first; our range questions, pressure handling, and rubric are editorial. This is not a Larson/Lopp leadership rule, a guarantee of negotiation success, or advice to adopt N01's market assumptions or artificial form-entry numbers. Assess preparation choices and clarity, never salary level, private constraints, or the person's willingness to risk an opportunity.
C09 — What do you want in your next role?
Variants: Where do you want to grow? What environment helps you do your best work? Do you want to manage people?
Intent: Understand direction and mutual expectations.
Strong answer target: Describe work you want to own, conditions that help, and skills you want to develop. Distinguish non-negotiables from preferences. If considering management, explain the work that attracts you and what you understand about it. Staying an IC is a complete professional direction.
Profile inputs/adaptation: User goals, examples of effective/ineffective environments, preferred track, and constraints. For directors/executives, include the kind of organizational or business problem sought; for ICs, include technical scope and collaboration. Do not infer a target from current title.
Acceptable alternatives: Stability, flexible arrangements, a domain change, deeper expertise, or a deliberate step down in scope can be sensible priorities. It is acceptable to be exploring a choice and identify what would resolve it.
Probes: Which preference matters most? What would make a role unsuitable?
Failure modes: A title-only ambition, invented career goals, or claiming compatibility while describing incompatible responsibilities.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Work sought | Gives a title without an understandable direction | Describes desired responsibilities or development |
| Informed preference | Cannot explain the preference's basis | Connects it to experience or a considered exploration |
| Mutual fit | Ignores a material mismatch after it is raised | Names priorities, unknowns, and meaningful constraints |
Provenance: Editorial synthesis informed by R02 and J01.
C10 — What questions do you have for us?
Variants: What would help you decide? What have we not covered?
Intent: Help the candidate learn whether the opportunity fits and clarify expectations. This is not an enthusiasm test.
Strong answer target: Choose questions whose answers change your decision or preparation: success expectations, current challenges, decision authority, support, team health, or the remaining loop. Adapt them to the interviewer's knowledge and information already shared. Ask for concrete examples where useful. Two thoughtful questions can be enough; length and quantity add no merit.
Profile inputs/adaptation: User priorities, unresolved role questions, company research, and conversation notes. IC: technical direction and adoption. EM: support and authority over delivery/people. Executive: mandate, peer expectations, resources, and business constraints.
Acceptable alternatives: If questions were already answered, say what you learned and what you will follow up on. Running out of time is not_observed, not evidence of disinterest. Practical questions are legitimate.
Probes: What would a good or concerning answer tell you? Who could answer this if this interviewer cannot?
Failure modes: Performative trivia, adversarial gotchas without a decision purpose, or repeating a question without acknowledging its earlier answer.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Decision value | Cannot explain why the question matters | Seeks information that affects fit or preparation |
| Context | Ignores available information or interviewer scope | Uses the discussion and asks an appropriate person |
| Useful specificity | Gets only slogans and has no relevant follow-up | Invites concrete examples or clarifies a material uncertainty |
Provenance: Direct screening theme in R01 and staff preparation in L06; evaluation limits are ours.