Skip to content
CAMPUX Cloud Bootcamp
Field notes · Careers
What engineers make $200,000 a year

Which engineers make $200k and up — and what it actually takes

By Captain O11 min readUpdated Sep 2026

Salary content on the internet has a fantasy problem. Half of it is written to sell you a course, and it quietly swaps total compensation for salary, the top of the range for the middle, and the winners for the field. This is the other kind of money post: where $200k is genuinely normal, where $500k actually happens, why $1M a year is almost never a paycheck — and what moves a real person up the ladder.

New to cloud? CAMPUX is a free, build-first course. Start here →

Senior engineers at large tech companies routinely clear $200,000 a year in total compensation — software, cloud infrastructure, security, and machine learning most reliably — but that figure includes stock and bonus rather than salary alone, and most engineers in the US never cross it. Getting there is usually a company change, not a title change.

I want to be straight with you about what this article is and is not. I am a working cloud engineer, not a compensation researcher. The numbers below are ranges pulled from two named sources — Levels.fyi, which aggregates self-reported total compensation at tech companies, and the US Bureau of Labor Statistics OEWS survey, which covers the whole labor market — both as of 2026. Self-reported data skews toward big tech and toward people proud of their number. Government data lags reality by a year or more. So treat every specific figure with suspicion and the direction as settled: the tiers below are real, the boundaries are fuzzy.

First, the sleight of hand: total comp is not salary

When someone says an engineer "makes $350k," they are almost never describing a salary. Big-tech pay has three parts: base salary (the paycheck), bonus (typically 10–20% of base), and equity (stock that vests over years). At senior levels the base is usually $160k–$220k even at the highest payers — the rest is stock. That distinction matters for two reasons. Stock moves: a package "worth" $400k when you signed can be worth $300k or $550k a year later depending on the share price. And stock is what makes the very high numbers possible at all — no company hands out $500k in cash. Every figure in this article is total compensation unless I say otherwise, and I will keep flagging it, because the swap between "comp" and "salary" is where most salary-content dishonesty lives.

Where $200k a year is normal

There is a real tier of the market where $200k total comp is unremarkable — the standard offer, not the exceptional one. It is narrower than the internet suggests.

Role and tierTypical total comp (not base)Source, dated
Software developer, US median (all employers)Low $130,000sBLS OEWS, latest release as of 2026
Senior software engineer, big tech$250k–$450kLevels.fyi, as of 2026
Senior cloud / infrastructure engineer, big tech$220k–$400kLevels.fyi, as of 2026
Senior security engineer, big tech$220k–$400kLevels.fyi, as of 2026
Senior ML engineer, big tech / AI labs$280k–$550kLevels.fyi, as of 2026
Staff engineer, mid-size tech$200k–$350kLevels.fyi, as of 2026
Staff / principal, top-paying companies$450k–$700k+ (≈half equity)Levels.fyi, as of 2026
Quant developer, top trading firms$300k–$600k+Levels.fyi and firm reports, as of 2026

Read that first row again before the rest of the table goes to your head. The median US software developer — across every employer, not just tech — earns in the low $130,000s per the BLS. Everything below that row describes a minority of the profession. It is a large, real minority you can join, but it is not the average outcome, and anyone presenting it as the average is selling something.

Where $500,000 happens

Go up two levels and narrow the company list, and you find the $500k tier. Staff and principal engineers at the top-paying companies report total comp of roughly $450k–$700k on Levels.fyi as of 2026. ML engineers and researchers at AI labs are in the same range or above it right now, though I would not bet a career plan on that market staying this hot. Senior quant developers and researchers at top trading firms get there through profit-linked bonuses instead of equity.

Two things about this tier that the fantasy content skips. First, at $500k roughly half the package is equity, so your actual annual income rides the stock market — people at this level have watched their "comp" drop $150k in a bad year without anyone touching their salary. Second, staff and principal are not senior-with-more-years. They are different jobs: setting direction across teams, being accountable for systems you do not personally build, spending more time writing documents and aligning people than writing code. Plenty of excellent senior engineers look at that job and decline it, reasonably.

