Scoring Each Fact Into Your Sixty-Second Interview Intro

Every interviewer opens with some version of "tell me about yourself," and the honest problem is not structure. It is selection. You have fifteen accomplishments and sixty seconds, and the standard advice hands you a present-past-future template without ever telling you which of the fifteen belong in the sixty. This guide is for a job seeker holding their raw history and one specific posting who needs to decide, defensibly, which facts make the cut and in what order. It gives you a scoring model you run against the posting on your screen, so the cut is a judgement you can explain rather than a gut call you hope was right.

Why the window forces a scoring rule, not taste

The 60-second budget mathematically limits you to about 6 to 10 facts, so discarding true lines is not a failure of nerve but a requirement of arithmetic. Conversational English averages roughly 150 words per minute, and most adults sit between 120 and 150. A 60-second answer is therefore about 150 words. If a clear, self-contained claim costs 15 to 25 words, the window holds somewhere between six and ten of them. There is no version of a good answer that fits more.

That ceiling is why a scoring rule is not optional. When you can only keep six to ten facts out of fifteen or twenty, the interesting question is which ones, and no amount of template advice answers it. Published length guidance clusters tightly around the same window.

Take the middle of that range, 130 to 170 words, as your budget. It is long enough to carry proof and short enough to force priority. The moment you accept the budget as fixed, the whole exercise changes shape: you are no longer writing an answer, you are running a cut.

The four dimensions every candidate line is scored on

Score each line of your history on four dimensions, because relevance alone is not enough when a fact can be relevant but unprovable, or provable but stale. Rate each dimension 0 to 3 and sum them; the total is what the line is worth for this posting. The four dimensions each measure something different, and each has a tell for when it lies.

• Relevance. Does the line map to a top-three requirement in this posting? A 3 maps directly; a 0 is off-target. It lies when a vivid origin story feels important to you but connects to nothing the employer asked for.
• Recency. How recent is the work? A 3 is current or last role; a 0 is a decade back. It lies when an old, impressive result crowds out a newer, more relevant one.
• Proof strength. Is there a number or a named result behind the claim? A 3 has a metric; a 0 is an adjective. "Managed a team of 15 for three years" reads as evidence; "strong leader" reads as filler.
• Differentiation. Would most candidates with your title say the same thing? A 3 is distinctive; a 0 is a cliche any peer could claim.

The scoring is deliberately blunt. You are not calibrating to two decimal places, you are separating the lines that clearly earn a slot from the lines that clearly do not, and forcing yourself to defend the ones in the middle.

Why differentiation is quantitatively necessary

Differentiation is not a nicety; it is forced by how crowded the field you compete against actually is. In Refolk's index of professional profiles, a plain job title places you in an enormous identical-titled crowd, which means the title itself signals almost nothing.

Those counts come from Refolk's index; the ratio is derived from them. When 348,446 people share your title in one market, saying "I'm a software engineer" locates you nowhere. What separates you is the named, metric-backed fact: the migration you led, the number you moved, the team you ran. This is exactly what your differentiation and proof-strength scores are catching. A line that any of those 348,446 peers could recite is a line doing no work in your sixty seconds.

Why the first fact does disproportionate work

Lead with your single strongest role-relevant fact, because judgements form in seconds and the opening claim carries more weight than anything that follows. This is not a soft claim. A University of South Florida study found that after 12 seconds of silent video of a candidate, observers made hiring recommendations that significantly correlated with those of people who watched the entire interview. Separate research from the University of Toledo found that ratings from just the first 20 seconds of an interview significantly predicted final scores after a full 20-minute session.

On top of that speed sits a primacy effect: information presented early carries more weight, so the first 30 seconds may matter more than the next 30 minutes. The implication for selection is direct. Ordering matters as much as selection, because a strong fact buried in position four is partly wasted. You want your highest-scoring, most-provable, most-differentiated line first, not a warm-up.

The funnel figures are drawn from the dossier's length and inventory guidance: you start with a dozen to twenty lines and end with the six to ten that survive, one of which is doing outsized work.

The selection and ordering procedure

Run these eight steps in order against one posting. The first two build your raw material, the middle four are the cut, and the last two turn one skeleton into a delivery you can actually give in the room.

Step 3 is the whole method. Once every line carries a number, the cut in step 5 stops being agonising and becomes clerical: you keep the top scorers until the budget runs out. That is the difference between a defensible answer and a hopeful one.

