The First HR Hire's Guide to Building a Career Framework
By Career Ladder Builder
You inherited a spreadsheet and a mandate — here is what to do first
The Slack message came on your third day: "Hey, can you put together something on career paths? A few engineers have been asking and I keep saying 'we're working on it.'" You open the shared drive and find a Google Sheet titled levels_v7_FINAL_USE_THIS.xlsx, last edited fourteen months ago, with seventeen rows across three tabs that nobody can explain.
This is the starting point for most first HR hires at 30–100 person startups. You were brought in because the company finally hit the size where informal hallway conversations about careers stopped scaling. Now a senior engineer is asking whether she is an L4 or an L5. A sales rep who hit quota two quarters running wants to know what a promotion to Account Executive actually requires. And the founder — who made every people decision until last month — is pointing at you.
The good news: a career framework is one of the highest-leverage things you can build, and it does not have to take six months. This guide walks you through a practical, sequenced approach — from auditing what you have to running your first evaluation cycle — so you can go from inherited chaos to a working system without reinventing the wheel.
By the end, you will have a clear picture of the four phases, the decisions to make in each, and the tools that can cut weeks off the build.
Understand why this matters before you start building
Before you open a new spreadsheet tab, it is worth internalizing what is at stake — not to alarm yourself, but to prioritize correctly.
Career opacity is a well-documented driver of voluntary attrition. Pew Research Center (2022) found that 63% of workers who quit in 2021 cited no opportunities for advancement as a reason — tied with low pay. McKinsey (2022) found that 41% of departing employees named lack of career development as their top reason for leaving. When your company has 60 people and loses two or three of its best engineers or account managers, the cost is felt immediately.
Replacement is expensive. According to SHRM (cited in their Executive Network, 2025), replacing an employee typically costs between 50% and 200% of that person's annual salary, depending on seniority and role complexity. For a $100,000 senior engineer, that is $50,000 to $200,000 in recruiting, onboarding, and lost productivity — before the institutional knowledge loss. Gallup (2023) echoes the same range and calls it a conservative estimate.
"63% of workers who quit in 2021 cited no opportunities for advancement — tied with low pay as the top reason for leaving." — Pew Research Center, 2022
The other risk is consistency. Without a documented framework, promotion decisions rest on relationship quality, recency bias, and whoever speaks loudest in a leadership meeting. That is not just unfair — it creates legal exposure over time. The EEOC recorded 88,531 new charges in FY 2024 (EEOC, 2025), and employment counsel will tell you that documented, consistently applied promotion criteria are one of the first things examined when a bias claim arises. Always confirm your organization's specific documentation obligations with qualified employment counsel, since requirements vary by jurisdiction and company size.
A career framework solves all of this at once: it gives employees a visible path, gives managers objective criteria, and gives the company an audit trail.
Phase 1 — Audit what exists before you build anything new
The instinct on day thirty is to start fresh. Resist it. A clean-slate framework that ignores the company's lived job architecture breeds more confusion, not less.
Take stock of what is actually in use. Collect every artifact: that levels spreadsheet, any job descriptions in your ATS, offer letters with titles, org chart exports, and any Confluence or Notion pages mentioning "career paths." Do not worry about tidying them yet — just gather.
Identify your job families. A job family is a group of roles that share a core domain of work — Engineering, Product, Sales, Customer Success, Marketing, Finance, People Ops. Most 30–100 person companies have five to eight active job families, though they may not call them that. List each family and the rough headcount in it. If Engineering has 25 people and Customer Success has 6, you will sequence your build accordingly.
Map the titles that already exist. Pull every unique title from your HRIS or payroll system. Group them by job family. You will almost certainly find: titles that are genuinely equivalent but named differently across departments (a "Senior Software Engineer" and a "Senior Engineer" doing equivalent work), titles that imply a level that was never formally defined, and titles created during an offer negotiation that fit nowhere on a ladder. Document all of this — it will drive your first framework decisions.
Interview two or three people per family. A fifteen-minute conversation with a manager and one IC (individual contributor) per family tells you more than any spreadsheet. Ask: "What does doing this job well actually look like at each seniority level? What separates an average performer from a great one at your level?" These answers become the raw material of your competency statements.
This audit phase typically takes two to three weeks for a first HR hire handling it alongside onboarding. The output is a one-page map: job families, rough level count per family, existing title inventory, and a short list of ambiguities to resolve.
Phase 2 — Structure your framework (levels, tracks, and competencies)
With the audit in hand, you can build. The key decisions in this phase are levels, tracks, and competencies.
Levels. A level is a defined tier of scope, complexity, and ownership within a job family. Most early-stage companies run three to five levels per family; five or six is common once Engineering reaches 25–40 people. Resist the urge to add levels to solve a compensation problem — that is a sign you need compensation bands, not more rungs. Most frameworks cap at six levels, which covers the range from entry-level to executive contributor or VP.
IC and Manager dual tracks. One of the most important structural decisions you will make as a first HR hire is whether to build a manager track alongside the individual contributor track. The absence of a manager track forces high performers into management as the only path to advancement — and produces reluctant managers. A dual track lets a Staff Engineer or Principal Product Designer advance on technical merit without a direct-report requirement. This is worth the extra design effort even at 50 people. For a deeper look at how to structure the IC vs. Manager split, the career ladder build guide on this blog walks through it step by step.
Competencies. A competency is a statement of observable behavior — not a personality trait, not a vague aspiration. "Writes clear technical specifications that a junior engineer can implement without follow-up questions" is a competency. "Is a great communicator" is not. Each level in each job family should have four to eight competency statements describing what the role requires at that level — covering dimensions like technical skill, collaboration, communication, scope of impact, and people development (for managers).
Writing competency statements from scratch for every level across every job family is the most time-consuming part of the build. This is where starting from a validated template library matters. Career Ladder Builder seeds each job family from ONET-derived competency content — covering 20+ job families — so you are editing and refining language to fit your company rather than staring at a blank document. For background on how ONET competency content is organized and what it covers, this overview of the O*NET competency framework is a useful primer.
What to avoid. The two most common first-draft mistakes are competency statements that are purely output-based ("hits quota") rather than behavior-based ("navigates a stalled deal by identifying the real economic buyer and restructuring the approach"), and competency lists so long per level that evaluations become unwieldy. Aim for specificity over volume.
Phase 3 — Run your first evaluation cycle, then iterate
A framework that lives in a document is a documentation project. A framework that feeds a structured evaluation is a people-development system.
Your first evaluation cycle does not have to be elaborate. The goal is to validate that your competency language is legible to managers, surfaces real signal about where employees are, and produces a gap report you can act on.
Choose a pilot team. Pick one job family — ideally the one with the most urgent need or the most cooperative manager — and run a single evaluation cycle before rolling out company-wide. Twelve to eighteen people is a workable pilot size.
Structure the evaluation. Each employee is scored against the competencies defined for their current level, with a 1–5 scale (or equivalent), and the evaluator adds brief evidence notes — real observations, not impressions. An Admin approval step before scores are finalized prevents managers from submitting half-completed evaluations and creates an audit trail. After scoring is complete, a skill-gap report shows where each employee is meeting level expectations, where they are exceeding them (a promotion signal), and where they have gaps (a development conversation prompt).
Run it fast. The common fear is that a first evaluation cycle will take weeks of manager time. A well-structured workflow — with clear instructions, a defined window, and a platform that routes approvals automatically — should not require more than 30–60 minutes per manager per direct report. This walkthrough of running a first evaluation cycle in 30 minutes covers the mechanics in detail.
Debrief and refine. After the pilot, collect feedback from participating managers and two or three employees. Common refinements: competency statements that felt redundant or unclear, a level bar that was set too high or too low relative to who was recently hired at that level, or an evaluation window that was too compressed. One revision cycle before the company-wide rollout is normal and expected.
Phase 4 — Move from spreadsheet to a system of record
If you built your framework in Google Sheets — which most first HR hires do, because it is fast — you will hit the limits of that approach sooner than you expect. The breakdown patterns are well documented: no version control on framework edits (a change to a competency statement overwrites the history), no employee-facing visibility without extra sharing gymnastics, no structured scoring, no automated gap reporting, and no audit trail when a promotion decision is challenged.
The question is not whether to move off spreadsheets — it is when, and to what.
What to look for in a career framework platform. At 30–100 employees, the practical requirements are: a place to define job families, levels, and competency statements; a structured evaluation workflow with scoring, evidence notes, and an approval step; per-employee and team-level gap reports; and review-cycle scheduling so the next cycle does not fall off the calendar. The architecture should be career-framework-first — not a performance review bolt-on.
The pricing model matters. Most enterprise HR platforms charge per user, which means your cost grows with every hire. For a company scaling from 60 to 100 people, that math can make a system cost prohibitive exactly when you need it most. Career Ladder Builder is priced as a flat monthly rate per organization — the Essentials plan starts at $199/month for up to 50 employees, and the Professional plan is $349/month for up to 150 employees — so the cost is predictable as you grow. A 14-day free trial lets you import your framework and run a test evaluation before committing.
For a fuller look at how first HR hires and People Ops teams have approached this transition, the HR and People Ops career ladder guide covers the organizational and political dimensions alongside the technical build.
The four decisions that determine whether your framework sticks
Across all four phases, four decisions tend to make or break a first career framework at a startup:
Scope before launch. Build for two or three job families first — not all eight. A partial framework in production teaches you more than a complete framework in a document.
Manager buy-in before employee rollout. Managers who understand the framework and helped shape the competency language defend it in promotion conversations. Managers who receive it as a finished product from HR are passive at best. Run a manager briefing — even a forty-five-minute Zoom — before employees see anything.
Separate the framework from compensation. The framework defines levels and competencies. Compensation bands are a separate overlay. Conflating them in the first build creates political battles that delay launch by months. Get the framework live, run one evaluation cycle, then layer in compensation.
Version control from day one. Every time you revise a competency statement or add a level, document what changed and why. This is the audit trail that protects the company when a promotion decision is questioned.
For a quantified view of what a working career framework returns in retention, promotion accuracy, and legal defensibility, the career framework ROI breakdown walks through the modeled math anchored to sourced replacement-cost figures.
Your first ninety days: a sequenced plan
Here is a practical sequence for the first HR hire working on this alongside the rest of the job:
- Days 1–30 — Audit. Collect all artifacts, map job families, inventory titles, interview two managers and two ICs per family.
- Days 31–60 — Structure. Draft levels and competency statements for your top two or three families. Review with department heads. Finalize the IC/Manager track decision.
- Days 61–75 — Pilot evaluation. Run a single evaluation cycle with one job family. Collect manager and employee feedback. Revise.
- Days 76–90 — Rollout plan. Schedule company-wide evaluation cycles. Decide on tooling (spreadsheet vs. platform). Communicate the framework to employees with a clear explanation of what it is, how it will be used, and what it is not (it is not a performance improvement plan; it is a development tool).
The ninety-day timeline is realistic for a first HR hire who has executive support and a cooperative management team. If you are working without much of either, build in buffer — and prioritize the job families where attrition risk is highest.
Start with a free trial, not a six-month project plan
The first career framework does not need to be perfect. It needs to be specific enough to be useful, documented enough to be defensible, and live in a system that lets you improve it over time.
If you are ready to move from the audit to the build, Career Ladder Builder gives you O*NET-seeded competency templates for 20+ job families, a structured evaluation workflow with scoring and approval, per-employee gap reports, and flat-rate pricing that stays predictable as you hire. Start a 14-day free trial at careerevaluations.com/demo — no credit card required, and you can import your existing job family structure in the first session.
This article references occupational content from O*NET, sponsored by the U.S. Department of Labor / Employment & Training Administration (onetcenter.org). O*NET data is used under CC BY 4.0.
Enjoying this? Get more HR development guides in your inbox.
