Reverse the job post, then cross-examine your resume

How do you find out what they'll ask, and whether your own stories hold up?

A job post is a list of what the team worries about. Count what it mentions and you get a rough map of where the questions will come from.

Your resume is the other source. Anything on it is fair game, and follow-ups go deep. An interviewer at Kapwing described a candidate with a polished, keyword-heavy resume who was fluent at first, then couldn't explain why a load spike happened, or what data a claimed feature handled.

Here's the rule that matters: use AI to pressure-test your real experience, and never to invent experience. If you can't defend a line through five follow-ups, fix your understanding or remove the line.

  • Demand: How often a skill shows up in the post. A rough signal, not a fact.
  • Priority: Demand multiplied by how weak you are at it. That's what you study first.
  • Follow-up ladder: Why, how, what broke, what would you change, what would it cost? Interviewers walk down it.

Steps:

  1. Paste the post into the mapper. Or ask AI to list the skills, with quotes from the post.
  2. Score yourself from 1 to 5. Be honest. A later mock will correct you anyway.
  3. Study by priority. Demand times weakness tells you where a day pays off most.
  4. Cross-examine each resume line. One line at a time, up to five follow-ups.
  5. Fix the gaps with facts. Look up the real numbers from your work. Don't let AI supply any.

Don't let AI write your story: A model will happily produce a stronger-sounding story, with invented numbers. That's how a candidate ends up silent at the follow-up. Ask it for questions, and keep the answers yours.

Prompt, Cross-examine one line:

You are a skeptical senior engineer interviewing me. Here is one line from my resume:
[line]
Ask one follow-up at a time. Go deeper with each: why that approach, how it worked, what broke, what you measured, what you'd change. Don't help me or suggest answers. After 5 questions, list exactly where my answers got vague.

Prompt, Read the job post like the hiring manager:

Here is a job post:
[post]
List the skills it really cares about, ranked. For each, quote the words that show it and write the two interview questions most likely to test it. Say which skills are only implied. Don't guess the company's process.

Code, Counting what the post asks for. A word count with care taken over word edges, so 'rag' doesn't match 'fragrance' or 'storage'.

export function mapJobPost(post: string, rules: SkillRule[]): [string, number][] {
  const out: [string, number][] = [];
  for (const { skill, keywords } of rules) {
    const hits = keywords.reduce((n, k) => n + (post.match(new RegExp(`(^|[^a-z0-9])${escape(k)}(?![a-z0-9])`, "gi")) ?? []).length, 0);
    if (hits > 0) out.push([skill, hits]);
  }
  return out.sort((a, b) => b[1] - a[1] || a[0].localeCompare(b[0]));
}
  • (^|[^a-z0-9]): The match must start at a word edge.
  • (?![a-z0-9]): And must end at one.
  • escape(k): Keeps a keyword such as 'c++' from being read as a regular expression.

Code, From demand to a study order. Combines what they want with what you lack.

/** Priority is demand times weakness, where 5 means strong. A skill you've nailed scores 0 and drops off. */
export function studyOrder(demand: [string, number][], myScores: Record<string, number>): { skill: string; priority: number }[] {
  return demand
    .map(([skill, hits]) => ({ skill, priority: hits * (5 - (myScores[skill] ?? 1)) }))
    .filter((x) => x.priority > 0)
    .sort((a, b) => b.priority - a.priority || a.skill.localeCompare(b.skill));
}
  • hits * (5 - (myScores[skill] ?? 1)): A skill you haven't scored counts as weak, since not knowing is a reason to look.

  • .filter((x) => x.priority > 0): A skill at 5 of 5 drops off the list, however often it's mentioned.

  • Failure, Treating the map as the truth: It's a count of words. Ask your recruiter what the rounds are, too.

  • Failure, Keeping a line you can't defend: A confident line followed by silence does more damage than leaving the line out.

Why multiply demand by weakness?
A skill you've mastered needs no time however often it's mentioned, and one the job never mentions isn't worth much either. The product points to where a day pays off.
What should you never ask AI to do to your resume?
Add experience or numbers you don't have. You'll be asked about them.

Sources: