Yueseryueser.com

← All workflows

Turning your job change into a story that persuades

A career story usually fails not because it lacks drama but because it confuses what I did with what I judged. Persuasion comes from choices and their costs, not from titles and project names.

How to do it

  1. Line up the scattered facts first

    Write down each node: why you wanted to move, which options you looked at, what made you decide, what worried you. Use “Turn scattered notes into structure” to order them as starting point, turn, choice, cost, result. Give facts before conclusions; it will fill in causes for you, and the parts it invents are exactly what you need to check.

  2. Separate the facts from your interpretation

    Use “Separate Fact, Inference, and Preference” to split the story into three kinds of statement: “the team was chaotic” is a judgment, “two managers in three months” is a fact, “I wanted a stable direction” is a preference. Mixed together it sounds like a complaint; separated, it reads as judgment.

  3. Attach evidence to every claim

    “Check whether claims match their evidence” will make you answer: when you say you led the rewrite, what is the evidence? Who decided, what did you change, did any metric move, what failed? This step swaps “led, drove, was involved in” for accurate verbs, and exposes the part you did not actually do.

  4. Rewrite it for each audience

    Use “Rewrite the same content for different readers” to prepare two versions: for a technical interviewer, the decisions and trade-offs; for HR, why you left, why here, how long you intend to stay. One set of facts, different emphasis. The facts must match across versions or they fall apart when the two interviewers compare notes.

  5. Stress-test it with a doubting reader

    Have “Play the reader who will close the tab” act as an interviewer who already suspects you left because you were failing, and name the sentence that increases the suspicion. It usually lands on a place where an adjective replaced a fact — “the culture was bad” with no incident attached.

Prompts used

FAQ

Should I tell the truth about why I left?

Yes, at the right level of detail. Pay, growth, and direction are all fine to name; the mistake is making the last employer the villain. “I want to work on X, and that team is mainly doing Y for the next year” puts the reason on the work instead of the people.

How do I explain frequent job changes?

Do not explain each move in turn; that turns into a defense. Pick one thread: what you were after, which moves brought you closer, and which one was a misjudgment. Admitting one error is more convincing than covering three, and it moves the conversation from why you can't stay to how you judge an opportunity.

What if I have no impressive results?

Talk about the choices you made under constraint: what you cut when resources ran short, what you protected during an incident, how a disagreement got settled. Interviewers can tell luck from judgment. Without a big win, a specific small decision is more credible than an inflated project.