How to ask for a raise and get a real answer

You've been handling the same workload for over a year, your manager keeps saying "let's circle back," and nothing circles back. That's the moment to ask for a raise directly, with a number attached, instead of hinting at it in a performance review and hoping someone notices. The way you phrase the ask determines whether you walk out with a plan or with another vague promise. Ask for a specific figure on a specific day, and ask what happens if the answer isn't yes today. That one addition turns a soft conversation into one with a deadline.

Ask for a number and a date, not a conversation

Most raise requests fail before they start because they're framed as feelings instead of numbers. "I feel like I deserve more" gives your manager nothing to act on. "I'd like to move from $58,000 to $64,000, effective next pay cycle" gives them a decision to make instead of a mood to manage. Pick your number before the meeting, not during it. If you're not sure where to land, look at what the role pays elsewhere in your market and anchor slightly above the middle of that range, since asking at the bottom just confirms a lowball and asking at the very top invites an immediate no.

A number also keeps the conversation shorter than it needs to be. If your manager has three people to see that week, the one who shows up with a figure and a date gets an answer first, simply because the ask already fits a spreadsheet instead of a feeling.

Set the date too. "Can we revisit this by the end of the month" is weak. "Can we have an answer by the 30th, before the next budget cycle closes" tells your manager the window is real and gives them a reason to act inside it rather than let the request drift into next quarter.

What the market actually pays, by job

Part of asking for the right number is knowing what the job actually pays elsewhere, not just what your current employer has settled into. Pay ranges vary enormously by role, and the spread inside a single job title can be just as wide as the gap between two different jobs. A Software Developer can earn anywhere from $82,460 to $214,670 depending on seniority and specialty, a range wider than the entire average salary of several other professions put together.

A few things jump out. The spread between the low and high end of a range tells you how much room a manager actually has to move. A healthcare manager's range stretches from $73,390 to $224,340, which means someone three years into the role and someone running an entire hospital department can carry the same job title while sitting on opposite ends of the pay scale. A stocker's range is far narrower, from $30,110 to $49,260, so the ceiling on what you can ask for inside that role is lower, but the sheer number of openings, 430,700 a year, gives you a different kind of advantage: if the raise doesn't come, another store down the street is hiring the same week.

Training length explains part of the gap too. A stocker can be trained in a few days to a few weeks, which is also why the role absorbs 430,700 openings a year without the market running dry. A plumber trains for 4 to 5 years through an apprenticeship, and that barrier to entry is exactly why the role's upper range reaches $108,420 even though the average sits at $63,800. The harder a role is to walk into, the more an employer loses by letting you walk out, and that difference should shape how firmly you push.

Openings per year change how hard you should push as well. A plumber role opens up 42,000 times a year against a far smaller pool of licensed tradespeople than the pool competing for stocker openings, which is part of why plumbing pay tends to climb faster for people who stay and build a reputation instead of switching shops every year. A business analyst, sitting at $101,860 on average with 94,100 openings a year, has both a wide range and a deep market, which is usually the best combination to have when you're asking for more.

Build your case from the tasks only you do

Generic praise doesn't move a budget. Specific tasks do. Before the meeting, write down the things you do that nobody else on the team does, or that nobody did before you took them on. A project manager who started covering meetings across time zones because the team went global has a stronger case than one who simply says they "work hard," because the time zone coverage is a fact a manager can point to when justifying the raise upward.

This matters even more in roles where the job itself is shifting. A business analyst or a corporate trainer working with tools that increasingly lean on automation can point to the parts of the job that still require judgment a system can't replicate, like reading a room during a training session or catching a flawed assumption in a dataset before it reaches a client. A corporate trainer carries an AI impact score of 6 out of 10, and a business analyst sits at the same 6, which means both roles are already absorbing automation faster than a plumber or a physical therapist, whose scores sit at 2. Naming that distinction out loud does two things: it shows you understand where the role is headed, and it reminds your manager why the human in the seat still matters.

If your job involves physical risk or irregular hours, say so plainly instead of assuming it's obvious. A line cook working weekend and holiday shifts, or a social services assistant covering evenings in a shelter, is absorbing a cost the paycheck doesn't always reflect. Naming the specific hours, not just "long hours," gives the ask weight. "I've covered every holiday shift since March" lands harder than "I work a lot of holidays." It also helps to know what the market already expects for roles like these: a line cook's work-life balance score sits at 4 out of 10, the lowest in this comparison, which is a fact worth putting on the table when the conversation turns to money instead of schedule.

