NVIDIA Engineering Levels and Salary: Pay by Discipline, by Site, and Why Reported Figures Understate It

Because reported figures use grant value, meaning what the stock was worth on the day it was awarded, and NVIDIA's share price has appreciated so sharply that realised value has run well ahead of it for anyone hired before about 2025.

The gap is not small. An engineer whose four year grant was priced several years ago may be realising a multiple of the number attached to their level. That distorts every published NVIDIA salary table, including this one, and it is the single most important caveat to hold in mind when reading any of them.

AI frameworks and inference work sits at the top, followed closely by CUDA and compute library engineering. Both carry a meaningful premium over the site baseline because the pool of people who can do them well is tiny and every AI lab and hyperscaler is bidding for the same names.

Compiler and toolchain work sits just behind. What surprises people is where silicon work lands: RTL design, verification, and physical design all pay below the software baseline at the same IC level, despite being harder to hire for, because they are benchmarked against a semiconductor market that moves more slowly than the software one.

Yes. NVIDIA lists offices in Beijing, Shanghai, Shenzhen, and Guangzhou, and maintains engineering presence in mainland China. This is a genuine difference from Google, which withdrew from mainland China and has no engineering there.

It matters if you are comparing offers across the two, because a China based NVIDIA engineering role is a real thing in a way that a China based Google engineering role is not.

Israel, by a considerable margin. NVIDIA's presence there expanded enormously through the Mellanox acquisition and now spans Yokneam, Tel Aviv, Raanana, Beer Sheva, and Tel Hai, with networking as the historical core.

Israeli compensation is also the closest to United States levels of any NVIDIA location outside America, which reflects a local market where NVIDIA competes with the same companies it competes with in Santa Clara.

It rises steeply with level. At IC1 stock is under ten per cent of the package and base salary is almost the whole thing. By IC3 stock is around a third. By IC5 it is roughly half, and above that it dominates.

The bonus goes the other way and effectively vanishes. Reported bonuses at IC1 and IC2 are small but real, and from IC3 upward they fall close to zero as the money moves entirely into equity.

Hire date, more than performance. Two IC3 engineers doing identical work can be realising very different sums purely because one was granted stock at a much lower share price than the other.

This creates awkward dynamics that NVIDIA managers deal with constantly. Long tenured engineers can be difficult to motivate with a refresher that looks small against what is already vesting, while recent joiners see a package that behaves like a normal technology employer. Both are at the same level and both are being paid correctly by the company's own rules.

On grant value it is broadly comparable at most levels and stronger at the very top, where the IC7 median exceeds one million dollars.

On realised value over the past few years it has been substantially ahead, though that is a statement about the share price rather than about NVIDIA's pay policy. Anyone joining now is being granted at a much higher price than earlier cohorts, so the historical outperformance should not be treated as a forecast.

Yes, more than at many comparable companies, but the volume drops and the nature changes. An IC5 or IC6 is more likely to write the prototype that settles an argument about whether an approach works than to own ongoing feature delivery.

The domain helps here. Performance work rewards people who can still get their hands into a profiler, so NVIDIA senior engineers tend to retain deeper practical involvement than the equivalent level at a pure software company.

For compute, AI infrastructure, and library teams it is close to decisive, and it is the clearest single differentiator in a candidate pool. For driver, graphics, networking, and silicon roles it is useful context rather than a requirement.

If you do not have it and want those teams, demonstrable low level performance work in any context is the next best signal. What interviewers are testing is whether you reason about memory hierarchies and parallel execution instinctively, and that can be shown without a CUDA project on your resume.

Internal mobility is supported and moves in both directions happen regularly. Given the pay gap documented on this page, hardware to software is the more commonly attempted direction.

It is not automatic. A move usually needs a manager willing to take the ramp cost and evidence that you have been building the relevant skills before you asked. Engineers who make the move successfully have generally been contributing to software adjacent work for a while first.

No. NVIDIA publishes no level to title map, no rubric, and no compensation bands. United States job postings in several states carry legally required base salary ranges, which is the only official figure available and covers base alone.

Everything else here is crowdsourced compensation reporting and community accounts, cross checked between sources. Discipline level figures in particular are expressed as relative positioning rather than precise medians, because the underlying samples are too small to support precision.

Joining today means being granted at a much higher share price than earlier cohorts, so the extraordinary appreciation that defined recent years is not available to you in the same way. Your package will behave more like a conventional large technology employer.

That is not an argument against joining, but it is an argument against treating other people's outcomes as your expected outcome. Evaluate the offer on grant value and on whether you would be satisfied with it if the share price simply held steady.