Job Strategy AIJob StrategyAI

    Scored on the same rubric employers use

    Most prep sites hand you a list of questions. Nobody is marking your answers. Below are real questions, what a weak answer sounds like, what a strong one does differently, and the dimensions your answers are scored on.

    01The rubric

    What is actually being scored

    Interviewers rarely tell you the rubric. These are the dimensions structured hiring assessments measure, and the same ones your mock interview report scores.

    Coachability

    What you do when the interviewer pushes back or shows you a better way.

    Strong answers take the point on board and adjust. Weak answers defend the first answer harder.

    Decision quality under ambiguity

    What happens to your answer when the interviewer changes the constraint halfway through.

    Strong answers absorb the new information and re-reason. Weak answers repeat the original answer louder.

    Emotional signals

    How you talk about tension with a colleague, a customer or a manager.

    Strong answers stay steady and fair to the other person. Weak answers turn into blame or go vague.

    Role-specific judgment

    How you weigh cost, risk and people in the trade-offs this exact job faces.

    Strong answers name the trade-off they accepted and why, in the job's own terms. Weak answers pretend the trade-off did not exist.

    Conscientiousness

    Evidence that you closed the loop, not just started the work.

    Strong answers include what you verified afterwards and what you got wrong. Weak answers end at the launch.

    02Worked examples

    Four questions, and how they are marked

    Read the weak answer first. It is the one most candidates give, and it is not wrong. It is just unscoreable.

    Role-specific judgment

    You are two weeks from a launch date the CEO announced publicly. Your team finds a bug that affects roughly 3% of users but corrupts their data. What do you do?

    Scores low

    "I'd tell my manager right away and let them decide."

    Scores high

    Name the decision as yours: quantify the blast radius (3% of users, permanent data loss, no rollback), state the option you would take (ship with the affected path disabled), state what you give up (that feature slips a month), and say what you would escalate and to whom by when. Interviewers score the reasoning, not the choice.

    This measures judgement because both answers are defensible. What is being read is whether you can hold two bad options at once and still commit.

    Decision quality under ambiguity

    Walk me through how you would grow signups by 20%. ... Now assume you have no budget and no engineering time. Same target.

    Scores low

    "I'd still run the paid campaign, just smaller."

    Scores high

    Drop the first plan out loud, say what the new constraint removes, and rebuild from what is left: existing users, existing traffic, existing copy. Then state which of your original assumptions no longer holds.

    The follow-up is the actual question. Every strong interviewer changes a constraint mid-answer to see if you re-reason or defend.

    Conscientiousness

    Tell me about something you shipped that did not work.

    Scores low

    "The requirements changed, so it never really got a fair chance."

    Scores high

    State what you predicted, what actually happened with a number, the specific decision of yours that caused it, what you changed afterwards, and how you know the change worked. Ownership without self-flagellation.

    Interviewers are not testing humility. They are testing whether you measured the outcome at all.

    Role relevance

    Why this role, and why now?

    Scores low

    "I'm looking for a new challenge and your company is doing exciting work."

    Scores high

    Point at one specific thing in the job description, connect it to one specific thing you have already done, and say what you want to learn that this role uniquely offers. Three sentences, no flattery.

    This is the most-asked and worst-answered question in hiring. Generic answers read as mass application.

    03Structure

    STAR, without the padding

    Every structured interview answer has the same four parts. Most candidates spend eighty percent of their time on the first one.

    S

    Situation

    One sentence. Where, when, how big. Interviewers stop listening at sentence three.

    T

    Task

    What you specifically owned, not what the team owned. Say "I", not "we".

    A

    Action

    The decisions, not the activity. Two or three choices you made and the one you rejected.

    R

    Result

    A number, a timeframe, and what you learned. No number means the story did not happen.

    04The session

    What happens when you practise here

    Questions are generated from your resume and the actual job description, so you rehearse your own stories rather than generic ones.

    The interviewer changes constraints mid-answer and asks follow-ups, because that is where real interviews are won or lost.

    Every answer is scored on STAR structure plus the five hiring signals.

    You get your own answer rewritten, so you can hear the difference rather than read advice about it.

    05Questions

    Common questions