Skip to content
KhaiziNam Blog KhaiziNam Blog
Go back
Đọc bằng tiếng Việt

How to Negotiate Your Salary as a Fresh Graduate: Stop Leaving Money on the Table

You’re about to receive your first IT offer but don’t know whether to accept immediately or push back? This is a practical guide for freshers and junior developers to negotiate confidently, backed by data, without risking the offer — applicable from your very first interview.

Every year, hundreds of IT freshers accept salaries 15–30% below the company’s actual budget — not because they lack ability, but because they lack the tools. This guide gives you exactly what you need: market benchmarks, negotiation psychology, and real scripts you can use immediately.

Table of Contents

1. Why freshers are often paid below their actual value

2. The real benefits of negotiating — even without experience

3. What to prepare before negotiating

4. Step-by-step salary negotiation guide

5. Real-world case study

6. Mistakes that cost you leverage

7. Quick FAQ


Why Freshers Are Often Paid Below Their Actual Value

The problem isn’t capability — it’s information asymmetry. The employer knows their budget clearly; the candidate doesn’t. In that situation, the party with less information is always at a disadvantage.

Freshers typically fall into one of three psychological traps: fear of losing the offer if they push back, believing they have no right to negotiate without experience, or simply not knowing what the real market rate is. All three lead to the same outcome — accepting the first number offered.

The reality is that most companies have a salary range, not a fixed number. The first offer is usually the low end of that range. If you don’t negotiate, you’re leaving money on the table — not just once, but for your entire tenure at that company, since future raises are typically calculated as a percentage from your base.

The Real Benefits of Negotiating — Even Without Experience

Many freshers believe salary negotiation is a privilege reserved for experienced candidates. This is completely wrong.

Benefit 1: A higher base — compounding effect over years

If you raise your starting salary from 8M to 10M VND, the gap isn’t just 2M/month. With 10% annual raises, after 3 years someone starting at 10M earns about 13.3M, while someone starting at 8M earns only 10.6M. The gap compounds over time — it doesn’t shrink.

Benefit 2: A signal of self-awareness and maturity

Contrary to what many fear, professional negotiation rarely causes employers to pull offers. It’s often read as a sign that you know your own value, communicate with maturity, and think strategically — qualities any team wants to hire.

Benefit 3: Negotiation isn’t just salary — total compensation is what matters

When base salary isn’t flexible, you can still negotiate: training budgets, remote work, shorter review cycles (3–6 months instead of 12), or equipment allowances. A 12M package with full remote and a 6-month review cycle may have higher real value than 14M with nothing else attached.

Benefit 4: Building the negotiation muscle early

Your first salary negotiation is always harder than your second. Starting early builds this thinking muscle from the beginning of your career, rather than having to learn it in higher-stakes situations later.

See also: IT Fresher & Junior Salary 2026 — How Much Should You Expect? for specific benchmark numbers before entering any negotiation.

What to Prepare Before Negotiating

Negotiating without preparation is negotiating to lose. Here’s what you must have before sitting down.

Step-by-Step Salary Negotiation Guide

Step 1 — Control when salary comes up

Never bring up salary before you receive an offer or before the employer asks. If pushed too early in the interview process, deflect politely: “I’d like to learn more about the role and expectations first — can we revisit compensation once we’ve both confirmed this is a good fit?”

Step 2 — Let them name the first number

When asked for your salary expectation, try: “I’d prefer to hear the budget range you have for this role first, so we can see if we’re aligned on expectations.” The party that names a number first typically anchors at a disadvantage — let them set the first anchor.

Step 3 — Respond to the first offer correctly

When you receive the offer, don’t respond immediately. Say: “Thank you so much — I’m genuinely excited about this opportunity. Would it be okay if I had a day to review everything carefully before getting back to you?” This is professional, not unusual, and gives you time to prepare a counter-offer.

Step 4 — Deliver a reasoned counter-offer

Real script: “I’m really excited about this offer and genuinely want to join the team. Based on my research into market rates for [Role] in [City], and given my experience with [1–2 specific points], I was hoping we could adjust to [your target number]. Is that something we could explore?”

Important: give a specific number, not a range. A range signals uncertainty — a specific number signals research.

Step 5 — Handle rejection or inflexibility

If the company says the salary isn’t flexible, pivot to non-salary terms: “I understand completely. In that case, would it be possible to consider a salary review at 4–6 months rather than 12? Or is there a training or certification budget available?” — this is how you extract value when the primary path is blocked.

Real-World Case Study

Minh just graduated with a Computer Science degree and applied for a Backend Developer role at an outsourcing company in Ho Chi Minh City. After the technical round, HR called with an offer of 8 million VND per month.

Instead of accepting immediately, Minh spent a day researching on ITviec and TopDev — confirming that the market rate for Laravel developers in HCMC runs 8–13 million for freshers. Minh also remembered having self-deployed a real application to a VPS using Nginx and Laravel during university — something not every fresher can say.

The next day, Minh called HR back: “I’m really happy to receive this offer and genuinely want to join. However, based on my market research and the fact that I already have hands-on production deployment experience, I was hoping we could adjust to 10 million. Would that be possible?”

HR responded that 10M was over budget, but could offer 9M and an earlier review at 5 months instead of 12. Minh accepted. Result: 1M/month increase plus a review cycle 7 months earlier — from a single 5-minute phone call with preparation.

