Map your scope to the AI archetype that supports your promotion case

When your company redraws its ladder around AI, the promotion question changes. You are no longer asking whether you have done the job long enough. You are asking whether your current scope already looks like the next level's skills-defined archetype.

At Salesforce, leadership said every job had been redesigned, and almost 20,000 employees were in roles that did not exist a year earlier. That kind of shift makes tenure a weak argument.

The people deciding your promotion will compare your scope to the next level's skills, not your years. If your case is built on titles, projects, or time in seat, it will blur. If it is built on a named archetype and evidence artifacts, it will be easier to defend.

The next level is a scope claim

AI career levels are being rebuilt around what a person can direct, build, evaluate, and govern. Salesforce used a Four R workforce model that included redesign, reskill, redeploy, and rebalance. The company said the framework is intended to help companies become agentic by design. That language matters because it moves the bar from using tools to shaping outcomes.

Its people leader said builder traits are built into all roles. That means the distinction between levels may be less about a new title and more about the size of the problem you can carry. A builder archetype is a set of responsibilities you can point to.

Salesforce listed four AI-focused roles it was hiring for: Agentic Managers, Ethical AI designers, Prompt Engineers, and Forward Deployed Engineers. You do not need one of those titles to use the logic. You need to know which adjacent archetype your current work already resembles.

The map is the promotion case

The map should fit on one page and cover six points in order.

1. List your current scope. Write the decisions you make, the systems you touch, the people you coordinate, and the outcomes you own. Done looks like a short inventory: what you start, what you finish, and what you are accountable for when it fails.
2. Collect evidence artifacts. Save the work product, not just the story: a spec, a rollout plan, a postmortem, a dashboard, a policy, a model evaluation, a customer brief. You are done when a reviewer can open five to eight items without asking you to explain them.
3. Name AI and agentic responsibilities. Identify where you prompt, evaluate, govern, integrate, or manage AI-driven work. Finish with one sentence for each responsibility: what you did, what the AI did, and what you had to judge.
4. Match the archetype. Compare your scope to the next level's skills definition. If your company uses named roles, use them. If it does not, use a working label such as builder, integrator, evaluator, or agentic manager. The step is done when one paragraph says why your current scope already matches that label.
5. Write the distinction criteria. State what separates your level from the next one. Salesforce invested in a workforce innovation team that performs skills distinction across its jobs. You are ready when the skills the next level requires are listed and marked as shown or missing.
6. Close the gap. Name the one or two gaps that remain and the evidence you will produce before the review. End with a plan that has dates, not a wish list.

Warning: the common mistake is to describe your current job as if it were the next level. Do not inflate. A promotion case survives scrutiny when the gap is small, named, and already being closed.

The case must compare scope to the next level

Who decides a promotion is usually a mix of your manager, a peer or skip-level, and a calibration group. They do not have time to reconstruct your career from memory. They need a clean comparison.

Two-thirds of companies said they plan to hire for particular AI skills. The World Economic Forum’s Future of Jobs Report 2025 found that 63 percent of employers named the skills gap as the main obstacle to AI transforming business by 2030. That pressure shows up in reviews as a demand for specificity.

Your map should make the next level visible. If your company is redesigning roles around AI, your case should show that you are not waiting for a new title to prove the scope. Bring the map, the artifacts, and the named gap to the review.