Your First IT Salary: How to Negotiate Your Offer and Earn What You Are Worth
Free help with this topic inside the Henry Jenkins Mentorship on Skool: live Security+ classes, AZ-104 guides, and career coaching. Join free →
Most new IT professionals lose real money before they ever start their first job. Not because the job pays poorly, but because they accept the first number on the table without a conversation. Studies show that most people who negotiate earn thousands more per year than people who do not, and that gap compounds over a whole career.
Here is the problem. Most beginners walk into salary talks with no proof, no research, and no plan. They think negotiation is about being pushy. It is not. Negotiation is about having evidence of your value and the confidence to state it clearly. That is exactly what a good career plan gives you.
This guide covers all 6 areas that build your leverage: the certifications that raise your market value, the hands on labs that prove your skill, the career development moves that put you in a higher pay band, the interviewing skills to run the negotiation conversation, the study tips to research real numbers, and the mentorship that keeps you from walking in alone. Work this plan and you will never again accept a salary blind.
Certifications That Raise Your Number
Certifications do 2 things at a salary negotiation. First, they move you into higher pay bands. Many job postings list pay ranges, and the top of the range is usually reserved for candidates who check the certification box. Second, they give you a fact to point to when you name your number. "I hold Security+" is a statement of value. "I am interested in security" is not.
If you are brand new, the CompTIA stack is the most direct path to higher entry pay. A+ proves you can do the foundational work. Network+ proves you understand how systems talk to each other. Security+ proves you can think about risk, and it unlocks government and defense roles that pay above market. That combination is often the difference between a 42,000 dollar help desk offer and a 58,000 dollar IT support or junior analyst offer.
For the cloud path, the Microsoft AZ-900 gets your foot in the door and the AZ-104 moves you into administrator roles that start 10,000 to 15,000 dollars higher than general support roles in most markets. Cloud skills are priced like a premium because every company needs them and the supply of certified people is smaller.
Do this now:
- Pick 1 certification to earn in the next 90 days and treat it as your negotiation investment. The exam fee is small compared to the raise it unlocks.
- List the certification on your resume the day you pass, not the day you feel ready. Employers filter on it.
- Research postings for your target role and write down how many list your planned certification as required or preferred. That is your evidence file for the negotiation.
- Never inflate what you hold. One verified credential beats 3 claimed ones, and background checks will find the truth.
Hands On Labs That Give You Leverage
A certification gets you into the conversation. A lab story wins it. When a hiring manager asks why you deserve the higher number, "I built a home lab with 3 virtual machines, segmented the network with VLANs, and set up monitoring with a SIEM" is leverage that a piece of paper alone cannot give you.
Labs give you negotiation power because they prove you can do the work on day 1. Employers pay more for candidates who need less training. If you can describe 2 or 3 real things you built, configured, and broke and fixed, you are no longer a risky beginner. You are a junior professional with evidence.
Build labs that map to the job you want and the pay you want:
- For security roles: build a virtual lab with an attack machine and a target machine, run scans with Nmap, and write up what you found. That single project gives you 3 interview stories about enumeration, analysis, and reporting.
- For cloud roles: deploy a full environment in Azure with virtual networks, virtual machines, and storage, then document the architecture. Cloud engineers who can show deployed resources command cloud pay.
- For support and admin roles: set up Active Directory in a virtual machine, create users and groups, and practice Group Policy. Every Windows shop pays for this skill.
- Put every lab on GitHub with screenshots and a short write up. A link in your resume that a manager can click is worth more than a paragraph of claims.
When the offer comes, your labs become sentences like this: "In my lab I already built and secured a network like the one in your job description, so I can contribute from week 1." That sentence is worth real money.
Career Development: Position Yourself in a Higher Pay Band
Your salary number is mostly decided before the negotiation, by the roles you target and the story you tell. Career development is the quiet work of aiming at the right band instead of settling into a lower one.
Start by targeting roles that pay more for the same experience level. A help desk role and a junior SOC analyst role may both hire beginners, but the analyst role often starts 8,000 to 12,000 dollars higher. A cloud support engineer and a general IT support tech are both entry level, yet cloud pays a premium. Choose your lane with the pay data, not just the job title.
Then build a visible record. Hiring managers negotiate with people, not resumes. The candidate with a GitHub full of labs, a blog post about a project, or a short video explaining a concept looks like someone already doing the job. That perception moves you from "trainee pay" to "contributor pay."
Make these moves:
- Write down 3 target roles and the salary range for each in your city, using sites like Glassdoor, Levels.fyi, and the Bureau of Labor Statistics. Only aim at roles you can describe with labs and certs.
- Post about 1 project per month where hiring managers can see it, on LinkedIn or a simple portfolio site. Visibility is a pay multiplier.
- Volunteer for 1 thing that sounds like the job you want, whether that is helping a nonprofit with their network or assisting a local business with a cloud migration. Real client work is the fastest band upgrade.
- Review your positioning every 90 days. If your skills moved up a level, your target salary should move with them.
Interviewing Skills: Running the Negotiation Conversation
Most beginners think negotiation is a single awkward moment at the end. In reality it is a skill you practice through the whole interview process, one conversation at a time.
The first rule: never give a number first if you can avoid it. When asked about salary expectations early in the process, answer with a question: "What is the budgeted range for this role?" That one sentence puts you on equal footing. If they press you, give a researched range, never a single number, and anchor the top of your range at your real target.
The second rule: tie every request to evidence. Do not say "I want more." Say "Based on my Security+ certification, the Azure environment I built and documented on GitHub, and the market data for this role in Atlanta, I am looking for 62,000 to 68,000." Evidence turns a wish into a business case.
The third rule: negotiate the whole package, not just the base salary. Entry level candidates often ignore signing bonuses, certification reimbursement, training budgets, remote days, and review timelines. A 6 month salary review written into your offer letter can be worth more than a small bump on day 1.
Practice these steps:
- Write out your exact opening sentence for the salary conversation and say it out loud 10 times. The words should feel natural before the real call.
- Prepare 3 evidence points before every final interview: your strongest certification, your best lab project, and 1 market data point. Bring them up even if the interviewer does not ask.
- If the offer is below your range, pause and say "I am excited about this role. Based on my research the range for this position is X to Y. Can we get closer to X?" Then stop talking. Silence is part of the skill.
- Get every change in writing before you accept. A verbal promise about a raise or a bonus is not an offer term.
Study Tips: Research the Market Before You Sit Down
You cannot negotiate what you have not studied. Walking into a salary talk without market data is like walking into a certification exam without studying the objectives. The research is the preparation, and most beginners skip it.
Study salary data the same way you study for an exam: with a plan, with sources you trust, and with notes you can reference. Spend 2 to 3 focused sessions on this before any offer arrives, so the numbers are already in your head when the moment comes.
Your research plan:
- Check 3 sources for your target role in your city: Glassdoor, Levels.fyi, and job postings that list pay ranges. Write down the low, middle, and high numbers. Your target lives between the middle and the high.
- Talk to 5 people doing the job you want. Ask what they started at and what they earn now. Real numbers from real people beat every website, and most professionals will share if you ask respectfully.
- Study the job description for keywords that raise pay: security clearance eligibility, cloud platforms, automation, specific tools. Each one you can honestly claim is a reason for a higher number.
- Learn the cost math. A 5,000 dollar raise is not just 5,000 dollars. Over 5 years with typical raises compounding, it can mean 30,000 dollars or more in lifetime earnings. Write that number down and keep it where you can see it.
- Rehearse your numbers out loud until they sound boring. If the number feels scary to say, you have not practiced enough.
Treat market research like an exam objective: know it cold, cite your sources, and update it every 6 months as the market moves.
Mentorship: Never Negotiate Alone
Here is what nobody tells beginners: almost every professional who negotiates well had someone in their corner the first time. A mentor who has been through 10 salary talks can tell you in 15 minutes what would take you 3 job cycles to learn alone.
A mentor helps with salary in 3 specific ways. First, they reality check your number. Beginners usually aim too low because they do not know the market. A mentor who knows your skills will tell you when you are underpricing yourself. Second, they role play the conversation. Practicing your opening line with someone who has sat on the hiring side removes the fear. Third, they connect you to people who share real numbers, which feeds your research with data no website has.
Find that person with the same energy you bring to studying:
- Join 1 community where IT professionals gather, such as a local meetup, a Discord server for your certification, or a mentorship program. Show up consistently for 30 days before you ask for anything.
- Ask a specific question, not a vague one. "Can I run my salary target past you for 10 minutes?" gets a yes. "Will you be my mentor?" usually gets silence.
- Offer value back. Share your study notes, help another beginner, or document a lab. Mentorship flows toward people who give, not just people who take.
- After your first negotiation, tell your mentor how it went. That closes the loop and turns a one time favor into an ongoing relationship.
You do not get what you deserve in this industry. You get what you can prove and what you can ask for. Build the proof with certifications and labs, aim with career strategy, research with study discipline, and ask with a mentor beside you. Your first salary sets the floor for every raise that follows. Make it count.
Build the Career, Not Just the Cert
Join the free Henry Jenkins Mentorship community: live Security+ classes, AZ-104 study guides, and career coaching.
Join Free MentorshipGet new articles by email
One short email when a new article drops. No spam, unsubscribe anytime.