THE THINKING BEHIND INTERVIEW COMPASS

Overall approach

Make the work happen. Then understand what made it work.

The site serves three perspectives: candidates, interviewers, and managers. Candidates are the primary audience: use the library to prepare for interviews, promotion conversations, and defenses with evidence from your own work. Interviewers and managers can use the same framework to make and support decisions.

Why this site exists

A polished story or a successful launch is not enough to judge the work. The same result can come from different decisions, team contributions, constraints, and luck. A useful conversation reconstructs the path from the goal to the outcome and makes the evidence inspectable.

That is why the library is organized around questions, evidence, and follow-ups rather than model answers. The questions help people explain their own work and help interviewers test what they need to know without pretending every person or context is identical.

From a real goal to an outcome

The sequence below is a reasoning path, not a script. In practice, teams revisit earlier steps as facts change.

  1. 01

    Start with the goal and the facts

    Who needs what, what is happening now, and which constraints, baselines, or dependencies matter?

  2. 02

    Find the real problem and define the bar

    Separate symptoms from causes. Define what success means, how it will be measured, what benchmark matters, and what would count as enough.

  3. 03

    Compare choices, including stopping

    Make feasible paths visible. Compare value, quality, cost, risk, reversibility, and opportunity cost; explain what not to do and why.

  4. 04

    Set up people, roles, authority, and resources

    Match the work to the right capabilities and decision rights. Make capacity, dependencies, and the support needed from other teams or leaders explicit.

  5. 05

    Coordinate execution and adapt

    Set priorities and a working cadence. Share decision-relevant information, handle conflict, escalate when needed, and intervene at the right level.

  6. 06

    Verify outcomes and contribution

    Compare with the baseline and agreed bar. Separate team outcomes from personal contribution, check other causes, and name costs or side effects.

  7. 07

    Learn, recover, and choose what comes next

    Review missed assumptions and setbacks, show what changed in later work, and check whether the role, organization, and personal goals can keep fitting.

Eight lenses on the work

The domains are different lenses on the same work, not eight boxes a person must check. A project may require several at once; role scope changes what evidence is appropriate.

ATechnical craft
Can the person reason from fundamentals, design and implement a sound solution, and meet an appropriate quality bar?
BBusiness and domain understanding
Can they model users, workflows, rules, and the context that gives the work meaning?
CValue and direction
Can they identify what matters, set priorities, compare with alternatives or competitors, and stop low-value work?
DDelivery and operations
Can they turn intent into milestones, manage capacity and dependencies, and close the loop on execution?
ECollaboration and influence
Can they make information actionable, resolve differences about facts or goals, and secure commitments across boundaries?
FPeople and organization
Can they shape teams and roles around business goals, hire, assign, coach, retain, and build a system that does not depend on constant heroics?
GLearning and adaptation
Can they learn across domains, recover from setbacks, use feedback, and show a change in later decisions?
HProfessional responsibility
Can they own their part, represent evidence honestly, manage emotion professionally, respect boundaries, and assess mutual fit?

PERSPECTIVE 1 · CANDIDATE

Use the site to prepare your evidence, not memorize answers

Most people who arrive here are preparing to be a candidate. Start from the role and decision you care about, then use the questions to find and explain evidence from work you have actually done. The library is a map for preparation, not a checklist you need to finish.

  1. Choose a target.Pick the role, responsibility scope, and context: an external interview, promotion review, or project/technical defense. A title alone does not tell you what evidence the decision requires.
  2. Translate the target into work.What outcomes does the role own? Which technical fundamentals, business understanding, collaboration, or leadership decisions matter? Use the role and capability pages to identify the expected scope.
  3. Choose real examples.For each example, explain the business or user need, challenge, your responsibility, the result, and your part in producing it. Compare the alternatives, pros and cons, cost, benchmark or competitor, and what you deliberately did not do. Use the same discipline for technical choices: fundamentals, quality bar, failure modes, and trade-offs.
  4. Check what the result proves.Separate team outcome from your contribution. State the evidence, its limits, side effects, and other possible causes. A failed or delayed project can still show sound judgment if you explain what changed in your later work.
  5. Practice the conversation and assess fit.Use questions to find gaps, then practice answering follow-ups in your own words. Ask the interviewer about real responsibilities, standards, support, and constraints; compare those answers with what you need and what the organization can sustain.

The goal is not to sound flawless. It is to help the other person understand your decisions and evidence, notice what you still need to learn, and decide whether the role fits both sides.

