You’re 20 minutes into a solid IT interview. The conversation is flowing. You’ve nailed the technical questions, told a good story about a production outage you handled, and the hiring manager is nodding along. Then they drop it:

“So, what are your salary expectations?”

And your brain shuts off.

You mumble something. Maybe you throw out a number that’s too low because you panicked. Maybe you say something vague like “I’m flexible” and immediately regret it. Or maybe you go too high, and you can feel the temperature in the room drop.

This moment trips up IT professionals at every level. The sysadmin making $65K who suspects they’re worth more. The senior engineer who doesn’t want to price themselves out of a role they actually want. The career changer who has no idea what the market even pays.

Here’s the thing: the salary conversation isn’t a trap. But it does have rules. And most IT pros never learn them because nobody teaches this stuff in certification programs or technical training.

Why This Question Feels So Uncomfortable

The awkwardness isn’t in your head. There’s a genuine power imbalance baked into the salary question, and it favors the employer almost every time.

They know the budget. You don’t. They’ve had this conversation hundreds of times. You’ve had it maybe a dozen. They have a range approved by finance, and their goal is to land you at the low end of it. Your goal is the opposite, but you’re flying blind.

This dynamic is why so many IT professionals either leave money on the table or avoid the conversation entirely. Neither approach works.

The other reason it feels uncomfortable: most technical people didn’t get into IT because they love talking about money. You got into it because you like solving problems, building systems, or breaking into networks for a living. Sales-style negotiation feels foreign. That’s normal.

But salary conversations aren’t sales pitches. They’re information exchanges. Once you reframe them that way, the whole thing gets easier.

When the Question Shows Up (And Why Timing Matters)

The salary question doesn’t always hit at the same point in the process, and where it lands changes your strategy.

The Application Stage

Many companies now ask for salary expectations right on the application form. This is the lowest-stakes version of the question, but it can still screen you out if you go too high or too low.

What to do: If the field is optional, skip it. If it’s required, enter a range based on your research (more on how to research below). Make the range wide enough to stay competitive — something like “$85,000 - $105,000” rather than a single number.

Some companies use this field to auto-reject candidates above budget. If you can’t find the salary range anywhere and the field is required, a broader range keeps you in the running while still anchoring high.

The Recruiter Screen

Internal recruiters and third-party staffing firms almost always ask about salary in the first call. This is partly to filter candidates and partly to set expectations before the hiring manager gets involved. This is the same call where they’ll verify your resume details and ask basic qualifying questions.

What to do: This is actually the best time to gather information rather than give it. The recruiter often knows the approved range. Ask: “What’s the budgeted range for this role?” Most will tell you.

If they push for your number first, give a researched range and add: “But I’d want to understand the full compensation picture before committing to a specific number.”

The Hiring Manager Interview

When the hiring manager asks about salary, it usually means you’re a serious candidate and they’re checking whether the numbers will work. This is good news, even though it doesn’t feel like it in the moment.

What to do: This is where your research and your value pitch matter most. Don’t just throw out a number. Frame it around what you bring. More on the exact scripts below.

The Offer Stage

If salary doesn’t come up until the offer, you’re in the strongest position. They’ve decided they want you. Now it’s just about the terms.

What to do: Don’t accept on the spot. Ever. “I’m really excited about this. Can I have 48 hours to review the full offer?” Then go negotiate from a position of strength. The negotiation tactics article covers this stage in detail.

The Research You Need to Do Before Any Interview

Walking into a salary conversation without data is like showing up to a technical interview without studying. You might survive, but you’re making it harder than it needs to be.

Where to Find Real Numbers

Not all salary data is created equal. Here’s what’s actually useful:

Levels.fyi is the best source for software engineering and DevOps roles, especially at larger companies. Shows base, bonus, and equity breakdowns. The data comes from verified submissions, so it’s more reliable than anonymous surveys.

Glassdoor is useful for a broad picture, but take the numbers with a grain of salt. The data skews older and doesn’t always distinguish between metro areas well. Better for getting a baseline than for precise targeting.

Bureau of Labor Statistics — Good for understanding macro trends but not granular enough for negotiation. Knowing the national median for “Computer Support Specialists” won’t help you negotiate a sysadmin role in Denver.

LinkedIn Salary Insights lets you compare roles and locations if you have a solid LinkedIn profile. Not perfect, but decent for ballpark figures.

The IT Support Group Salary Survey covers real-world numbers from 1,072 IT professionals. Check our 2026 salary survey for benchmarking against peers.

Job postings themselves. Many states and cities now require salary ranges in job listings. Colorado, California, Washington, New York City, and others have pay transparency laws. Even if you’re not in those states, companies that list ranges there often apply the same ranges nationally. Search for the same role on job boards with location set to Colorado or NYC to find ranges.

How to Build Your Number

