How to Know If a Job Offer Is Fair

TL;DR

"Fair" means different things depending on the company type, your experience level, the geography, and what the role actually offers you beyond base salary.
Compare against market data for your specific role, level, and location. Not just general "software engineer" numbers.
Red flags include vague equity promises, a "we don't negotiate" stance on reasonable requests, and cliff-less vesting schedules.
A below-market base is not automatically a bad offer. Context matters. Growth opportunity, mentorship, and employer brand are real variables.
If you're unsure, ask. Most hiring managers expect you to ask questions about an offer.

Most people receiving their first engineering offer don't have a reference point. You've been in school, or in a bootcamp, and the hiring process has felt like a test you were either going to pass or fail. When the offer comes through, there's an instinct to just say yes before the company changes its mind.

That instinct is understandable. It's also how people end up underpaid for years.

Evaluating whether an offer is fair isn't complicated, but it requires you to do some work before you respond. The goal isn't to squeeze out every last dollar. The goal is to understand what you're agreeing to and whether it's reasonable given what the market actually pays.

Before you can evaluate anything, you need real compensation data. Researching salary before your interview gives you the baseline you need to make sense of any number you receive.

What "Fair" Actually Means

Fair is not a universal number. A $95,000 offer for a junior role in Austin is a different conversation than the same number in San Francisco. A $110,000 offer at a Series A startup with meaningful equity is a different conversation than the same number at a Fortune 500 company with no equity at all.

There are three dimensions to evaluate:

Fair relative to market rate. This is the most objective dimension. You can look up what companies in your area pay for comparable roles at comparable companies. Sites like Levels.fyi, Glassdoor, Blind, and LinkedIn Salary give you real data. The key is to be specific. "Software engineer" salaries vary by two or three times depending on level, location, and company type. Use filters. Look at new grads with 0-2 years of experience.

Fair given your experience level. If you have a strong internship track record, open-source contributions, or a compelling portfolio, you may be worth more than a candidate with the same degree but less practical experience. If you're a bootcamp grad applying to your first role, you may be priced at the lower end of the range until you have a track record. This isn't unfair — it's how hiring works. It just means you should calibrate expectations appropriately.

Fair given the opportunity. This is the hardest one to quantify but often the most important. A role that pays $15K less than market but gives you direct access to senior engineers, real ownership of significant features, and a brand name that opens doors later is often a better deal than a role that hits market rate but puts you in a poorly mentored, high-churn environment.

The Full Picture: It's Not Just Base Salary

Base salary gets most of the attention. But total compensation includes a lot more, and you need to understand the full offer before you can assess it.

Equity. At startups, this usually means options (the right to buy shares at a set price if the company grows). At public companies or late-stage startups, it's often RSUs (restricted stock units with real cash value at vesting). The difference matters enormously. Options at an early startup might be worth a lot, nothing, or somewhere in between. RSUs at a stable public company have more predictable value.

