What Counts as Good Pay in 2026

Most pay advice starts and ends with a number, as if $70,000 or $100,000 were a finish line that means the same thing to everyone. It is not. The single most useful move you can make when you evaluate compensation is to stop treating pay as an absolute and start treating it as a position inside a distribution. The federal government publishes exactly the distribution you need. The U.S. Bureau of Labor Statistics runs the Occupational Employment and Wage Statistics program, which reports what real people in more than 800 occupations actually earn, broken into percentiles rather than a single misleading average. At Metaintro, the AI career platform we built around more than 50 million live job listings and 1.8M+ users, the pattern we see over and over is that workers who benchmark their pay against a real range negotiate and job-hunt from a completely different footing than workers who carry around a vague sense of what "good" should be. This guide turns that federal range into a judgment tool you can use on any number.

Why is "good pay" a relative number and not an absolute one?

Ask ten people what counts as good pay and you will get ten different answers, most of them anchored to whatever that person happens to earn or wishes they earned. That is the trap. A salary is not good or bad on its own. It is good or bad relative to three things you can actually measure: your occupation, your location, and the typical household around you.

Start with the occupation. According to the BLS Occupational Employment and Wage Statistics release, the median annual wage across all occupations was $49,500 (BLS OEWS May 2024 median annual wage for all occupations). That single number is nearly useless for judging your own pay, because it blends a cardiac surgeon and a dishwasher into one figure. What matters is the range for your specific line of work. Registered nurses had a median annual wage of $93,600 in May 2024, with the lowest tenth earning under $66,030 and the highest tenth earning above $135,320. Software developers had a median of $133,080, ranging from below $79,850 at the tenth percentile to above $211,450 at the ninetieth. Customer service representatives had a median hourly wage of $20.59. A $70,000 salary is below median for a nurse, well above median for a customer service rep, and a fraction of what a senior developer commands. Same number, three completely different verdicts.

Then layer in location. A dollar in one metro is not a dollar in another. The U.S. Census Bureau reports that real median household income was $83,730 in 2024, not statistically different from 2023, but that national figure hides enormous variation. The Pew Research Center defines the middle class as households earning two-thirds to double the median, adjusted for household size and local cost of living, which means the income that lands you comfortably in the middle in a lower-cost area might barely clear the lower bound in an expensive one. Across the roles we track at Metaintro, we consistently see the same title carry very different listed pay depending on the metro, and workers who ignore that geography make bad comparisons.

The takeaway is not complicated. Good pay is a coordinate, not a milestone. To judge any number you need to plot it against your occupation's range, your metro's cost of living, and the local median household income. Miss any one of those and you will either sell yourself short or feel poor at a number that should feel fine.

How do you benchmark your pay against your occupation's percentiles?

The single most powerful habit in this entire guide is learning to read your occupation's wage percentiles. A percentile tells you what share of workers in your job earn less than a given amount. If the tenth percentile for your role is $50,000, then only ten percent of people in that job earn less. If the ninetieth percentile is $120,000, then only ten percent earn more. Your salary's position inside that spread is the truest single measure of whether your pay is good for what you do.

Here is how to do it. Look up your occupation on the Occupational Outlook Handbook, which sits on top of the same OEWS wage data and gives you the median plus the tenth and ninetieth percentile for hundreds of jobs. The Handbook even publishes a short guide to using wage data during salary negotiations. Find your job, read the median, and read the two tails. Then place your own pay. Are you near the tenth percentile, at the median, or pushing the ninetieth? That single placement tells you more than any "is $X a good salary" search ever will.

Consider the before and after. Before: a marketing coordinator tells a friend she makes $70,000 and calls it "good money," full stop, with no reference point. After: she looks up her occupation, sees her role's median sits near her number, notes the ninetieth percentile is meaningfully higher, and realizes she is squarely mid-pack with real room to climb through a raise or a move. The number did not change. Her understanding of it, and her leverage, transformed completely. The second version knows exactly what argument to make when she asks for more, and she can back it with a federal source rather than a feeling.

A second before and after shows the danger of skipping this step. Before: a warehouse operations lead gets an offer of $62,000 and accepts on the spot because it is more than his current $58,000, a $4,000 bump that feels like a win. After: he checks his occupation's percentiles, discovers experienced leads in his field commonly sit ten to fifteen percent higher, and counters with data instead of gratitude. When you know the range, a raise that looked generous can reveal itself as a lowball, which is exactly the pattern we cover in how to spot underpaid roles and lowball offers. This is also the mechanic behind how to figure out your market rate, the number-crunching cousin of judging whether pay is good.

