Internal Mobility: Make Skills Based Moves Real

I've found one simple rule makes this real: hire for readiness to grow, not just proof of doing.

In practice, I look for about 70% alignment on core capabilities, and I treat the other 30% as a designed stretch, not a reason to pass. It is always easier to "pass" because developing people requires intentional effort.

But the shift isn't just the rule, it's how we support it:

We anchor roles on what success looks like, not just past titles
We get really honest about what's truly essential vs. teachable

This does two things:
It creates real access for internal talent, and it builds a culture where growth is expected, not penalized.

From a coaching lens, it also shifts the conversation with team members from "Am I qualified?" to "What's my next edge to grow into?" which is where you start to see confidence and mobility compound.

Most internal mobility is a total sham. Managers treat their best people like private property and block transfers to keep their own numbers high. We broke that cycle with the "No-Veto Rule." If an employee passes a technical skill test for a new role, their current boss doesn't get a vote. It sounds harsh. But it stops talent hoarding. It forces our leaders to actually mentor their teams instead of just riding their coattails.

We also ditched the "years of experience" trap for internal moves. We use "Skill Proxies" instead. If a support rep is a wizard at explaining complex policy jargon to angry customers, we know they have the logic for SEO or technical writing. We give them a one-week trial project to prove it. If they nail the logic, the job is theirs. Titles are just lazy shorthand. Outcomes are the only currency that matters.

I promoted my warehouse manager to VP of Operations despite zero executive experience because I stopped writing job descriptions around credentials and started writing them around problems to solve.

Here's the rule that made it work: Every internal role opening had to include a "Skills Translation Guide" that mapped what we actually needed to what people were already doing. When we needed someone to oversee our 140,000 sq ft facility expansion, the traditional hire would've been someone with a construction management degree. Instead, I looked at what the role actually required: coordinating multiple vendors, managing timelines under pressure, and making quick decisions when things went sideways. My warehouse manager had been doing exactly that for three years, just with different stakeholders.

The breakthrough was forcing hiring managers to list five specific situations the person would face in their first 90 days, then asking which current employees had handled similar situations anywhere in the company. Our customer service lead became our first marketplace partnerships manager at Fulfill.com because she'd spent two years translating frustrated brand owners' complaints into operational fixes. That's the same skill as managing 3PL relationships, just from a different angle.

The mistake most companies make is treating internal mobility like a favor to employees rather than a competitive advantage. When I scaled my fulfillment company to $10M, roughly 60% of our leadership team came from internal promotions where we'd recognized adjacent skills. These people ramped faster, understood our culture, and had credibility with the team that no external hire could match.

The real test: If you can't explain to a current employee why they weren't considered for a role using specific skills they lack rather than credentials they don't have, your process is broken. Skills-based hiring isn't about being nice to internal candidates. It's about recognizing that someone who's solved similar problems in a different context will outperform someone with a perfect resume every single time.

One rule changed internal mobility from aspiration into a scheduling requirement. Every open role first needed three adjacent skill matches listed. Managers could not post externally until those transferable capabilities were defined. For example, service representatives often matched operations roles through troubleshooting discipline. Merchandisers frequently fit procurement openings because pattern recognition beats exact experience. This forced hiring teams to evaluate learning velocity before pedigree.

We also required a paid two week shadow sprint before interviews. Candidates handled real tasks with structured scoring on judgment and adaptability. That revealed hidden operators better than resumes, titles, or manager opinions. Internal movement accelerated because evidence replaced assumptions and confidence replaced politics.

In order to realize skills-based mobility, companies need to adopt a capability-first rule that enables companies to treat internal movements with the same degree of technical rigor as they do with external hires, while also taking into consideration the employee's experience within the company. The main error companies make is equating the amount of time an employee has worked with the company to the amount of competency they have.

Take an employee who has spent three years in a support role; their debugging, logic, and systems architecture experience for a developer role must be considered when they look at opportunities for moving into a developer role; however, when the employer only looks at the employee's HR file which shows their current job title, the employee's experience in support is ignored.

We propose an additional phase called skill-proofing, which states that when an internal candidate is applying for a new role within the organization; they would not be screened based on their previous title or length of tenure with the company, but rather examined based on their ability to perform a task associated with the new department. To accomplish this, we would ask each candidate who is interested in an internal move to complete an objective technical skills assessment or complete a project simulation. This would allow the company to evaluate the applicant as an engineer, strategist, or builder as opposed to just a member of a particular department.

By doing this, we shift the conversation from "Do you have the necessary experience?" to "Can you complete this type of project successfully?" By eliminating the "pedigree" barrier with evidence of capability, organizations find that their best resources are typically within their own walls, waiting for the right opportunity to showcase their skill set.

The practical rule that made skills-based hiring real at GpuPerHour is what I call the project proof standard. Instead of asking whether someone has the right title or degree for a role, we ask whether they have completed a project that required the core skills the role demands. If they have, the role is open to them regardless of which team they currently sit on or what their formal background looks like.

The way this works in practice is straightforward. When we post an internal role, we list three to five specific deliverables that the person in that role will need to produce in their first ninety days. Not abstract competencies like strategic thinking or cross-functional leadership, but concrete outputs. For example, when we needed someone to lead our data center partner onboarding process, the posting described the actual work: build a standardized hardware validation checklist, design the pricing integration workflow, and create the partner performance dashboard. Anyone in the company who had done work adjacent to those deliverables could apply, even if they came from our customer success team or our engineering team.