Mistakes That Cost You Leverage

Quick FAQ

Q: What if the company pulls the offer because I negotiated?

A: This is extremely rare when you negotiate professionally with clear reasoning. If a company withdraws an offer simply because a candidate politely asked about compensation, that’s actually valuable information about their culture — you just avoided a problematic work environment. To minimize risk, always express genuine enthusiasm for the role before raising the salary question.

Q: Can a fresher with no work experience really negotiate?

A: Yes — but your arguments must match your situation. Instead of work experience, use: personal projects deployed to production, technical certifications (AWS, Google Cloud), open-source contributions, or pure market benchmark data. Companies pay for the value you deliver — not years on a resume.

Q: Is it better to negotiate by email, phone, or in person?

A: Phone or in-person is generally more effective for initial negotiation — you can read reactions and adjust in real time. Email is useful to confirm in writing after you’ve verbally agreed. Never negotiate for the first time over text or chat — it’s too easy to receive a hard no with no room for dialogue.

Q: How much above the offer is reasonable for a counter?

A: For freshers, 15–25% above the initial offer is reasonable when backed by market data. For example: offer of 8M, counter of 9.5–10M is natural. Countering 40–50% higher without special justification destroys goodwill. Always pair your number with a specific reason — a number without context carries no weight.

Q: What if the offer is already higher than I expected?

A: Still try a light counter — not out of greed, but because you don’t know their ceiling. If they offer 12M and you only expected 10M, try asking about an early review or remote policy instead of pushing salary higher. There’s always additional value to unlock even when the base is already good.

Final Thoughts

Negotiating salary as a fresh graduate is not overreaching — it is a basic career skill you should master from day one. Every extra million at your starting point compounds into tens of millions over the first 3–5 years of your career.

Prepare your benchmarks, define your target number, practice your scripts, and walk in with a professional mindset — not begging, not confrontational, simply two parties finding a fair number together.

See also: IT Fresher & Junior Salary 2026 — How Much Should You Expect? for full benchmark data by role and company type before entering any salary negotiation.


Share this post:

Related Posts

IT Fresher & Junior Salary 2026: PHP, Node.js, React, Flutter - Real Market Data

Real salary benchmarks for IT freshers and junior developers in Vietnam in 2026, broken down by tech stack - so you know exactly what number to quote in interviews, or whether you're being underpaid right now.

Junior Developer Portfolio: What to Include to Get Interview Calls

A junior developer portfolio is the collection of real projects, skills, and professional information you present so employers can evaluate your abilities — substituting for the work experience section of your CV that's currently empty. For freshers and junior developers, a portfolio isn't something that's "nice to have" — it's the only evidence you can offer to prove you can actually build things

How to Write a Junior Developer Cover Letter With No Experience

Learn how to write a junior developer cover letter with no experience, including practical templates, real examples, common mistakes, and tips to pass the CV screening round.

Body Language in Tech Interviews: 7 Mistakes That Cost You the Offer

Body language in tech interviews refers to the non-verbal signals — posture, eye contact, hand gestures, and vocal tone — that recruiters observe alongside your technical answers. Mastering these signals helps you project confidence and professionalism from the very first second you walk into the room.

Questions to Ask Your Interviewer as a Junior Dev (Beyond Just Salary)

A practical guide to asking questions in IT job interviews — why the "do you have any questions?" moment matters more than most candidates realize, 20+ real questions organized by purpose and interview round, what never to ask, and how to choose the right questions for each interviewer you face.

Why Did You Choose IT? An Interview Answer That Actually Impresses Recruiters

A practical guide to answering "Why did you choose IT?" in job interviews — what HR is actually evaluating, a 3-part framework for building your answer, script templates for freshers and career changers, and the common mistakes that make this answer sound hollow and unconvincing.

'What Is Your Greatest Weakness?' — IT Interview Answer That Won't Get You Rejected

A practical guide to answering "What is your greatest weakness?" in IT job interviews — why the question is a trap for most candidates, a 3-step framework for freshers and junior developers, ready-to-use script templates, real case studies, and the six most common mistakes that get candidates rejected on the spot.

ReactJS Junior Interview Questions: 30+ Real Questions With Answers 2026

30+ of the most commonly asked ReactJS junior interview questions in 2026 — covering Virtual DOM, hooks, state management, and performance optimization — with detailed answers and code examples to help you confidently pass any technical interview. You've been learning React for a few months, you've built projects, but every time you walk into an interview you get asked things no tutorial ever cove

Refresh Token in Node.js and Laravel: Complete Production Implementation Guide 2026

A complete guide to implementing Refresh Tokens in both Node.js (Express) and Laravel PHP — covering database design, API endpoints, rotation logic, and common pitfalls — helping developers build a production-ready JWT authentication system in 2026.

Session vs JWT: Which Should Developers Choose? A Practical Comparison for 2026

A detailed comparison of Session and JWT across 6 practical technical criteria — architecture, revocation, scaling, performance, security, and complexity — helping developers make the right choice for each type of project in 2026.


Previous Post
Backend Junior Interview Questions: The Complete Guide Covering APIs, Databases, Auth, and Caching
Next Post
IT Fresher & Junior Developer Salary in 2026: How Much Should You Expect?