Can You Get Fired for Asking for a Raise? | HireFlow

9 min read

You've rehearsed it in the shower and you still haven't booked the meeting. The question underneath the delay usually isn't how much should I ask for. It's quieter than that: can you get fired for asking for a raise, and is this the thing that puts your name on a list?

Here's the straight version. In most of the US you can legally be let go for almost any reason, so technically yes. But that isn't what usually happens, and it isn't what you should plan around. The realistic risks are smaller and more manageable, and they change depending on how you frame the ask.

If part of your nervousness is that you'd have no backup if it went badly, fix that first. Run your resume through the free ATS resume checker so you know the file is ready before you walk into any conversation about money. A current resume changes how the meeting feels.

Can you get fired for asking for a raise? The legal answer

Every US state except Montana runs on at-will employment. That means either side can end the relationship at any time, for any reason that isn't specifically illegal, with no notice required.

So the technical answer is yes. Asking for more money is not, by itself, a protected act that shields your job.

But read that sentence carefully, because it cuts both ways. At-will also means your employer already could have let you go last Tuesday for wearing the wrong shoes. The ask doesn't create a power they lacked. It just makes you newly aware of one.

What this is not: a promise that nothing bad can happen, and not legal advice. State law varies, union contracts and written employment agreements override the default, and an employment attorney in your state is the right call if you think something has already gone wrong.

What is actually protected

Three things move a pay conversation from "at-will" into territory where the law has something to say.

Talking about pay with coworkers

Under the National Labor Relations Act, most private-sector employees can discuss wages and working conditions with each other. That protection applies whether or not there's a union. A policy telling you never to discuss salary with colleagues is, for many workers, unenforceable.

This matters because "I found out I'm paid less than the person doing my job" is one of the most common reasons people ask in the first place.

Raising a pay gap tied to who you are

If the gap you're pointing at lines up with race, sex, age, disability, religion, or national origin, you've moved into anti-discrimination law. The Equal Pay Act and Title VII both live here. Retaliation for raising that concern in good faith is separately illegal, even if the underlying claim doesn't hold up.

Asking for money you are already owed

A raise and unpaid wages are different animals. Unpaid overtime, missing final paychecks, or hours worked off the clock fall under the Fair Labor Standards Act, and complaints about them carry retaliation protection. If that's your situation, don't frame it as a raise. It isn't one.

I've sat on the hiring side of enough of these to notice a pattern: the people who get into trouble rarely got there by asking. They got there by asking in a way that read as an ultimatum, then having nothing to fall back on.

The risks that are actually real

Termination is the fear. It's rarely the outcome. These are the things that actually happen, in rough order of how often you'll meet them.

• A soft no with no date. "Let's revisit next cycle." The most common answer, and the one that costs you a year if you accept it without pinning a date.
• Being read as a flight risk. Some managers respond by quietly routing the interesting work elsewhere. This is the real cost, and it is almost always triggered by hinting at other offers you don't have.
• A counter that isn't money. A title, a course budget, a day of remote. Fine if you wanted those. A problem if you accept them and the number never moves.
• Getting fired. Uncommon, and when it happens it usually follows an ask delivered as a threat, or lands on someone whose performance was already under review.

Sounds manageable, right? It mostly is. The failure mode isn't the ask. It's asking with nothing behind it.

How to ask so it stays about money

Step 1: Separate the two possible conversations

Decide which one you're having before you book anything. My job grew and my pay didn't is a scope conversation. I'm paid below market is a benchmark conversation. They need different evidence, and mixing them weakens both.

Step 2: Write the scope list

Open a blank document. List what you own now that you didn't own twelve months ago. Put a number and a date on each line. Not adjectives.

Take a mid-level operations coordinator who writes this first:

"I've taken on a lot more responsibility this year and I've been a real team player."

Same person, rewritten so a manager can act on it:

"Since March I've run vendor onboarding for all 14 suppliers after Dana left — that was a separate role. Cycle time went from 9 days to 4. I'm also the approver on purchase orders under $10k, which wasn't in my job description."

The second version isn't bragging. It's a job description your manager can take to their own boss without doing extra homework, and that is the entire trick.

Step 3: Book it properly

Send a calendar invite for 30 minutes. Title it something plain like "comp check-in." No ambush, no Friday afternoon, and not immediately after a bad quarter.

Step 4: Ask, then stop talking

Give the scope list, give the number, then be quiet. Most people talk themselves down in the silence — offering a smaller figure before anyone has answered the first one.

A line that works:

"Based on the vendor work and the approval authority, I'd like to move to $X. What would it take to get there?"

"What would it take" is doing real work in that sentence. It turns a yes-or-no into a list of conditions, which is much harder to end with "not right now."

