Should you be paid per story point?
If you have spent any time as a software engineer, your first reaction to that question is probably to laugh.
Of course not. Story points are gameable. They are defined internally by each team, inflated quarter over quarter, sandbagged in planning sessions, weaponized in performance reviews. Pay engineers per story point and the whole system collapses inside a month.
You are right. And you are also missing the bigger point.
The story point is broken. But the underlying idea — paying engineers for delivered work rather than for time-in-seat — is not. The reason story points fail as a payment unit is that they are the wrong unit, not that the model itself is wrong. Once you fix the unit, everything downstream — your income, your hours, your autonomy, your relationship with your employer — changes more than you currently think it can.
This piece is for you, the engineer. Not your CTO. Not your VP. You.
The industry has spent the last year talking about outcome-based delivery as a transformation for buyers, for boards, for procurement teams. Almost nobody has stopped to ask the question that actually matters to the person who does the work: what does my career look like when the unit of payment changes?
The answer is more interesting than you've been told.
I. Why Story Points Failed — and What Replaces Them
The reason your team's story points have never been used to pay anyone is that they cannot be priced across organizational boundaries. Your team's "5-point story" is somebody else's "3-pointer" and somebody else's "8." The unit is internal, relative, and arbitrary. You cannot pay engineers in a currency that means something different at every company.
The fix is a unit that means the same thing across companies, teams, and engagements. Call it a Delivery Unit (DU). A calibrated, externally-defined chunk of accepted shipped work, scoped by complexity and acceptance criteria rather than by hours worked or by a single team's whims.
Think of it the way a kilowatt-hour works in electricity. One kilowatt-hour means exactly the same thing whether you buy it from a utility in Mumbai, a solar farm in California, or a generator in Lagos. The pricing varies; the unit does not. Without a stable unit, there is no market for the thing — only haggling.
The DU does for engineering what the kilowatt-hour did for electricity: it creates a portable unit you can earn, spend, compare, and price. Your delivered work at company A is worth exactly the same as the same work at company B. You can be paid for the work itself, not for the political negotiation of how that work was estimated.
This is the change everything else hangs on. Once the unit is stable, the rest of the transformation becomes operational.
Let us walk through what that operational transformation actually looks like — for you.
II. The Math of Your Income
Here is the part you actually care about.
Take a mid-level software engineer in 2026. Five to seven years of experience. Solid generalist, deepening in one area — distributed systems, data engineering, front-end performance, whatever. Currently earning, at a respectable US tech company, around $180K base, $20K–$30K in bonus and equity, plus benefits — call it $230K total compensation.
Now suppose the same engineer is paid per DU instead.
In the calibrated DU market, the engineer-side payout is roughly $100 per delivered, accepted DU. A working engineer on a well-scoped backlog ships somewhere between 200 and 300 DUs per month, depending on complexity tier and specialization.
Run the math. At the low end: 200 DUs × $100 × 12 = $240,000 per year. At the high end: 300 × $100 × 12 = $360,000. For specialists shipping high-complexity-tier DUs, the per-unit payout rises, and so does the annual figure.
Compared to the FTE equivalent at the same experience level (~$230K total compensation), the gross is 30–50% higher for mid-level engineers, and the delta widens for seniors and specialists.
Three things produce that gap.
One: you are no longer paying for the overhead of being one company's employee. HR, recruiting, real estate, management layers, internal political theater, the entire scaffolding of a 5,000-person engineering org — all of it gets stripped out of your effective hourly rate. You used to pay for it implicitly through depressed compensation. You no longer do.
Two: you are working at higher utilization on the work that actually matters. FTE engineers spend 35–45% of their week on meetings, status updates, performance review cycles, internal mobility politics, and the slow drag of corporate process. DU engineers spend that time shipping. The hours you currently bill at one effective rate become hours you bill at a meaningfully higher one, because the unit being paid for is shipped, not just present.
Three: portfolio pricing rewards quality. When your work history is portable — every accepted DU is verifiable across the market — engineers who ship well command a premium they could never extract from a single employer. The salary band that capped you at $200K dissolves when the market can directly observe your output.
The income increase is real.
It is also not the most interesting thing.
III. What Your Week Actually Looks Like
If the math is the surface change, the lived experience underneath is bigger.
A typical week as a DU-paid engineer working through a Virtual Delivery Center looks roughly like this:
You wake up Monday morning and check your DU backlog across three clients. You have committed to roughly 14 DUs this week, distributed across two product features at one client, a refactor sprint at the second, and a performance investigation at the third.
You attend exactly one synchronous meeting that week: a 30-minute pod standup with the four other engineers at your VDC who share part of this backlog. The clients do not run standups for you. They run async acceptance reviews against the DUs you submit.
The rest of the week is deep work. You ship. You submit. You get acceptances or revision requests. You ship again. By Friday afternoon you have delivered 13 of 14 committed DUs, plus an unscheduled one that came in as a P0 from one of the clients.
You did not write a self-evaluation. You did not sit through a sprint retro about another team's interpersonal dynamics. You did not have a coffee chat with a skip-level manager about your career path. You did not get pulled into a meeting whose only purpose was to summarize the meeting that preceded it.
You did not have a manager.
You had a delivery pod. You had clients with backlogs. You had acceptance criteria. You had work that was either shipped or not shipped, accepted or not accepted, paid for or not paid for.
For some engineers, this is heaven. For others, it is terrifying. We will get to who is which in a moment. But the day-to-day reality is concrete: the unit of your work life shifts from time spent in proximity to work delivered and accepted. Everything else flows from that.
IV. The Honest Fears
It would be dishonest to write this piece without engaging the things you are right now worried about. Here are the six biggest — and honest answers.
"My income will be volatile." Yes — if you have one client. No — if you have three to five. Portfolio diversification has solved this problem in adjacent industries for a hundred years. A partner at a law firm, a fractional CFO, a top freelance designer — none of them are paid by a single client, and none of them have wildly volatile income. Their workflow is structured around concurrent engagements, so that the trough in any one client is absorbed by the others. The math is straightforward: lose one of five clients and your income drops 20% for the month it takes to replace them, not 100% forever.
"What about benefits, health insurance, retirement?" A VDC operates as an employer of record. The standard model is that the VDC carries health insurance, retirement, parental leave, and the other benefits you currently get from your FTE — funded out of the platform fee charged against your DU revenue. You retain employment status. You retain benefits. You change what you are paid for, not whether you are employed.
"How do I get promoted? How does my career grow?" Your portfolio is the new ladder. Today, your "career growth" is mostly a function of internal political navigation at one company — who you know, whose work gets matched to yours for visibility, whether your manager is willing to advocate for your promotion to her manager. In a DU model, your career is your visible work history: every accepted DU at every client, verifiable, portable, building. The mid-level engineer who has shipped 600 accepted DUs across five clients has a stronger resume than the senior engineer at one FAANG who has shipped two flagship features in three years. Mastery compounds — and it compounds across clients, rather than being trapped behind one company's internal review process.
"What if I'm laid off from a client?" You are not. Layoffs are an artifact of FTE structure — they happen when one company over-hires and corrects. In a DU model, clients adjust their backlog, not their headcount. If a client reduces DU consumption from 200 per month to 100 per month, you ship 100 fewer DUs to them and pick up the difference elsewhere. The transition is days, not months. There is no layoff event. There is no severance. There is just a smooth adjustment in the mix of your client portfolio.
"What happens to my identity? 'I work at Google' meant something." This one is honest. It is real. For a generation of engineers, the company brand was the primary career signal — to friends, to family, to the next employer, to dating apps. That changes. The brand you build in a DU world is yours: your portfolio, your reputation, your acceptance history, the specific work you have shipped. Some engineers find this liberating. Others find it disorienting. There is no universal answer. But it is worth noting that every other knowledge profession that has worked this way — law, consulting, design, medicine in private practice — has eventually evolved its own status markers that are not tied to a single employer. Engineering will too.
"I'm a junior engineer. This sounds great for seniors. What about me?" This is the most honest concern of all, and the answer is: the DU model in 2026 is built for mid and senior engineers first. The juniors come next. Ramp time, mentorship, the slow apprenticeship of learning a complex codebase — these are not yet well-served by pure DU economics. The transition for junior engineers will be slower and structurally different. Some VDCs will run apprenticeship tracks. Some traditional FTE roles will remain, at least for the first 2–5 years of a career. The honest forecast is that you will spend your first three years in a traditional FTE arrangement learning your craft, and then transition to the DU economy as a mid-level. This is roughly the same arc that medicine, law, and consulting have had for a century: an apprenticeship phase, then independent practice.
V. Who Wins, Who Loses, Who Has to Adapt
The DU economy is not uniformly good for every engineer. Be honest about who wins and who has to adapt.
Strong winners:
- Senior and staff-level engineers with deep specialization. The market can now price their depth directly, and their effective rate rises materially.
- Engineers in lower-cost geographies. DU pricing globalizes the market in a way FTE salaries never did. A senior engineer in Bangalore or Kraków earning at SF rates is not a fantasy in this model. It is the math.
- Engineers who currently moonlight or freelance. They have already informally accepted the multi-client structure. The DU economy formalizes what they already do.
- Engineers who hate office politics. The structural drag they currently absorb simply disappears.
- Engineers who can do both — write specs and execute. The new full-stack person.
Has to adapt:
- Engineers whose value to a company is primarily proximity and availability — "the senior engineer who knows where all the bodies are buried." This is real value, but it is hard to price in DUs. These engineers will need to convert their tribal knowledge into shippable specifications, or stay in core FTE roles.
- Engineers in deep people-management positions. Management as such is not DU-able; the management function moves into the small FTE core that every company will retain. Engineers who want to manage will need to choose: stay in the core, or transition back to individual contribution.
- Engineers whose status game depends on FAANG branding. They will have to build identity around the work itself, not the employer's logo. Some will love this. Some will struggle.
Loses, at least transitionally:
- Engineers in their first three to five years out of college. The apprenticeship structure has not yet been ported to the DU world. This will change, but slowly.
- Engineers whose career strategy was internal mobility at one giant company over thirty years. This was always a slow strategy; it is now also a fragile one.
VI. What To Do This Year
If reading this piece has made you curious — or anxious — about whether you should make a move, here is the honest playbook.
Do not quit your FTE. Not yet. The model is mature enough to commit to as a primary mode of work, but the transition is best done gradually. Quitting outright is the single most common mistake engineers make when they first hear about this model.
Pilot it on your evenings and weekends. Join a VDC's roster for moonlight work and ship 5–10 DUs per month outside of your FTE role. Use this to learn the rhythm: how to negotiate scope, how to write to acceptance criteria, how to manage two or three client backlogs at once. The skills are learnable but take a few months to absorb.
Build your portfolio deliberately. Every accepted DU is a line on your new resume. Within twelve months you should have 50–100 accepted DUs from multiple clients. That portfolio becomes your primary career artifact — more valuable than your current LinkedIn title, more durable than your current job offer.
Learn to write specifications. This is the dual skill of the DU world: not just executing well, but specifying well. The engineers who can do both — write a clean spec for a client, then execute against it — will be the most valuable. Spend an hour a week practicing the discipline of writing acceptance criteria for the work you are doing in your day job. The skill compounds.
Specialize in something cleanly DU-able. Not every kind of engineering work decomposes neatly into shippable units. Pure research, very-long-cycle infrastructure work, deeply collaborative team-systems work — these are harder to scope as DUs. If you want to live in this world, lean into work with clear inputs, clear outputs, and clear acceptance criteria. Backend services, data pipelines, integration work, application features, focused refactors, performance investigations — these all decompose cleanly.
Find your VDC early. The platforms that mediate this market are forming now. The engineers who join in the first 18–24 months will build reputation, get the best backlogs, and accumulate portfolio while the supply side is still thin. The engineers who wait until the market is crowded will be competing against established portfolios from day one.
VII. The Decade Ahead, For You
For most of the last thirty years, the trajectory of an engineering career has been roughly fixed.
You graduated. You joined a company. You moved up an internal ladder you mostly could not see. Your compensation was set by salary bands you could not negotiate against from a position of strength, because you only had one employer at a time. Your career growth was a function of which managers liked you, which projects you got staffed on, and whether your annual review was written by someone willing to fight for your promotion.
That arrangement was the product of a specific economic moment — the moment when engineering work could not be cleanly priced across organizational boundaries. As long as the unit of work was time, every engineer was effectively in a one-buyer market: their own employer.
That moment is ending.
The DU economy is not the end of engineering careers. It is the end of the single-buyer market for them.
For the first time in three decades, the engineer is becoming the primary economic agent of their own career. You will be paid for what you actually produce. You will work on what you actually find interesting. You will keep the upside of your skill, your taste, your depth, your portfolio.
The engineer who figures this out first will earn more, learn faster, and answer to fewer people than any engineer of the FTE generation that came before them.
The story point was the wrong unit.
The Delivery Unit is the right one.
And on the other side of that unit change is a version of your career that you are going to want.