The percentile habit is also what keeps a big-sounding number honest. A $133,080 software developer salary sounds enormous, and it is above median for the role, but if you are actually operating at a senior level where the ninetieth percentile runs past $211,450, then that "high" salary is really a mid-range one dressed up by a scary-looking dollar sign. Judging pay means judging position, not magnitude. For the specific question of whether crossing into six-figure territory means what people think it means, we go deep in how much is six figures, really.

How does cost of living change whether a salary is actually good?

A salary is only as good as what it buys where you live. This is where a lot of otherwise smart people go wrong, because a large gross number in an expensive metro can leave you with less real breathing room than a modest one in an affordable place. Good pay has to survive contact with your actual rent, groceries, and taxes.

Take the classic before and after. Before: an engineer accepts a $180,000 offer in one of the most expensive metros in the country and assumes she has made it, because $180,000 is objectively a lot of money by national standards, well above the $83,730 median household income the Census Bureau reports. After: she runs the local cost math and discovers, as our own reporting on why a $180K tech salary no longer stretches in San Francisco lays out in detail, that housing and daily costs eat the headline number alive, leaving her feeling squeezed at a salary that would be luxurious almost anywhere else. The gross number was excellent. The real, cost-adjusted number was ordinary. Nothing about the paycheck told her that. Only the local comparison did.

Now run it the other direction, because the flip side is the more encouraging story. Before: a project manager in a mid-sized, lower-cost metro earns $78,000 and feels underpaid because a friend on the coast makes $120,000 and never lets him forget it. After: he compares each salary to its own local median household income and cost of living, and realizes his $78,000 clears his metro's median comfortably while his friend's $120,000 barely keeps pace with a far more punishing one. He is, in the terms that matter, the better-paid of the two. A lower number can be genuinely good pay, and a higher number can be quietly mediocre, once you correct for where the money is actually spent.

This is why remote and relocation decisions turn into pay decisions in disguise. If your role can be done from anywhere, moving from a high-cost metro to a lower-cost one can raise your real pay without changing your salary at all, a dynamic tangled up with the same forces we cover in why remote workers may face higher layoff risk and the top US cities for remote work in 2026. The practical rule is simple. Never evaluate a salary in a vacuum. Divide it, at least roughly, by the cost of living where you will spend it, and compare the adjusted figure to the local median. That is the only comparison that tells you the truth.

How do you compare your pay to median household income the right way?

The median household income is the single best sanity check for whether a salary is objectively decent, and almost nobody uses it correctly. The Census Bureau figure of $83,730 for 2024 is a household number, not an individual one, which trips people up constantly. A single person earning $83,730 is doing better relative to peers than a four-person household earning the same, because that one salary supports one person rather than four. Household size is not a footnote here. It changes the verdict.

Use the median as an anchor, then adjust. The Pew Research Center framework is the cleanest way to do it: households earning below two-thirds of the median are lower income, two-thirds to double is middle, and above double is upper, all adjusted for household size and local prices. Pew even offers an interactive income calculator that places your household given your metro and size. Running your number through that tool is one of the fastest ways to convert a raw salary into an honest verdict. It answers the real question, which is not "is this a big number" but "where does this put my household compared to everyone around me."

Pay pressure tracks the same shift in hiring. Lacey Kaelani, CEO of Metaintro, told People Managing People that "AI is not completely eliminating roles, but instead restructuring roles and therefore slowing hiring for some jobs." What counts as good pay depends on staying in the skills that hold their value as that restructuring plays out.

Here is the mistake to avoid, framed as a before and after. Before: a new graduate earning $55,000 as a single person compares herself to the $83,730 household median, concludes she is far behind, and feels demoralized. After: she recognizes that the household median blends dual-income households, adjusts for the fact that she is one earner supporting one person in a moderate-cost metro, and sees that her pay is a reasonable, on-track starting position rather than a failure. She stopped comparing an individual salary to a household number and started comparing like with like. The despair evaporated because the comparison was finally fair.

The reverse mistake is just as common and just as costly. A dual-earner household pulling $95,000 combined might feel comfortably middle class against the raw median, yet in a very high-cost metro, adjusted for two people and steep local prices, that same income can land at the lower edge of the local middle. The median is a starting line, not a destination. Anchor to it, then correct for household size, local cost, and how many people the income supports. Only then does the comparison mean anything, and only then can you say whether your pay is genuinely good or just numerically large.

What role do benefits, raises, and pay transparency play in a good number?

A salary is the headline, but it is not the whole story, and judging pay only by base is how people end up comparing incomparable offers. Two jobs at the same base can differ by thousands in real value once you count employer retirement contributions, health premiums, bonuses, equity, and paid time off. A number that looks slightly lower on paper can be the genuinely better-paid role once the full package is counted, which is exactly why we treat total compensation as its own skill in compare total compensation, not just salary.

