How to Ask for a Raise in Your First Job: A Step-by-Step Script for Young Professionals
Glory Karl

You've been in your first real job for a while now. You're not the new person anymore. You're the one who knows the vendor follow-up, the one who rebuilt the tracker nobody asked you to fix, the one who quietly covers for the team when things slip. And you're starting to think you're worth more than you're being paid.
So why does typing the words "can we talk about my salary" feel like you're asking for a favor?
Here's the honest answer: nobody taught you how to ask for a raise in your first job. School taught you to wait to be evaluated. Your first job taught you to keep your head down and be grateful. Neither of those lessons gives you a script for a conversation that most people avoid for years.
This guide gives you the script. Not a vague pep talk. A two-week plan, the exact words to use, and the answers to the questions that make your stomach drop. You can use all of it, or just the parts that fit your situation.
Before You Ask: Decide What You're Actually Asking For
Most first raise conversations go sideways before they start, because the person asking hasn't decided what they want. They walk in hoping to "feel valued" and walk out with a vague promise to "revisit this in a few months." That's not a win. That's a delay.
So before anything else, get specific about your ask. You're choosing one of these.
- A percentage increase. You want more money in the same role. This works best when your responsibilities have grown since you started or when your pay is out of line with what the role pays in your market.
- A promotion with a title change. You're already doing parts of the next-level job and you want the title and pay to match.
- A raise tied to a specific change. For example, "I'm taking over the reporting from Maya" or "I'm now managing the interns." You're asking to be paid for work that's about to land on you.
- A meeting to set a checkpoint. Sometimes the honest ask is: "I'd like to agree on what would justify a raise in six months, in writing." That's a real, respectable ask, and it's often the smartest first move.
Pick one. Write it down in a single sentence. If you can't, you're not ready for the meeting yet, and that's fine. You're not wasting time. You're preparing.
Know your number before the meeting, not during it
You need a number, a range, and a walk-away point.
Your number is what you ask for. Your range is what you'd accept. Your walk-away point is the lowest offer you'd say yes to without feeling resentful every time you open your payslip. Write all three down. Then, when someone asks "what number are you thinking?" in the meeting, you don't have to invent something on the spot.
Research comes from job postings for the same title in your region, salary data from recruiting firms, conversations with people one or two years ahead of you, and any published pay bands your company uses. In some places, employers are required to list salary ranges. Use whatever you can find. You don't need perfect data. You need a defensible guess.
Build the Case: Two Weeks of Quiet Preparation
Confidence in this conversation doesn't come from hyping yourself up in the bathroom mirror. It comes from evidence. Here's how to build it in about three hours of work spread across two weeks. Roughly 90 minutes of that is thinking and drafting. The rest is notes you can take as you go about your normal day.
Step 1: Create a two-column proof list
Open a document. Make two columns.
In the left column, write down every contribution you've made since you started, or since your last review. Be specific and quantified where you can.
Not "helped with social media." Instead: "Took over the weekly newsletter from a departing contractor and rebuilt it in the existing tool, which reduced the time it took each week from an afternoon to about an hour."
Not "reliable." Instead: "Covered two weeks of client intake during a colleague's leave; zero inquiries went unanswered."
If you don't have numbers, use time saved, problems prevented, or things that simply wouldn't have happened without you. Those count.
Step 2: In the right column, write what it was worth
This is the part young professionals skip, and it's the part that does the work. For each item on the left, write the business impact in plain language. Did it save the team hours each week? Bring in a client? Prevent a costly mistake? Reduce the number of complaints? Make a process possible that hadn't been possible before?