Why $1,000,000 a year is almost never salary

Now the question behind the question. People who clear $1M a year in tech essentially never do it through wages. They do it three ways:

As of 2026 there are credible reports of seven-figure packages for a small number of senior AI researchers, and those offers are real — and they are also equity-heavy, concentrated in a few hundred people worldwide, and a symptom of a hiring frenzy rather than a durable rung on a ladder. If someone is selling you a roadmap to $1M a year, the roadmap is the product and you are the revenue.

Nobody pays a million-dollar salary. Seven figures is equity that appreciated, a company you started, or a fund you made money for.

The mechanics people miss

Here is the part that took me embarrassingly long to understand, and that no compensation table shows.

The jump from $150k to $300k is a company change, not a title change

Pay bands differ by a factor of two for the same work. A senior engineer at a regional insurance company and a senior engineer at a big tech company can have near-identical jobs — and the second one earns double, because the bands are set by what each company's market position lets it pay, not by the difficulty of the work. This means the highest-return career move is usually not grinding for a promotion inside your current band; it is moving your existing level into a higher-paying company's band. Annual raises of 3–5% will never re-price you across that gap. An offer will.

Equity is the multiplier, and it is volatile

Everything above $250k or so is mostly stock, which means the difference between tiers is largely how much equity a company grants and what its stock does after. That cuts both ways: refreshed grants at a rising company quietly push people past numbers they never negotiated, and a falling stock does the reverse. If you compare offers by base salary alone you will systematically pick the wrong one; if you count equity at its most optimistic value you will feel robbed in two years. Value it at today's price, hedge it in your head.

Location and cost-of-labor localization

Most large companies pay by where you live, not where the company is. The same level in the Bay Area, in Texas, and in Lisbon maps to three different bands. Remote roles at US-tier pay exist and are fiercely competed for. None of this is fair, exactly — it is how labor markets price things, and it is worth knowing before you anchor on a number a Bay Area engineer posted.

The realistic cloud path through all of this

Since this is a cloud engineering site, here is where cloud sits honestly in the picture, with the same hedges as everything above — ranges from Levels.fyi and BLS OEWS as of 2026, direction settled, specific numbers mobile.

So cloud engineering reaches every tier in this article short of the seven-figure fantasy, and the fork in the road is the same one: at senior, staying in a median band or moving into a big-tech band is worth more than any certification you could add. The fuller picture — including how cloud compares to adjacent roles — is in do cloud engineers get paid well, and if part of your question is whether this field survives the AI wave long enough to pay off, I took that on separately in which jobs will survive AI.

The honest gap

Most engineers never cross $200k, and they have good careers anyway. The distribution is lumpy: a minority of companies pay the numbers this article is about, and averages published by anyone hide that. Salary content also has a survivorship problem — the person posting a $420k package on Levels.fyi is real, and so are the thousands of engineers at $115k who never post anywhere. Both are outcomes of the same career. $130k in a mid-cost city with reasonable hours is a genuinely good life, and treating it as failure because a screenshot went viral is how people make bad decisions. Chase the higher tiers if you want them — they are reachable — but know what the base rates are while you do it.

What actually moves someone up

If the tiers are real and the fantasy is dead, what is left is mechanics. In rough order of return-on-effort — and notice what is not on this list:

  1. Scope. Pay follows the size of the problem you are trusted with. An engineer who owns a service earns senior money; one who owns a platform other teams depend on earns staff money. Growing scope inside your job — volunteering for the migration nobody wants, owning the incident review — is what makes the next tier's interviews passable.
  2. Company tier. Covered above, and worth repeating because it dominates everything else: the same skills sell for double in the right band. Interviewing at higher-paying companies is uncomfortable and has a real failure rate, and it is still the highest-return move available to most people.
  3. Negotiation at offer time. Offer time is nearly the only moment your pay is genuinely negotiable, and equity is usually more flexible than base. A single calm counter — "I have a competing number at X, can you improve the equity?" — routinely moves offers by amounts a year of exceptional performance would not.
  4. Switching at the right moments. The pattern that shows up over and over in comp data: people who changed companies every 2–4 years early in their careers out-earn people who stayed a decade, because each switch was a re-pricing. This flattens out at senior-plus, where staying long enough to build scope starts to pay better than hopping.
  5. Certification count is not on this list. Certifications get you interviews at the early tiers — I hold 14-plus and they mattered for getting in the door. Nobody at any company I have worked for was paid more for having more of them. Past entry level, evidence you have run real infrastructure beats a badge wall every time.