Good pay is also a moving target, because wages and prices both drift. The BLS Employment Cost Index tracks how compensation changes over time, and a salary that was strong three years ago may have quietly slipped below market as the range moved up around it. This is why benchmarking is not a one-time act. Re-check your occupation's percentiles every year or two, and treat a stale salary as a signal, not a comfort. When the check reveals a gap, the fix is a documented conversation, which we script step by step in how to ask for a raise and, when it is a new offer on the table, in how to negotiate a job offer.

Pay transparency laws have made this dramatically easier than it was even a few years ago. Wage and hour rules sit with the U.S. Department of Labor, but disclosure mandates are largely a state matter, and according to the Society for Human Resource Management, there are now 14 state laws and seven local jurisdictions requiring some level of pay disclosure, which means many job postings now list a real salary range you can benchmark against before you ever apply. That is a gift for anyone trying to judge pay, and it changes what you are allowed to ask in an interview, a topic we unpack in pay transparency laws and what you can ask. Skills shift the range too. The PwC 2026 Global AI Jobs Barometer found a 62% wage premium for workers with AI skills, and Gallup reports AI use at work rose to 45% of employees in the third quarter of 2025, up from 40% the quarter before. In postings on our platform we see pay for roles that pair a domain with AI fluency cluster toward the higher end of their occupation's range, which is worth remembering when you judge whether your own number has room to grow. You can build that judgment directly with use AI to benchmark your salary.

Is the pay in front of you actually good, or just a big number?

Here is how to answer that question the next time a salary lands in front of you, whether it is your current pay or an offer you are weighing. Do not react to the size of the number. Run it through the framework instead.

First, place it in your occupation's range. Pull up your job on the Occupational Outlook Handbook or the underlying OEWS data, read the tenth percentile, median, and ninetieth percentile, and mark where your number falls. If you are below median for real experience, that is a flag no matter how large the number looks. Second, cost-adjust it. Compare the salary to the local median household income and the cost of living where you will actually spend it, using the Pew calculator to see which income tier it puts your household in. Third, count the whole package, not just base, and check whether the range has drifted since you last looked. Only after all three passes should you let yourself feel good or bad about the number.

The before and after here is the whole point of this guide. Before: you hear a salary, feel a jolt of excitement or disappointment based purely on its size, and decide on instinct. After: you plot it on three axes, occupation percentile, local cost, and household median, and reach a verdict you can defend with federal data. The emotional first reaction is almost always wrong, because it is anchored to the magnitude of the number rather than its position. The framework is almost always right, because it is anchored to reality.

Do this once and it becomes automatic. You will never again look at a paycheck and wonder vaguely whether it is good, because you will know exactly how to check. Good pay stops being a mystery and becomes a coordinate you can read. When you are ready to put a real number on your own market position and turn that verdict into a better job, start with the career pay pillar and let the platform surface roles that pay at the range you now know you deserve.

Related Articles

• How to Negotiate Your Salary
• Career Metrics for Earning Potential and Market Value
• Americans Demand Salary Transparency
• Could AI Raise Your Salary
• The $12,000 Pay Gap and Where It Hides in Your Offer
• 70% of Workers Got No Raise in Six Months
• Companies That Pay for Vacation, Benefits Worth Chasing
• High-Paying Jobs to Target in 2026
• How to Negotiate a Higher Offer in 2026
• Why a $180K Tech Salary No Longer Stretches in San Francisco
• The Top US Cities for Remote Work in 2026

People Also Asked

Q: What salary is considered "good" for one person versus a household?

A: There is no single number, which is why you compare like with like. A single earner should measure against individual pay for the occupation, not the household median. The Census Bureau reports a real median household income of $83,730 for 2024, but that blends dual-income homes, so a single person earning less than that can still be doing well. Run your household size and metro through the Pew income calculator today to see your actual income tier instead of guessing.

Q: How do I quickly check if my pay is fair for my job?

A: Look up your occupation on the BLS Occupational Outlook Handbook, read the tenth percentile, median, and ninetieth percentile, and mark where your salary falls. If you sit below the median with solid experience, you have a documented case for a raise. This five-minute check turns "I feel underpaid" into "I am at the 35th percentile for my role," which is a far stronger place to negotiate from.

Q: Does a high salary in an expensive city beat a lower one in a cheaper place?

A: Not automatically. Divide each salary by its local cost of living and compare the result to the local median household income before deciding. A large gross number can leave you with less real breathing room than a modest one, which is exactly what happens in high-cost metros. Cost-adjust first, then judge, so you are comparing purchasing power rather than headline dollars.

Wondering what you should earn? Metaintro tracks how roles get posted and paid in real time, so you can benchmark your number against the live market instead of guessing. Sign up to see what your target role pays and get matched to openings that fit.