Building the requirement list in step 2 and mapping your history to it is exactly the tailoring work Refolk does when it reads a posting and scores how well your history fits, so if you are tailoring an answer for every loop, let the tool surface which of your facts line up with each posting before you score by hand.

Fitting survivors to the template without letting it choose for you

Every top guide prescribes present-past-future, so use it as a container for your scored survivors, not as the thing that decides what goes in. The formula, attributed to Lily Zhang of the MIT Media Lab, starts with the present, where you are now, segues to the past, the experiences and skills you gained, and finishes with the future, why this opportunity excites you. One guide even assigns proportions: present 30 to 40%, past 30 to 40%, future 20 to 30%.

The trap is treating the template as the answer. It converges across every guide precisely because it is the easy part. The unserved gap is which accomplishment fills each slot, and that is what your scores decide. Sort your survivors into present, past, and future buckets, but override the arc when primacy demands it: if your strongest scored line lives in the past bucket, some sources let you open past-present-future instead. Order within the arc is a judgement; leading with your best fact is not negotiable.

LEAD (highest total score, most provable): ____________________
PRESENT (current role + one role-relevant proof): ____________________
PAST (one earlier line that maps to a top-3 need, with a metric): ____________________
PAST (optional second, only if budget allows): ____________________
FUTURE (why this specific role, tied to one stated need): ____________________
Total facts: ____ (target 6-10)   Timed length: ____ sec (target 60-90)

Keep the skeleton as bullets, not sentences. You rehearse from it and vary the wording each time, because a perfectly cut answer read robotically still fails.

How this goes wrong: the failure modes and their false positives

The most common failures are lines that score high on pride and low on the dimensions that matter, and the fix for each is a specific check you can run before you walk in. Each failure mode below has a false positive, the reason a bad line looks good, and a concrete test.

The life-story opener is the most seductive. Off-target detail suggests you struggle to focus on what matters, so the origin story that has nothing to do with the posting signals a weakness even when it is charming. Resume recitation is chronological completeness masquerading as thoroughness: every role gets a mention, none gets a metric. Rambling is a real cost, not a stylistic one; one recruiter reports a candidate who talked and talked for 45 minutes off a single question. Length is itself a signal of how well you prioritise.

Two more failures live in delivery rather than selection. Stage mismatch wastes deep technical judgment on a recruiter or logistics on a hiring manager. Memorised delivery undoes a good cut: memorised answers sound memorised, so rehearse from the skeleton and vary the wording. Both are caught by the last two steps of the procedure, not the scoring.

Adjusting the cut for the screen versus the hiring manager

Build one scored skeleton, then produce two variants, because the stage changes emphasis, not length. A phone screen is usually run by a recruiter or coordinator after reviewing your materials, trying to narrow the pool. It covers a summary of education, work history, and skills, plus basics like salary expectations, availability, and career goals. The hiring-manager interview is a more in-depth assessment of fit and ability to do the job, conducted by the person who holds final say.

For the screen variant, re-score with relevance to the stated must-haves weighted highest, and let one logistics line survive. For the manager variant, weight proof strength and differentiation highest, and swap in the line that shows judgment rather than the line that shows you meet a checkbox. The budget stays 60 to 90 seconds either way; you are reordering and substituting one or two survivors, not writing a second answer from scratch.

To see how differentiated the crowd around a real role actually looks before you decide which of your facts stands out, search the kind of profile you are up against.

Notice how concentrated even a large field can be: in Refolk's index sample, London accounted for 10 of 25 UK profiles, or 40%, so geography clusters candidates on top of each other and sharpens the need to differentiate on results.

Before you call the answer done

Run this checklist against the finished skeleton, out loud, with a stopwatch in hand. It catches the failures that survive scoring because they live in delivery.

Keeping the answer current across a search

Re-run the scoring for every posting rather than reusing one answer, because the same history scores differently against different requirements. The inventory in step 1 is durable: build it once and keep adding lines as you finish work. The requirement extraction in step 2 and the scoring in step 3 are per-posting and cheap to redo, usually 20 minutes once the inventory exists.

Refresh the inventory whenever you ship something with a number attached, because proof strength is the dimension most job seekers are short on and new metrics are the fastest way to raise a line's score. When a new posting lands, do not ask "what's my tell me about yourself answer." Ask "which six to ten of my facts score highest against this one," and let the budget do the cutting it was always going to do.