You're not inflating. You're translating. "I made a tracker" becomes "the team can now see where every ticket stands, which means fewer double replies to clients."
Step 3: Add what's grown since day one
List the things you handle now that you didn't handle when you started: tasks you took on, people you support, decisions you make without checking with anyone. When your responsibilities grow and your pay doesn't, that's not a demand. That's a mismatch worth pointing out.
Step 4: Pick your top three, then throw away the rest
Your manager will remember three things. They might remember five at a push. They will not remember the tenth item on your list. So choose the three strongest, with the clearest impact, and make those your argument. You'll bring the full list to the meeting in case you're asked, but you'll open with three.
Step 5: Find the right window
Timing changes the conversation. Better windows include just after you've delivered something visible, during the normal review cycle if your company has one, or before the budget gets locked rather than after. Worse windows include the week your manager is firefighting a crisis, the day after a major team failure, or the twelve minutes at the end of a busy Friday.
If your company runs annual reviews, ask for a separate conversation a few weeks before that process begins, not during it. Review meetings are usually about ratings and process. A raise conversation deserves its own room.
Step 6: Request the meeting in plain language
Don't ambush them in the hallway. Don't hint. Send something short and direct:
"Hi Sam, I'd like to set up 30 minutes this week or next to talk about my compensation and how my role has grown since I started. Happy to work around your calendar. Would Thursday or next Monday work?"
Notice what's in there. It's clear about the topic. It's short. It gives options. And it doesn't apologize. You're not asking permission to have a feeling. You're scheduling a business conversation, which is a normal part of work.
| Week | What you do | Time budget |
|---|---|---|
| Week 1 | Build the proof list, write the impact column, and pick your top three | About 75 minutes |
| Week 1 | Research your number, range, and walk-away point | About 45 minutes |
| Week 2 | Write and practice the script out loud, including the money answer | About 30 minutes |
| Week 2 | Send the meeting request and prepare three questions to ask them | About 15 minutes |
| Total | Roughly under three hours, spread across two weeks | About 2 hours 45 minutes |
The Script: Exactly What to Say in the Room
Structure matters more than clever wording. Open warm, come with the facts, make the ask, then stop talking. That last part is the hardest.
The opening, about 40 seconds
"Thanks for making time. I want to talk about my pay. I've really valued being here, and I want to be here as the role grows. So I've put together where I think I've added value and where my responsibilities have changed, and I'd like to make a case for a salary review."
Then walk your top three, briefly. For each one, say what you did and what it changed. Two sentences per item, maximum.
"When [person] left, I took over the newsletter and rebuilt it so it takes about an hour a week instead of an afternoon. That's roughly a day a month back for the team, and open rates haven't dropped since we took it in-house."
Do not read from a document with your eyes down. Glance at your notes if you need to, but look up. You're not presenting a thesis. You're having a conversation about money with a person who can approve it.
The ask, one sentence
"Given all that, I'm asking for [specific number or percentage], and I'd like to see it take effect from [month or pay period]."
Then pause. Count to five in your head. Silence feels enormous from your side of the table and perfectly normal from theirs. Every word you add after your ask weakens it. Don't fill the gap with "I mean, whatever you can do" or "I know it's a tough time." Let it sit.
When they ask "what number were you thinking?"
Have this ready. Answer it directly, and give it a frame.

"I looked at what this role pays in our market and what my responsibilities look like now compared to when I started. Based on that, I'm looking for [number]. I know that's above my current level, and I think it reflects what the job has become."
Do not give the number first if you can help it, but if they ask, answer. Mumbling "I don't know, what do you think?" hands the entire conversation to them.
When they say "let me think about it"
This is the most common response, and it's not a no. It's also not a yes, and you should not treat it as one.
"That's fair. What would be helpful for you to make a decision? And can we put a date in the diary to come back to this, maybe two weeks from now?"
Then send a short follow-up email the same day summarizing what you asked for and when you'll talk next. Written confirmation is not aggressive. It's professional, and it prevents your request from quietly evaporating.
When they say no
A no is information. Your job is to find out what kind. Two different nos need two different responses.
A no because of budget or timing: "I understand. Could we agree on a date to revisit, and on what would need to be true by then?"
A no because they don't see the impact: "Help me understand what would need to look different for a yes. I'd rather know than guess."
Both answers give you something to work with. Neither requires you to accept "we'll see" and never bring it up again.
What to Do Right After the Conversation
Within an hour, while it's fresh, do these three things.
- Write down what was said. The number offered, the reasons given, the date agreed, and anything vague you need to clarify. Memory rewrites itself within a day, and this record protects you.
- Send the recap email. Three or four lines: thanks, restating the ask, confirming next steps and dates. Keep the tone warm and matter-of-fact, not legalistic.
- Decide what you'll do if nothing changes. Not today. But name it, privately, so you're choosing to stay rather than drifting into staying. If a raise doesn't come and the reason given is one you can't act on, you've learned something real about this employer, and that's worth knowing at 24 rather than 34.
The Mindset Move That Makes All of This Easier
The thing that gets in the way isn't a missing script. It's a belief that asking means you're ungrateful.
Flip it. You're not asking for a favor. You're giving your employer a chance to keep someone who's already contributing and who is thinking clearly about their future. Managers can't fix pay they don't know is a problem. Staying silent doesn't protect you. It just delays the moment when you find out where you stand.
And notice the skill you're actually building here. You're learning to make a case for yourself with evidence, to ask for something directly, to handle a no without crumbling, and to follow through in writing. Those are not first-job skills. They're career skills, and you'll use them for the next forty years.
So pick your number this week. Draft the three items this week too. Send the request by the end of next week. If the answer is lower than you hoped, you'll have a date to revisit and a clearer picture of what your employer values. If the answer is better than you expected, you'll wonder why you spent so long waiting.
Either way, you stop guessing and start knowing. That's the whole point.