That last point is why the job-search end of this matters more than the studying end. The skills open the door to the tier; the search-and-negotiate mechanics decide which band you land in. We built a free class on exactly that stage — landing the job — covering how hiring actually filters people and what to do at offer time, and the free exam practice is there for the credential step before it. If you want the whole path compressed with an instructor and a cohort instead of assembled alone, that is what the live bootcamp is for — but the free material will take you a long way first.

Questions people also ask

What engineers make $200,000 a year?

Senior software engineers, cloud infrastructure engineers, security engineers, and machine learning engineers at large tech companies commonly earn $200,000 or more in total compensation, per Levels.fyi as of 2026. So do staff-level engineers at mid-size tech companies and specialists in niches like quant development. That number almost always includes stock and bonus — base salary alone at these levels usually sits between $150,000 and $200,000. Outside big tech, $200,000 is uncommon: the BLS OEWS median for software developers is in the low $130,000s in its latest release.

Which engineer makes $500,000 a year?

Staff and principal engineers at the top-paying tech companies — the well-known majors and a handful of high-paying private companies — report total compensation of roughly $450,000 to $700,000 on Levels.fyi as of 2026, and machine learning engineers at AI labs and quant developers at top trading firms can land in the same territory. The catch is that at $500,000, roughly half the number is usually equity, which moves with the stock price. Almost nobody is paid a $500,000 salary; they are paid around $200,000 to $250,000 in cash plus stock that happens to be worth the rest this year.

What jobs make $1,000,000 per year?

Essentially no engineering job pays a $1,000,000 salary. The people who clear a million a year as engineers get there through equity appreciation — early employees whose stock grew several times over, founders whose companies succeeded — or through quant finance, where senior traders and researchers at top funds can reach seven figures in a strong year through profit-linked bonuses. As of 2026 there are reports of seven-figure packages for a small number of senior AI researchers, but those are rare, equity-heavy, and not a career plan. If a course or influencer promises you a path to $1M a year, treat it as marketing.

Do cloud engineers make $200k?

Senior cloud and infrastructure engineers at large tech companies do — Levels.fyi shows senior-level total compensation of roughly $220,000 to $400,000 at the majors as of 2026. At a typical non-tech company, a senior cloud engineer is more likely to earn $140,000 to $200,000, and entry-level roles start around $70,000 to $110,000. So $200k is a real, reachable number in cloud, but it usually requires reaching senior level and moving to a company whose pay bands go that high, not just accumulating years or certifications.

Do you have to work at a big tech company to make $200,000 as an engineer?

Mostly, yes — or at a company that pays like one. The single biggest driver of engineering pay is not skill or title, it is which company's pay bands you sit in: the same senior work can pay $150,000 at one employer and $300,000 at another, per Levels.fyi data as of 2026. High-paying startups, trading firms, and some remote-first companies also cross $200,000. What rarely gets you there is staying put at a median-paying employer and waiting for raises, because annual raises almost never re-price you into a different tier.

Your next class · free
You've read the idea. Class 42 — Landing the Job is where you build it, hands-on — no account needed.Start Class 42 →
Captain O
Founder & instructor · CAMPUX Cloud Engineering Bootcamp
Keep reading — the money set
Free path to the interview: Class 42 — Landing the Job. Next note: Do cloud engineers get paid well? →