A second example: the benchmark case

The scope argument only works if your job actually grew. Plenty of people are simply underpaid for the job they were hired to do, and that needs different evidence.

Take a support specialist three years into the same role. The weak version:

"I looked online and it seems like people in my role make more than I do."

The version a manager can escalate:

"For senior support specialists in this metro, the postings I'm seeing from comparable companies land between $X and $Y. I'm at $Z. I've been in the role three years, I handle the escalation queue, and I train new hires. I'd like to move into that band."

Use live job postings for the range, not a salary-site average. Postings are what your employer would have to pay to replace you this month, and that is the number that moves budgets.

Step 5: Get the recap in writing

Same day, send a short email: what you asked for, what was said, any date given. Friendly, three sentences. If the answer was "next cycle," the email is what stops next cycle from becoming next year.

Copy this, change the brackets, send it the same day:

{`Subject: Following up on today's comp conversation

Hi [Manager],

Thanks for making time today. To recap what I asked: moving from
[current] to [target], based on [scope or benchmark].

My understanding is [what they said — e.g. "you'll raise it with
Finance and we'll revisit in the March cycle"]. Let me know if
I've got that wrong.

Happy to put together anything that helps make the case.

[Your name]`}

Two things that email does. It creates a dated record, and it quietly converts a vague "we'll see" into a stated commitment your manager now has in their inbox.

Edge case: your company has formal comp cycles

Some employers only move salaries in a fixed window, and your manager genuinely cannot approve anything in June. Ask when the window opens and what decisions get made before it — budgets are usually set weeks earlier. The useful ask becomes "what do you need from me before you submit?" rather than a number in the wrong month.

Edge case: you're on a performance plan

Don't ask yet. A raise request during an active PIP reads as a misread of the room and gives a manager who is already documenting you something else to document. Clear the plan first.

Edge case: you actually do have another offer

Then you're not asking for a raise, you're negotiating a counter — different conversation with different rules. Our guide on how to counter a job offer covers that. Only mention a competing offer if you are genuinely willing to take it.

Mistakes that turn a raise talk into a problem

• Bluffing about an offer. Managers call bluffs more often than people expect, and some start planning for your exit either way.
• Using personal expenses as the reason. Rent going up is real, and it is not a business case. It puts your manager in the role of solving your budget.
• Naming a specific coworker's salary. Discussing pay is protected; putting a colleague's exact number on the table in a meeting still tends to shift the conversation onto them instead of you.
• Asking with no number. "I'd like to talk about compensation" and then waiting. You've handed the anchor to the other side.
• Treating a no as the end. A no with conditions is a roadmap. Ask what would need to be true, and when you'd revisit.

Telling a real no from a stalling no

Most people hear "not right now" and stop. But the two kinds of no need completely different follow-ups, and you can tell them apart in the meeting.

A real no comes with a mechanism. "Bands are set at the director level and yours is capped at $X until you move up a level." That is information you can act on — it tells you the money is behind a promotion, so the next conversation is about scope and title, not salary.

A stalling no comes with a feeling. "Now's not a great time, let's circle back." No mechanism, no date, no condition.

That is not a decision. It is a deferral, and it will repeat unless you convert it.

Convert it with one question, asked calmly, right then:

"Understood. What specifically would need to be true for this to be a yes, and when should we look at it again?"

If you get a condition and a date, you have a plan. If you get another feeling, you have your answer about this employer — and that is worth knowing before you spend another year waiting for a cycle that never opens.

Have a backup before you have the meeting

Confidence in this conversation comes from options. Not from a script.

Before you book anything, get your resume into a state where you could apply this week if you wanted to. Upload it to the free ATS resume checker and look at two things: whether the file parses cleanly, and whether the scope you're about to describe to your manager actually appears on the page. If you've been doing vendor onboarding for six months and your resume still describes the job you were hired into, that's worth fixing regardless of how the meeting goes.

If the ask does go sideways and you start applying, the cover letter generator will build the letter around the expanded scope rather than your original title.

The short version

• Can you get fired for asking for a raise? Legally yes in at-will states, but it's uncommon and usually follows an ultimatum, not a request.
• Pay discussions with coworkers, discrimination concerns, and unpaid-wage complaints carry real legal protection.
• The ask that works is a scope list with numbers and dates, not a feeling about fairness.

Do one thing today: open a document and write down three duties you carry now that weren't yours a year ago. Put a number next to each. That list is the meeting.

And get the backup in place first. Check your resume for free so the conversation happens from a position of choice.

Read more

• How to ask for a raise — the full script and timing.
• How to ask for a promotion — when the answer is a title, not a number.
• How to counter a job offer — if you decide to look elsewhere.