joogy06/agent-foundry/career-internal-visibility

Career: internal visibility

<!-- REVIEW-BY: 2027-01-31 --> Verified 2026-07-29. Volatile figures live in career-coach/references/market-snapshot-2026-06.md, per family convention — this file carries the qualitative claim.

1. The asymmetry that governs everything here

Your external brand is discovered. Your internal standing is decided in rooms you are not in.

Ratings and promotions are settled in calibration, by people who mostly have not watched you work. What reaches that room is a manager's summary, a rating history, and whatever a sponsor can recall under time pressure — see career-leadership on sponsorship, which is the other half of this.

Two consequences, and both are practical:

1. Your evidence has to survive being retold by someone else. A contribution nobody can state in

one sentence with a number attached does not travel.

1. The person writing the summary is working from your text. In practice, most managers draft

from the self-assessment. Whatever you fail to write down, they will not invent — that makes §4 the highest-leverage writing you do all year.

This is not self-promotion, and framing it as such is how good engineers lose promotions. It is making real work legible to people who did not see it.

2. The annual rhythm

The cycle is compressing. Most large organisations now run mid-year or quarterly conversations alongside — or instead of — a single annual appraisal. More checkpoints means more chances to correct, and more occasions where an unwritten contribution silently fails to count.

3. Goals that survive the review

Write a goal so that whether you met it is not a matter of opinion. The test: could a reasonable person who dislikes you agree it was achieved?

The distinction worth internalising: measure what CHANGED, not what got SHIPPED. "Delivered the migration" is an activity. "Cut month-end close from 6 days to 2" is a result. Activity goals reward motion and are impossible to argue with in your favour, because the achievement is invisible.

• Name the baseline at the start. A goal that improves something has to say what it was before,

and nobody will accept a baseline reconstructed after the fact.

• Write the evidence line while writing the goal — how it will be shown, and where the number

will come from. A goal whose evidence source does not exist yet is a goal you cannot prove.

• Include one goal that is visibly bigger than your grade. Promotion cases are built on

operating at the next level before the title, and that has to be visible in the written goals or it reads as scope creep rather than readiness.

• Get goals written down in the system, not agreed in a corridor. A manager change mid-year is

common, and the new one inherits the record, not the conversation.

4. Evidence capture — the brag document

Keep a running record, updated when things happen. Not weekly if that fails; but at every completion, incident and piece of praise.

## <date> — <one-line title>
Problem:     what was wrong, and who it hurt
Did:         MY specific contribution, distinct from the team's
Result:      the number, and the baseline it moved from
Evidence:    link — dashboard, PR, doc, ticket, email, meeting note
Who saw it:  names — who can corroborate this in a calibration room
Level:       which behaviour at which grade this demonstrates

Why reconstruction fails, concretely: you forget the mid-year work entirely by December — recency bias is brutal and it is your own memory it distorts first. Dashboards get rebuilt, tickets get archived, the colleague who could corroborate it leaves. The evidence decays faster than the memory, and the memory decays fast.

• Capture praise verbatim, with the sender and date. A quoted line from a stakeholder outweighs

a paragraph of your own framing.

• Record what broke and what you did about it. Incidents you handled are among the strongest

evidence of seniority, and the only people who never cite them are the ones who did not keep notes.

• `Who saw it` is the field people skip and the one that converts. Evidence nobody can confirm

is an assertion.

Keep it somewhere you own and can take with you — the same record feeds the CV (career-application-writer) and the interview stories (career-storytelling). Respect confidentiality: figures, client names and internal metrics do not leave with you.

5. Writing the self-assessment

Specific, behaviour-based, forward-looking. Name what happened, why it mattered, and what comes next.

• Numbers, not adjectives. "Significantly improved reliability" is unquotable in a calibration

room. "Cut P1 incidents from 14 to 3 across two quarters" survives being repeated by someone else.

• Lead each item with impact, not chronology. The reader is skimming; the first clause is the

one that lands.

• Attribute honestly and claim precisely. "I led" where you led, "I contributed to" where you

