Why Senior LinkedIn Profiles Score Lower on Proof Than Mid-Level

2026-09-06

The pattern

Avery scores every profile across four pillars: First Impression, Story, Proof, and Visibility. Proof asks a narrow question. Not what were you responsible for, but what is different because you were there, and how would a stranger know.

You would expect Proof scores to rise with seniority. More years, more launches, more budget, more evidence. In practice we see the opposite often enough that it is worth writing down: a VP profile will frequently score lower on Proof than a senior individual contributor profile at the same company.

This is a qualitative pattern from reviewing profiles, not a statistic, and we are not going to dress it up as one. But it repeats enough, and the mechanisms behind it are specific enough, that it is worth naming. There are four, and they compound.

Mechanism one: scope substitution

Senior people describe scope because scope is the currency of senior hiring conversations. Ask a Director what they do and you will hear team size, budget, region, and remit. That is not a bad instinct. In a live conversation, scope is the first thing the other person needs to calibrate level.

The problem is that scope is a description of the box you were put in, not of what you did inside it. "Led a 40 person operations organization across four sites" tells a reader the size of the job. It tells them nothing about whether you were good at it. Two people can hold that identical line while one of them turned a failing region around and the other one presided over its decline.

Proof scores the second half of that sentence, and on a lot of senior profiles the second half is missing entirely. The Experience section reads as a series of org charts.

The fix is a sentence shape. We call it Scope, Action, Change, and it is deliberately boring:

Scope: the box. 42 people, four sites, the East region.
Action: the specific thing you decided or built. Named one escalation owner per site.
Change: what moved, with a before and an after. On time delivery from 71 to 94 percent over three quarters.

Most senior profiles have the Scope and nothing else. Some have Scope and Change but no Action, which reads as luck or as taking credit for a tailwind. All three, in that order, is what Proof is looking for, and it is usually one added clause per bullet rather than a rewrite.

Mechanism two: the we problem

The more senior you are, the more of your work was done by other people, and the more uncomfortable first person singular starts to feel. Leaders who are good at their jobs have usually spent years deliberately transferring credit to their teams, because that is how you keep a team. Then they write a LinkedIn profile in the same voice and every accomplishment arrives as "we".

The instinct is correct and the venue is wrong. A hiring manager reading "we grew the segment 40 percent" cannot tell what you contributed. The sentence is not modest, it is unresolved, and the reader has to guess. Under time pressure, readers guess low.

The fix is not to claim the team's work. It is to be specific about the layer you operated at, which is more impressive than the vague version anyway. Compare:

Vague we: "We grew the enterprise segment 40 percent year over year."

Resolved: "Restructured enterprise coverage from geographic to vertical territories and rebuilt the comp plan around multi year deals. The team grew the segment 40 percent year over year, with the vertical accounts carrying most of it."

The team still gets the growth. You get the two decisions, which is what a hiring manager is actually buying. Nobody is hiring a Director because they personally closed deals. They are hiring the judgment that produced the structure.

Mechanism three: the confidentiality ceiling

This one is real and it is not a writing problem. Senior work is disproportionately covered by confidentiality: unannounced reorgs, deals that did not close, margin figures, headcount actions, product roadmaps, litigation, anything pre IPO. A VP of Finance often genuinely cannot publish the numbers that constitute their best evidence.

What we see on profiles, though, is that people treat this as binary. Because the number is confidential, the whole accomplishment disappears, and an entire two year stretch of the most consequential work of someone's career shows up as one line about ownership.

The fix is to publish the shape without the value. Four techniques, in rough order of preference:

Relative instead of absolute. "Cut close time by 40 percent" reveals nothing about the company. "Reduced close from twelve days to seven" reveals almost nothing either. Percentages and ratios are usually publishable when the underlying figures are not.

Order of magnitude. "A nine figure portfolio" or "a mid eight figure book" is standard, accepted, and non specific.

The mechanism, not the outcome. If you cannot state the result, state what you built and let it imply the scale. "Built the pricing governance process now used across all four business units" is evidence, even with no number attached.

Third party verification. When you cannot say it yourself, have someone else say it. A recommendation from a former CFO describing what you fixed is proof, and it sits outside your own claims, which makes it stronger than anything you could write.

We have a longer treatment of this in how to show proof when your work is confidential, because it is one of the most common blockers we get asked about.

Mechanism four: recency inversion

This is the one people are most surprised by when we point it out, and it is the easiest to fix.

On a lot of senior profiles, proof density is highest in the oldest roles and lowest in the most recent one. The Analyst job from 2014 has three specific accomplishments with numbers. The VP role they have held for the last four years has two lines about ownership and remit.

The reason is timing. People write their profile carefully when they are job searching. A senior person who has not searched in six years last did that writing when they were mid level, and they wrote that role while it was fresh, while the numbers were still on a slide they had just presented. Every role since has been added in a hurry, at the moment of the promotion, when there were no results yet because the role had just started. And then it never got revisited.

The result is a profile whose evidence peaks eight years ago. A reader scanning top down hits the thinnest, vaguest content first, which is also the content that determines whether they keep reading.

The fix is a diagnostic you can run in two minutes. Count the quantified or specific outcomes in each role. Write the counts down next to the titles. If the numbers go down as you move up the page, you have recency inversion, and the highest return edit available to you is to rewrite the current role and delete half of the oldest one. Nobody is hiring you for 2014.

Why the scoring does not curve for seniority

A fair question: if senior work is genuinely harder to evidence, should the Proof pillar be more generous at senior levels?

We decided no, and the reason is that the scoring is meant to predict how a reader reacts, not to reward degree of difficulty. A hiring manager looking at a VP profile with no evidence on it does not think "confidentiality constraints, understandable". They think "I cannot tell what this person is good at" and they move on. The bar is higher at senior levels, not lower, because the cost of the hire is higher and the reader is more skeptical.

There is also a practical argument. Every senior profile we have looked at that scored well on Proof had the same constraints as the ones that scored badly. Same NDAs, same team attribution norms, same busy schedules. They just solved it, usually with relative figures and mechanism statements rather than raw numbers. The constraint is real. It is not disqualifying.

Student profiles are the one place we do adjust the weights, because the constraint there is structural rather than solvable: a sophomore does not have five years of outcomes to describe. A VP does.

What to do this week

1. Count the specific outcomes in each role, top to bottom. If the counts decline as you move up the page, you have recency inversion.

2. Find every line that is pure scope and add an Action and a Change to it. Start with the current role.

3. Find every "we" in your Experience section. For each one, add the decision or structure that was yours. Leave the outcome with the team.

4. For anything you cannot publish, convert it: relative figure, order of magnitude, or mechanism.

5. Cut the oldest roles down to two lines each. That space belongs to the last four years.

If you want to know where your profile actually sits before you start editing, an Avery audit scores all four pillars and ranks the fixes by impact, so you spend the hour on the thing that moves the number rather than the thing that is easiest to change.