Take data from at least three sources and look for where they overlap. Adjust for:

  • Location: A network engineer in San Francisco makes 30-40% more than one in Indianapolis. If the role is remote, most companies still adjust for your location.
  • Experience: Most salary data buckets experience into junior (0-2 years), mid (3-5), senior (6-10), and principal/staff (10+). Know which bucket you’re in.
  • Certifications: Some certs genuinely move your salary range. CISSP and cloud architect certs (AWS Solutions Architect Pro, Azure Solutions Architect) often add $15-25K. CompTIA A+ and Network+ don’t typically move salary needles for experienced pros.
  • Specialization: Cybersecurity analysts and cloud engineers consistently out-earn generalist roles. If you have specialized skills, your range is different from the generic title suggests.

Your target should be a range — not a single number. The bottom of your range should be the minimum you’d actually accept. The top should be ambitious but defensible based on your research.

Exact Scripts for the Most Common Salary Questions

You’re probably here for the scripts. Let’s get specific.

”What are your salary expectations?”

This is the most common version. Here’s a framework that works at every level.

For mid-career IT pros (3-8 years):

“Based on my research for [role title] in [city/market], and given my experience with [specific relevant skill], I’m targeting the $X to $Y range. But I’m more interested in the total opportunity — the work, the team, and the growth potential. Is that range in line with what you’ve budgeted?”

Notice a few things about this script. It leads with research, not feelings. It names a range, not a single number. It mentions a specific skill to justify the higher end. And it ends with a question that puts the ball back in their court.

For entry-level or career changers:

“I’ve been researching [role title] salaries in [market] and I’m seeing a range of $X to $Y for someone transitioning in with [relevant transferable experience or certification]. I’m flexible on the exact number, but I want to make sure we’re in the same ballpark. Can you share what the range looks like on your end?”

If you’re switching into IT from another field, you might feel like you have zero leverage. You have more than you think. Transferable skills matter, and acknowledging your research shows you’re serious.

For senior/specialized roles:

“For this level of [specialization] in [market], I’d expect total compensation in the $X to $Y range, depending on the equity and benefits structure. I’d want to understand the full package before getting too specific. What does the comp structure look like here?”

Senior folks: stop underselling. If you’re a cloud engineer or security architect with 8+ years, you should be leading with total comp, not just base salary.

”What are you currently making?”

This question is increasingly illegal. Several states ban it entirely. But it still gets asked. A lot.

If it’s illegal in your jurisdiction:

“I’m not comfortable sharing that — actually, I believe [state/city] prohibits that question. But I’m happy to discuss my salary expectations for this role.”

Say this politely but directly. If the interviewer pushes back, that tells you something about the company culture.

If it’s legal where you are:

“I’d rather focus on what this role pays and what I bring to it than anchor to my current compensation. My target for this move is in the $X to $Y range — does that work with your budget?”

The reason you deflect: your current salary might be below market (especially if you suspect you’re underpaid), and sharing it anchors the entire negotiation lower.

”We need a specific number, not a range”

Some recruiters and hiring managers push back on ranges. Here’s how to handle it.

“Fair enough. If I had to pick one number, I’d say $X. But that assumes the benefits, PTO, and growth opportunities are competitive. I’d want to evaluate the full picture before locking in.”

Pick a number in the upper third of your researched range. You can always negotiate down. You can almost never negotiate up from your opening number.

”That’s above our budget”

This isn’t necessarily a rejection. It’s information. Sometimes it’s a test.

“I appreciate the transparency. What does the approved range look like? I’m interested in the role and want to find something that works for both sides.”

If they name a number that’s genuinely too low, it’s okay to say so: “That’s below what I could accept for this move. Is there flexibility in the range, or is it firm?” Then decide whether the role is worth it for other reasons: growth, learning, title, remote work.

Sometimes the gap is unbridgeable. That’s useful information too. Better to find out now than three rounds of interviews later.

The Mistakes That Cost IT Pros the Most Money

After looking at patterns across hundreds of IT salary discussions in communities and hiring forums, a few mistakes show up over and over.

Mistake #1: Answering Too Fast

The salary question triggers a fight-or-flight response. Your instinct is to fill the silence with a number, any number, just to make the discomfort stop.

Resist this. Take a breath. It’s completely acceptable to pause for two or three seconds before answering. You can even say, “That’s a great question — let me think about how to frame this.”

Nobody has ever lost a job offer by pausing to think.

Mistake #2: Naming a Number Without Context

Saying “$95,000” and then going silent is one of the weakest positions you can put yourself in. There’s no justification, no framing, no signal that you’ve done research.

Always attach your number to something: market data, your experience level, a specific skill you bring. “Based on what I’m seeing for senior sysadmins in the Dallas market, and given my experience managing VMware environments at scale, I’m targeting $95-110K” is the same number but carries ten times the weight.