contributed. Over-claiming on something a peer also reports is the fastest way to lose a manager's trust, and it is checkable.

• Answer the growth question with a real gap and what you did about it. A non-answer reads as

either no self-awareness or no ambition; a real gap with a documented response reads as senior.

• Mid-year is for course-correction, not summary. State where you are against each goal, what has

changed, and what you will do with the remaining time — and surface a slipping goal at mid-year rather than at year-end, when it is still recoverable and raising it still reads as ownership.

Write it from the brag document, in one sitting, and cut. Assembling from a record takes an hour; assembling from memory takes a day and produces less.

6. The internal skills profile — a system, not a formality

Large employers increasingly run internal talent marketplaces — Eightfold and its equivalents — where your profile is matched against internal roles, gig projects, mentoring and learning paths.

This changed what the profile is for. It used to be an HR record. It is now an input to a matching model that decides which opportunities are surfaced to you at all.

How it behaves, and what follows:

Update it on the same rhythm as the brag document, not when you are already looking — a profile edited the week a role opens is visible as such, and by then the matching has already run.

One thing to know rather than to act on: these platforms also model attrition risk from engagement, progression and compensation patterns. That is how they are sold. It is not a reason to game the profile — it is a reason to understand that the system is inferential, and to make sure what it infers about your skills is accurate.

7. Internal writing as deliberate visibility

A Confluence page or an internal blog post is the only artefact that keeps working while you are not in the room. It is read by people who will never attend your demo, and it is quotable months later.

The document that gets cited beats the document that is thorough. Optimise for being linkable:

• Write the thing people keep asking about. The runbook everyone reconstructs from Slack, the

decision record for the argument that recurs quarterly, the onboarding page that saves a week. The test is whether someone links to it without you.

• Put your name and the date on it, and keep it current. An owned, maintained page is a

reputation asset; an abandoned one is evidence you do not finish things.

• Decision records travel furthest. What we chose, what we rejected, and why is the document

people return to — and it demonstrates judgement, which is exactly what promotion bars ask about and what task lists cannot show.

• Internal blog and news posts reach sideways and upwards, across the organisation, which is

where sponsors are. A post-incident write-up, a "what we learned shipping X", a plain-language explanation of something your area does that others depend on.

• Write for the reader two levels up and one department across. Jargon-dense internal writing is

invisible to precisely the audience that matters for progression.

Then cite your own writing in the self-assessment. A link is verifiable evidence in a way a claim is not — this is the cheapest conversion of work into recorded impact available.

Use confluence-content-creator for the mechanics of the page, human-voice-writing for keeping the prose yours.

Getting a specific thing in front of a specific person — a proposal, a demo, a deck — is career-advocacy: pre-wiring the decision, the internal channels, and how to make the ask.

8. The promotion packet

Assemble, do not compose. If §4 has been running, this is an editing job.

1. State the case in one sentence — the level, and the claim that you already operate there.
2. Map evidence to the published criteria, in their language and their order. The committee reads

against a rubric; making them translate is making them work against you.

1. Three to five deep examples beat fifteen shallow ones. Depth is what survives challenge.
2. Show scope and duration — sustained operation at the level, not one visible quarter.
3. Name corroborators and give them notice, with the specifics they can confirm.
4. Address the obvious objection yourself. Every case has one; leaving it for the room means

someone else frames it.

The bar is "already operating at that level", not "ready to". Cases fail on evidence of scope far more often than on quality of work.

9. Targeting a senior AI or executive technical role

For a Head of AI, senior AI consultant or CTO-class role, what committees test is narrower and harder than the job description implies. They ask you to walk through a real programme you owned end to end — including the thing that broke, and what it cost — and they push on governance, decisions you reversed, and how you funded the work against sceptical stakeholders.

Three assets recur, and the strongest candidates have all three:

• Technical judgement deep enough to earn engineers' trust — architecture and data, not vendor

selection.

• Organisational design — building and running the team, not only the system.
• Translation into revenue, risk and velocity — the ability to state what the work was worth in

the terms an executive committee uses.