We Killed Job Titles—A Flat Structure Was Faster

Our engineering ladder had 14 levels. Junior Engineer I through Distinguished Engineer. Each level had a detailed rubric with 12 competency dimensions scored on a 5-point scale. Promotions required a written packet, three peer endorsements, a skip-level review, and a calibration committee deliberation.

In any given quarter, 30% of our engineering conversations were about levels, not engineering. "Am I ready for Staff?" "Why did they get promoted and I didn't?" "What do I need to demonstrate for the next level?" Engineers spent more time positioning for promotion than solving problems.

We eliminated all titles except "Engineer." Everyone is an engineer. Compensation is based on impact and market rate, not title. We saved 400 hours per year in promotion administration and eliminated an entire category of organizational dysfunction.

How Titles Create Dysfunction

Title inflation distorts the market. Every company inflates titles differently. A "Senior Engineer" at a startup might have 3 years of experience. At a Big Tech company, 8-10 years. A "Staff Engineer" at one company writes code; at another, they haven't committed code in years.

This creates a ratchet effect. Engineers expect their next role to have an equal or higher title. Companies inflate titles to attract candidates. New hires arrive with inflated expectations. The cycle continues until titles become meaningless.

We hired a "Principal Engineer" from a large company. His principal-level work at that company would have been senior-level work at ours. He was frustrated by what he perceived as a demotion. We were frustrated by a misalignment between title and capability. Both of us were victims of an industry that uses titles inconsistently.

Levels create artificial ceilings and floors. A Junior II engineer has an idea that could save the company millions. But juniors don't architect systems — that's a staff-level activity. So the idea gets routed to a senior or staff engineer who may or may not execute it as well.

Conversely, a senior engineer who wants to spend a month doing hands-on coding instead of "leading" and "mentoring" feels pressure to delegate, because individual contribution is expected of lower levels. The title system prescribes behavior based on hierarchy rather than allowing people to do their best work.

Promotion-seeking replaces impact-seeking. When promotions are the primary mechanism for compensation growth, engineers optimize for promotable activities. They choose visible projects over impactful projects. They write blog posts and give talks (promotable) instead of fixing tech debt (not promotable). They volunteer for cross-team initiatives (good for the packet) instead of going deep on their team's hardest problems.

The promotion-seeking behavior is rational. The system incentivizes it. But it's destructive. The company's hardest, most impactful problems often have no promotional visibility. The engineer who quietly maintains the critical infrastructure that runs 60% of revenue gets overlooked while the engineer who launches a shiny new feature gets promoted.

Our Flat Alternative

One title: Engineer. No levels, no ladders, no rubrics. The most junior person on the team and the most experienced person on the team have the same title.

Compensation based on impact and market rate. Every six months, managers assess each person's impact on the team's goals and adjust compensation accordingly. Impact is defined broadly: shipping features, fixing bugs, improving processes, mentoring teammates, handling incidents, writing documentation. Any activity that makes the team more effective counts.

We use market data from Levels.fyi, Glassdoor, and our own salary surveys to ensure compensation is competitive. But we don't slot people into bands based on title. Instead, we ask: "What would this person command on the open market given their demonstrated capabilities?" and pay accordingly.

Influence based on expertise, not title. In technical discussions, the person with the most relevant expertise leads — regardless of seniority. A newer engineer who deeply understands the caching layer has more authority on caching decisions than a veteran who has never worked on it.

This was the hardest cultural shift. In a titled organization, senior people are expected to have the final word. In our flat structure, expertise has the final word. This required senior engineers to let go of positional authority and newer engineers to step up when they had relevant knowledge.

What We Gained

400 hours per year returned to engineering. No more promotion packets. No more calibration committees. No more level-mapping exercises for new hires. No more "what level is this role?" discussions. That time is now spent on actual engineering work.

Collaboration improved dramatically. When there is no hierarchy, there is no "that's beneath me" or "that's above my level." Engineers work on whatever creates the most impact for the team, regardless of complexity or visibility. Senior engineers fix bugs. Newer engineers design systems. Everyone reviews everyone's code.

Retention improved unexpectedly. We expected turnover to increase because engineers couldn't "get promoted." Instead, voluntary attrition decreased from 16% to 9%. In exit interviews, departing employees from the old system frequently cited "feeling stuck at my level" as a factor. Under the flat system, nobody feels stuck because there are no levels to be stuck at.

Hiring became easier. Our job postings say "Engineer" and list the problems we are solving, not the level requirements. Candidates self-select based on interest in the problems rather than matching their title to our ladder. We get applications from people who would never apply for a "Junior" or "Senior" posting because they don't know where they fit.

Common Objections

"How do engineers know they're growing?"

Through direct feedback in weekly check-ins and through the scope and complexity of the work they take on. Growth is visible in what you work on and how you work, not in a title change.

"How do engineers represent their seniority externally?"

On resumes, engineers describe their work and impact, which is more valuable than a title anyway. "Led the migration of 200M records from MySQL to Postgres with zero downtime" is more compelling than "Staff Engineer" to any competent hiring manager.

"Won't experienced engineers feel devalued?"

Some did, initially. The ones who stayed discovered that their influence increased, not decreased. Without titles, authority flows to expertise and trust. Experienced engineers who are genuinely good at their jobs earn more influence in a flat structure than in a titled one, because their authority comes from demonstrated competence rather than a label.

"What about engineers who want to become managers?"

Management is a separate role, not a promotion. Engineers who want to manage can transition to people management. But they don't get a higher title; they get different responsibilities. This framing helps attract people who genuinely want to manage, not people who see management as the only path to higher compensation.

Conclusion

Job titles exist because we copied organizational structures from the military and manufacturing — industries where hierarchy serves a clear purpose. In knowledge work, hierarchy creates friction. It slows decisions, distorts incentives, and substitutes credential for competence.

Pay people fairly based on their impact. Let expertise, not title, determine influence. Spend your organizational energy on solving problems instead of administering levels. Your best engineers don't care about titles. They care about doing meaningful work with talented people.