Mistake #3: Saying “I’m Flexible” and Meaning It

“I’m flexible” is fine as a diplomatic softener at the end of a well-framed answer. It is not fine as your entire answer. “I’m flexible” by itself says “I haven’t researched this and you can lowball me.”

You’re probably skeptical of another interview article telling you to “know your worth.” Fair. But this one is purely mechanical: if you don’t name a number, someone else will, and their number will be lower than yours.

Mistake #4: Ignoring Total Compensation

Base salary is the number everyone fixates on. But total compensation (health insurance, 401k match, RSUs/equity, bonus, PTO, education stipends, remote work) can swing the real value of an offer by 20-40%.

A $95K offer with a 6% 401k match, $5K education budget, and full remote is worth more than a $105K offer with no match, no education budget, and mandatory office attendance. Run the full math before comparing offers.

This matters especially for remote IT positions where the salary might look lower on paper but the total package (plus no commute costs) makes up the difference.

Mistake #5: Not Negotiating Because You “Don’t Want to Be Difficult”

This one plagues IT professionals more than almost any other group. Technical people tend to be conflict-averse. Negotiating feels confrontational. It isn’t.

Hiring managers expect you to negotiate. When you don’t, some of them actually worry — “does this person not know their value?” One survey from Glassdoor found that roughly 68% of employees accepted the salary they were first offered. That means 68% of people are probably earning less than they could.

You’re not being difficult. You’re being professional.

Special Situations That Trip People Up

When You’re Overqualified for the Role

Maybe you’re a senior engineer who wants to step into a lower-pressure role. Or you were laid off and need to cast a wider net. Either way, the interviewer is looking at your experience and wondering if you’ll bolt after six months.

Address it directly: “I know my experience level might seem high for this position. I’m genuinely interested in this role because of [specific reason]. On salary, I’m aligned with what this position pays — I’m not expecting senior-level compensation for a [mid-level] role.”

When You’re Making a Career Change Into IT

If you’re transitioning from another field, your previous salary might be irrelevant (a teacher making $45K moving into a help desk role at $50K) or misleadingly high (a finance analyst making $120K moving into entry-level cybersecurity).

Focus the conversation on the role, not your history: “My previous compensation was in a completely different field, so I don’t think it’s relevant here. For [this IT role], I’m targeting $X based on my research and the certifications I’ve earned.”

When the Role is Remote

Remote roles are trickier. Some companies pay the same regardless of location. Others adjust based on your zip code. A few (increasingly rare) try to cut salary for remote workers under the logic that “you’re saving on commute.”

Ask directly: “Does compensation for this role vary by location, or is it the same regardless of where I’m based?” This saves you from mispricing yourself. If they adjust for location, research the salary for their HQ city, not yours — that’s usually the anchor they use.

When You’re an Internal Candidate Going for a Promotion

This is a different dynamic entirely. You already know the company, and they already know you. The leverage you have is institutional knowledge and the cost of replacing you. The leverage you don’t have is competing offers (unless you go get one).

Before the conversation, find out what external candidates would get for the same role. If there’s a significant gap between what you’re making and what the market pays, bring the data. “I’ve been looking at market rates for [new role], and I want to make sure my compensation reflects the market for this position, not just an increment from my current salary.”

For more on navigating internal moves, the getting promoted guide covers the politics side of this.

What Salary Transparency Laws Changed (And What They Didn’t)

Pay transparency is reshaping the salary conversation in IT, but the change is uneven.

As of 2026, Colorado, California, Washington, New York (including NYC), Connecticut, Maryland, Rhode Island, Nevada, and several other states require employers to disclose salary ranges in job postings or upon request. Illinois, Massachusetts, and Hawaii have similar laws on the books or recently enacted.

What this means for you:

  • If the posting includes a range, use it. That range is your anchor. Target the upper half unless you’re significantly junior for the role.
  • If you’re in a transparency state and the employer doesn’t post a range, you can request it. They’re legally required to share.
  • If you’re applying from a non-transparency state to a company headquartered in one, the law usually still applies — the employer has to comply based on where the job is posted, not where you live.

What transparency didn’t fix: Ranges are often absurdly wide. “$70,000 - $140,000” tells you almost nothing. It just means they have budget flexibility, and where you land in that range depends entirely on the negotiation. Transparency gave you the playing field dimensions. You still have to play the game.

How to Practice Before the Real Thing

You wouldn’t walk into a technical interview without practicing, and salary conversations deserve the same prep.

Script It Out

Write down your answer to “What are your salary expectations?” using the frameworks above. Say it out loud. Seriously — the first time you hear yourself say a number out loud should not be in the interview.

If saying “$110,000” feels physically uncomfortable, practice until it doesn’t. The discomfort comes from unfamiliarity, not from the number being wrong.

Role-Play With Someone