The adjacent skills recognition piece is critical. We found that our customer success team had people who understood partner economics deeply because they spent every day talking to customers about pricing and capacity. That knowledge translated directly into partner-side work, but under a traditional job-title framework, those people would never have been considered for the role.

The result has been that our internal mobility rate is roughly three times what it was before we adopted this approach. More importantly, the people who move internally ramp faster than external hires because they already understand how the marketplace operates. They just need to apply that understanding in a new direction.

Faiz Ahmed
Founder, GpuPerHour

The most useful rule we used was hiring for clear signs of pattern recognition instead of matching exact job titles. If someone had solved a similar problem in a different role we still treated that as relevant experience. This helped us look past titles and focus on the choices they made the tradeoffs they handled and how quickly they learned new work. It gave us a better way to judge real ability.

To make this practical we added one required interview question for people moving internally. We asked them to share a time when they inherited a messy process found the main issue and improved the result. This question quickly showed which strengths could transfer well to a new role. People from operations account support and finance often did very well because they already understood the business and knew where problems existed.

The practical rule that has actually moved the needle for us at Dynaris: every internal job posting opens to internal candidates one full week before any external posting goes live, and every hiring manager has to interview at least one internal applicant before reviewing external resumes. That's it. Most companies say they prioritize internal mobility but never enforce it operationally - the external pipeline arrives faster, the hiring manager is busy, and the internal candidate gets a polite "thanks for applying." The week head start changes the default. The other piece that made skills-based hiring real for us was rewriting our role requirements as outcomes rather than as resumes. Instead of "3-5 years experience in product marketing," the requirement reads "has shipped pricing or positioning changes that produced measurable conversion lift." That phrasing immediately surfaces internal candidates whose past role didn't carry the right title but whose actual work matched the outcome. We've moved two engineers into product management roles this way - neither would have made it past a traditional resume screen, but both had the underlying skill demonstrated on real projects. The recognition trick that helped us spot adjacent skills: we run a quarterly "projects you led" exercise where every employee writes a one-page summary of work they shipped, regardless of their job title. The summaries get tagged by skill (data analysis, customer interviewing, technical writing, vendor management) and the tags feed our internal mobility dashboard. When a role opens, we can search the tag library for people who've done that work, even if their current title doesn't reflect it. The honest constraint: skills-based mobility only works if the company is willing to backfill. The biggest blocker isn't HR process - it's the manager who blocks internal moves because losing a strong performer is painful. The fix is making backfill support visible and budgeted, so saying yes doesn't punish the manager. Until that incentive is corrected, every other policy is theater.

Skills-based hiring breaks down in most companies at exactly the same point: the job description still lists a title as the baseline, so internal candidates who've done the adjacent work but don't carry the matching title get filtered before a human sees them. We've seen this in how our customers structure their internal mobility, and it's almost always a labeling problem, not a capability problem.

The rule that actually moved things was simple: anyone who'd been doing at least 60% of the target role's core tasks, in any capacity, for six months or more got a first-round conversation, no exceptions. That covered people on stretch assignments, people covering for departures, people who'd picked up scope during a reorg without a title change. Fill time on internal roles dropped noticeably once that rule was in place, and the acceptance rates were higher than external hires, which I find pretty hard to argue with.

Every open role required a bridge path for one internal mover before posting broadly first. This made managers define learning in 30, 60, 90 days instead of fixed profile for better planning clarity. Once this bridge existed, internal talent was seen less as risk. It became viewed as investment over time.

Most roles are not filled by perfect technical match. They are filled by consistency coachability and accountability in practice. People who know the operating rhythm often ramp faster than outside candidates with strong resumes in real work settings. Managers were asked to list non negotiables and separate them from trainable skills.

A practical rule we used was every open role needed six month apprenticeship path before a perfect hire. If a strong internal person could reach full productivity within six months we counted them as qualified. This simple idea forces leaders to separate what essential from what is familiar. Most roles become more open once we apply thinking honestly.

We supported it with short transition plan listing the first three skills to learn. It included the first decision they would own and the operator who would coach them. Internal mobility fails when companies celebrate in theory but leave learning curve to chance. Unlock is not lowering bar but building a faster bridge using support and trajectory instead of title matching.

The rule I used: before any role goes external, it has to be declined internally first — and that declination has to be documented.
Most organizations say they prioritize internal mobility but never operationalize it. There's no process. Managers post externally out of habit or because they already have someone in mind. Internal candidates find out a role was filled when they see the LinkedIn announcement.
The practical fix is a mandatory internal posting window — minimum five business days — before any requisition goes to external sourcing. During that window, the hiring manager has to actively notify their team and any adjacent teams where the skill set might exist. Not just post it on the intranet nobody checks.
The second piece is adjacent skill recognition. Most job descriptions are written as a wish list for the person who just left the role. Rewrite them around the outcomes the role needs to produce in the first 90 days. When you do that, you stop filtering out internal candidates who don't have the exact title history and start seeing who can actually do the work.
The companies that make internal mobility real treat it as a sourcing channel — not a courtesy. That means metrics, accountability, and a hiring manager who gets asked in the debrief: did you consider internal candidates and why or why not?"
— Desiree Goldey, Founder & CEO, Do Better Consulting * dobetterconsulting.net