Vesting schedule. Most offers include a 4-year vest with a 1-year cliff. The cliff means you get zero equity if you leave in the first year. That's standard. What's not standard: no cliff at all (sounds nice but it's unusual and worth asking about), or a cliff longer than one year, which should raise questions.

Bonus. Some companies include a signing bonus, a performance bonus, or both. Signing bonuses are often one-time and may come with a repayment clause if you leave within 12-24 months. Performance bonuses vary. Ask whether they're discretionary or formula-based, and what the average payout actually is.

Benefits. Health insurance quality, 401(k) matching, remote flexibility, equipment stipends, learning budgets. These are real dollars. A $5,000 difference in base salary can evaporate if one company's benefits are significantly better than the other's.

Red Flags in an Offer

Some things in an offer warrant follow-up or caution. Not all of them are dealbreakers, but they're worth flagging before you sign.

Vague equity numbers with no specifics. "You'll receive options. We'll discuss the amount after you join" is not an offer. Any legitimate company can tell you the number of shares, the strike price, the current preferred share price, and the vesting schedule before you sign. If they can't or won't, that's a yellow flag.

"We don't negotiate" as a flat policy. Some companies have compressed pay bands and limited room to move. That's fine and they should say so. But a company that frames a reasonable counteroffer as an insult, or threatens to rescind an offer because you asked a question, is showing you something about their culture. You want to know that before you start.

Below-market base with a big promise of upside. "The base is low but our equity is going to be huge" is a claim that requires verification. Ask about the company's last valuation, what percentage of the company your grant represents, and the current preferred share price. If they can't answer those questions, the equity narrative isn't grounded in anything.

No cliff or unusual vesting terms. A standard 4-year vest with 1-year cliff is normal. Anything that deviates significantly from that deserves scrutiny.

When Below-Market Might Still Be Worth It

This is the part most advice skips. A below-market offer is not automatically a bad offer.

Think about what you're actually buying with a job. You're not just buying a salary. You're buying a set of conditions for the next 2-4 years of your career: the quality of mentorship you'll receive, the type of problems you'll work on, the brand name on your resume, and the relationships you'll build.

A role at a well-regarded company where you'll be mentored by experienced engineers, work on real production systems, and build a track record is often worth accepting even at 10-15% below market. That's especially true for first jobs, where the learning opportunity compounds into every future role.

The question to ask is: why is it below market?

If it's below market because the company genuinely can't pay more (early startup, nonprofit, funded but not profitable), and the other variables are strong, that's a legitimate tradeoff.

If it's below market because the company doesn't respect engineers' market value, that's different. You'll find out quickly whether that's the case based on how they respond when you bring up compensation at all.

How to Have the Conversation

Most candidates treat the offer conversation as a final exam. Either you get the number you want or you failed. That framing makes the conversation harder than it needs to be.

A better approach: treat it as information exchange. You have questions. They have answers. You can also make a case.

Start by saying thank you and that you're excited about the role. Then ask for time to review the offer in full. Most companies will give you 3-7 business days. Use that time to do the research, understand the full package, and decide what, if anything, you want to ask about.

If you're going to ask for more, be specific. "I was hoping the base could come closer to $X based on comparable roles I've seen for this level and location" is a real ask. "Can you do better?" is not.

If they say no, that's okay. You've learned something and you can decide whether to accept on the original terms. If they say yes, even partially, that's real money over your first year.

The conversation doesn't have to be adversarial. Most hiring managers have seen it before. What reads well: calm, specific, grounded in data, clearly interested in the role. What reads poorly: demanding, ultimatum-heavy, or making comparisons to companies you'd clearly rather work at.

If you want to prepare for that conversation properly, negotiating your first engineering offer covers the full playbook.

The Framework in Practice

When you get the offer, work through these steps before responding:

Look up comparable offers. Find 5-10 data points on Levels.fyi and LinkedIn for the same role type, company size, location, and experience level. What's the range? Where does this offer sit?
Calculate total comp. Add up base, expected equity value (conservatively), bonus, and the dollar value of meaningful benefits. Compare totals, not just bases.
Assess the non-financial factors. What do you know about the team, the manager, the mentorship culture, the growth path? If you don't know, ask before signing.
Decide what your actual question is. Is the base low? Is the equity vague? Is the vesting structure unusual? Be specific about what you want to clarify or ask about.
Make the call. Once you've done the work, you can make a decision with real information instead of guessing.

No offer is perfect. Every job involves tradeoffs. What you want to avoid is accepting something you'll regret in six months because you didn't ask the obvious questions when you had leverage.

After You Sign

Your first offer sets a baseline, but it doesn't lock you in forever. Once you're in the role and performing, there's a path to improving your compensation through performance reviews and promotions. Understanding how raises and promotions work at your first engineering job will help you think beyond the offer letter and toward what the first 2-3 years could actually look like.

The offer conversation is important. So is knowing what you're working toward once you've accepted.

If you want structured support evaluating offers and negotiating your first role, here's how the Globally Scoped program works.