Ask a friend, spouse, or mentor to play the interviewer. Have them push back: “That’s higher than we expected.” “Can you be more specific?” “What are you making now?” Practice your responses until they feel natural.

Prepare for the Pushback

Write down the three most likely objections and your responses:

  1. “That’s above our range” → “What does the approved range look like?”
  2. “We need to know your current salary” → “I’d rather focus on what this role pays.”
  3. “Can you go lower?” → “Is there flexibility elsewhere in the package — signing bonus, PTO, education budget?”

Having these responses pre-loaded means you won’t freeze when the pressure hits.

Record Yourself

This sounds cringe-worthy, but it works. Record yourself answering the salary question on your phone. Listen back. Do you sound confident? Are you rushing? Do you trail off at the end? The patterns you catch will surprise you.

The Cheat Sheet

Save this for right before your next interview:

ScenarioWhat to Say
”What are your salary expectations?""Based on my research for [role] in [market], I’m targeting $X-$Y. Does that align with your budget?"
"What are you currently making?""I’d rather focus on what this role pays. My target is $X-$Y."
"We need a specific number""If I had to pick one: $X. But that assumes competitive benefits."
"That’s above our budget""What’s the approved range? I want to find something that works."
"Are you flexible on salary?""I am within a reasonable range. What does the total comp package look like?”
Recruiter asks first”What’s the budgeted range for this role?”

What Happens After You Name Your Number

The conversation doesn’t end when you say a number. What happens in the next 30 seconds matters just as much.

If they agree immediately: You probably went too low. Don’t panic. This is why you negotiate the full package, not just base salary. Ask about signing bonuses, review timelines, and equity.

If they counter lower: This is normal and expected. Don’t take it personally. Ask what’s driving the lower number and whether there’s flexibility in other areas.

If they go silent: Let them. Silence is not rejection. Many interviewers pause to think or to note your answer. Resist the urge to immediately backpedal with “but I’m flexible!” Let the silence breathe.

If they end the conversation: Rare, but it happens. If your number is genuinely misaligned, it’s better to find out now. You wouldn’t want to go through four rounds of interviews only to discover the offer is $30K below what you need.

Build the Skills That Make the Number Bigger

The best salary negotiation strategy is having skills the market pays well for. While you’re prepping for interviews, invest in the skills that actually move the needle.

Shell Samurai is a good place to build real command-line skills if you’re targeting sysadmin, DevOps, or security roles — all of which tend to pay above the IT median. Combine hands-on practice with relevant certifications, and your salary range shifts upward before you walk into the room.

If you want to go deeper on the specific questions interviewers will ask, prep those in parallel. The salary conversation goes better when you’ve already demonstrated your value in the technical portion.

FAQ

Should I always give a range instead of a specific number?

Yes, in almost every scenario. A range signals flexibility while still anchoring high. Make your bottom number something you’d genuinely accept — don’t play games with a “range” that starts way above market. The exception: if a recruiter specifically asks for a single number and won’t accept a range, give the number in the upper third of your researched range.

What if I lowballed myself in an earlier interview round?

It happens. You’re not locked in. At the offer stage, you can say: “After learning more about the scope of this role, I’d like to revisit compensation. Based on the responsibilities we discussed, I think $X better reflects the position.” Will this always work? No. But hiring managers know that early-stage numbers are preliminary, and most will entertain a reasonable adjustment.

Do salary transparency laws mean I shouldn’t negotiate?

Absolutely not. Posted ranges are just that: ranges. Companies budget for negotiation within those ranges. If a posting says $90K-$120K, they expect the final offer to land somewhere in the middle or upper portion for strong candidates. Transparency gives you better data, not a final answer.

How do I handle salary questions in a virtual interview?

The strategy is exactly the same. The medium doesn’t change the message. The one difference: in a virtual interview, you can keep your salary research notes just off-camera. Use that advantage. Tape your range, your justification, and your pushback scripts to the wall behind your webcam if you need to.

Is it okay to ask about salary in the first interview?

It’s more than okay — it’s smart. You don’t want to invest hours in a process only to find out the pay is $30K below your minimum. Frame it as practical: “Before we go further, I want to make sure we’re aligned on compensation range so neither of us wastes time. Could you share what’s budgeted for this role?” Most hiring managers respect this directness. The ones who get offended are telling you something about the company culture.

The salary conversation gets easier every time you do it. You don’t need to be a smooth talker or a natural negotiator. You need research, a framework, and the willingness to sit through a few seconds of discomfort.

Every dollar you negotiate is a dollar you earn for every year you hold that role. A $5,000 bump isn’t just $5K. It’s $5K multiplied by however many years you stay, plus the compound effect on future raises, bonuses, and your next job’s starting salary.

Stop leaving money on the table. Practice the scripts. Do the research. Walk in knowing your number.