Follow the preparation guidePractice candidate questionsReview technical questionsPrepare questions for the employer

Operating systemsComputer networksDatabases

PERSPECTIVE 2 · INTERVIEWER

Design questions around the decision you need to make

Start with the role’s outcomes and responsibility scope. Decide which evidence would change your assessment, then use questions and follow-ups to gather it. Keep the criteria comparable while allowing candidates to show different paths; separate observed facts from interpretation, and do not turn one answer into a verdict on someone’s character.

Read the interviewing methodBrowse interviewer questions

PERSPECTIVE 3 · MANAGER

Design the conditions for results

Management is more than assigning tasks and checking status. Start from the business goal, then decide which capabilities and roles are needed, how responsibilities should be divided, and where teams need clear interfaces. A useful structure reduces unowned work and unnecessary overlap while giving people room to own outcomes.

  • Resources and upward support:Summarize the goal, evidence, key risk, and decision needed. Make capacity, dependencies, trade-offs, and the cost of delay concrete; ask for the sponsorship or top-down decision that can unblock the work.
  • Operating mechanisms:Choose meeting, reporting, and information-sharing rhythms that help the right people decide. Make priorities visible, handle cross-team conflict, and manage work across levels without pulling every decision upward.
  • Hiring and using people:Define the role before selecting a person. Match difficult work with capability, motivation, support, and authority; agree what good looks like and when a manager should coach, intervene, or step back.
  • Retaining and developing people:Notice high performance and potential through sustained evidence. Choose development paths for different strengths, provide meaningful scope and resources, coach against observable gaps, and handle improvement plans or role transitions fairly, consistently, and through the organization’s established process.

People, judgment, and fit

Questions about humility, ego, maturity, resilience, or professionalism should not become personality labels. Look at behavior over time: how someone responds to disagreement, updates a view when evidence changes, credits others, owns mistakes, regulates emotion, and treats commitments.

Confidence or a strong ego is not automatically a problem; the question is whether capability is real and whether the person can learn, collaborate, and keep the impact of that style within healthy bounds. Fit is also mutual: compare what the person needs, what the organization can offer, and whether that match can last as the work changes.

Setbacks belong in the same evidence-based view. A failed project does not settle the question by itself; examine the decisions, constraints, response, recovery, and whether learning changed later behavior.

Understand each participant’s purpose, then find your position

An interview, promotion review, or project defense is a decision process. The people in the room may share a broad goal, but they do not all own the same question. Before choosing what to explain, work out what decision is being made, who will make or shape it, and what evidence each person needs.

Candidate in an interview
The interviewer is testing evidence against the role; the hiring manager is also weighing the team’s needs, risks, and working context. Show how your decisions and contribution fit the work, and use your questions to assess the role and support available.
Promotion candidate
Reviewers are looking for sustained responsibility at the next scope, not one unusually successful project. Connect repeated decisions and attributable outcomes to the expectations of that scope; clarify what remains outside your ownership.
Project or technical defense
Reviewers need to judge whether the problem was worth solving, whether the choices were sound, what the result proves, and what decision or support is needed now. Make the baseline, alternatives, cost, risks, ownership, and open questions easy to inspect.
Manager or senior sponsor
They need a concise view of progress, risk, dependencies, and the choice in front of them. State the impact of waiting, what your team can do, and the specific resource, decision, or sponsorship that would change the outcome.

A practical way to respond

  1. Name the decision and its criteria. If they are unclear, ask what the group needs to decide and by when.
  2. Read the participants’ responsibilities and incentives without assuming hidden motives. Separate the decision owner, evidence gatherers, affected partners, and people who can unblock resources.
  3. Choose evidence that answers their question. Explain your own role, trade-offs, results, and limits; do not claim work owned by the team.
  4. Surface conflicts or missing support early. State the trade-off, ask for the needed clarification or decision, and confirm the next step.

Reading purpose is not performing for an audience. It helps you put the right evidence in front of the people responsible for a decision, while also checking whether their expectations and the organization’s offer fit your own goals.

Start from your role

The library is a growing reference, not an exhaustive encyclopedia or an automatic verdict on a person. Follow the preparation guide if you are a candidate; use the interviewing method to structure an assessment; use the management questions to examine how a team creates the conditions for sustained results.

Candidate: prepare for a roleInterviewer: plan the conversationManager: assess and lead a team