Time it to the calendar, not your mood

Don't ask for a raise the day you're frustrated. Ask when the business has a reason to say yes. That usually means right after you finish a project that mattered, or right before the annual budget gets locked. It can also mean the moment your manager is building a case to leadership about what the team delivered, since your raise request fits naturally into that story. A systems analyst who just finished a system launch that avoided a costly outage has a natural opening that won't exist three months later when the memory has faded.

Growth projections also tell you something about timing, even if you never mention the number out loud. Every profession in the table above carries a job outlook score of 9, which puts them in a part of the job market expected to grow much faster than average, and companies feel that pressure before it shows up as a hiring freeze. A healthcare manager role is projected to grow 24.2 percent, the fastest expansion in this comparison, which means a hospital or clinic struggling to keep a manager in place has real incentive to close a pay gap quietly rather than restart a search. If your employer is struggling to fill open seats in your field, that's an advantage sitting in plain sight, and it's strongest right before a busy season starts, not after it.

AI impact scores hint at urgency too. A software developer carries an AI impact score of 7 out of 10, the highest in this comparison, while a plumber and a physical therapist sit at 2, the lowest. That gap doesn't mean developers should expect smaller raises, it means the case has to center on judgment and ownership a tool can't replace, while a plumber's case can lean more on scarcity and physical demand.

Avoid asking during a hiring freeze, right after layoffs, or in the same week your manager is dealing with a crisis. The timing doesn't have to be perfect, but it shouldn't actively work against you either.

Force a real answer instead of a maybe

The biggest mistake people make isn't asking for too much. It's accepting a non-answer. "Let me see what I can do" is not a commitment, it's a way to end the meeting without conflict. When you hear that, respond with a direct follow-up: "What would need to be true for this to be a yes, and when can we talk again?" That question does two things. It forces your manager to name a condition, which turns a vague stall into a visible target, and it locks in a second meeting so the conversation doesn't quietly disappear.

This matters even more in a field like social services, where 48,900 openings come up every year. An assistant who hears "let me see what I can do" too many times can walk into a comparable role at another agency long before this one finally answers.

If the answer is a flat no with no reason attached, ask for the reason anyway. Start with the most common one: is this about budget? If your manager says no, ask whether it's about timing instead, maybe the raise is fine in principle but the cycle just closed. If it's neither, the honest answer is probably about your performance, and that's worth asking about directly too, since it points you toward the one thing you can actually change before the next conversation.

Write down what gets said in that meeting the same day, while it's fresh. If your manager promises a review in three months, put it on the calendar yourself and bring it up again exactly then, politely but firmly. Managers are busy, and the promises made in a raise conversation often fall behind the next fire they have to put out. That's not usually bad faith. It's just how workplaces run. Your job is to make sure the promise survives contact with a busy calendar.

If the answer is no, here's what to ask instead

A clear no, with a real reason and a real timeline attached, is still a better outcome than a maybe that drags on for a year. If the raise genuinely isn't coming, ask about the things that don't show up on a pay stub. A flexible schedule matters most in roles that run evenings and weekends, like a social services assistant covering a shelter or a healthcare manager covering a unit that never closes. A title change that helps your next job search costs the company nothing today but changes what recruiters see on your resume next year. A training budget or fewer weekend shifts can matter just as much as the number on the check, especially in a role like line cook, where the work-life balance score already sits at 4 out of 10.

If none of that moves, it's worth comparing your current pay against what the role earns elsewhere, using real ranges rather than guesswork. A physical therapist, for comparison, works in a role with a work-life balance score of 7 out of 10 and a salary range of $77,140 to $135,140, which shows that strong pay and a sustainable schedule aren't mutually exclusive, they just depend on the profession and the employer. If you're in a role with strong growth and a wide range like project manager, where pay runs from $61,580 to $167,970 depending on scope and industry, a flat no at the bottom of that range is a signal worth taking seriously.

Open the Project Manager page, compare the training routes and the salary bands against your own trajectory, and decide whether the next raise is more likely to come from this employer or from the next one.