You've got multiple data analyst offers and no idea how to use them. This complete negotiation playbook teaches you how to compare total compensation, frame a counteroffer as an entry-level candidate, handle pushback, and close the deal — without burning any bridges.
You've spent months building your portfolio, grinding through SQL practice problems, and rehearsing behavioral interviews. Then something remarkable happens: you get not one offer, but two. Maybe three. Companies that barely acknowledged your applications six weeks ago are suddenly competing for your attention.
This is one of the strangest emotional experiences in a job search — you've been told repeatedly that you're unqualified, that you need more experience, that entry-level data roles aren't really entry-level. And now you're holding multiple offers, and you have no idea what to do with them. You feel grateful enough that turning down any money seems reckless, but you've heard you're supposed to negotiate. The problem is that every negotiation guide you've found was written for someone with five years of industry experience and a competing FAANG offer to wave around. That's not you, and you know it.
By the end of this lesson, you'll have a complete, realistic playbook for navigating salary and total compensation negotiation as a first-time data analyst hire — specifically when you have competing offers giving you genuine leverage, but no professional data experience to anchor your ask. We'll cover how to evaluate competing offers with precision, how to frame your counteroffer without sounding delusional, how to have the actual conversation (with scripts), how to handle pushback, and how to make the final decision when companies call your bluff.
What you'll learn:
This lesson assumes you've already received at least one written offer (or a strong verbal offer) and have at least one other active process in a late stage. If you're still working toward offers, the foundational work — building a strong portfolio, preparing for technical rounds, and navigating the full interview process — should come first.
You should also have a basic understanding of what data analyst compensation looks like in your target market. If you haven't done that research yet, we'll build it here, but plan to spend time on it before you start talking numbers.
Before we get tactical, let's fix a mindset problem that causes most first-time candidates to leave money on the table.
You've probably internalized the idea that your lack of experience makes you a weak negotiator. The logic feels airtight: experienced candidates have proven output, verified skills, and market alternatives. You have a bootcamp certificate, a GitHub with four projects, and six months of self-study. Who are you to negotiate?
Here's what that framing misses: negotiation leverage isn't about your credentials. It's about your alternatives. When you have a competing offer, you have a genuine, credible alternative to accepting any single offer. That's what creates leverage — not your resume, not your experience level, not how impressive your portfolio is.
A company that has invested four to eight weeks in recruiting you, run you through three to five interview rounds, and extended you an offer has already made a significant bet that you're worth hiring. They've spent real money — recruiter hours, engineering hours, coordinator time — to get to the point of making you an offer. When you reveal that another company has also made that bet, you've just confirmed your market value in the most concrete possible way.
Key insight
Competing offers are the only form of leverage that is universally respected in salary negotiation, regardless of experience level. A competing offer from a credible employer is more powerful than five years of experience when it comes to compelling a hiring manager to move on compensation.
This doesn't mean you can extract unlimited money. You're still an entry-level hire, and companies know it. But the ceiling on what you can realistically ask for is meaningfully higher than you'd have without competition. The question is how to use that leverage cleanly, professionally, and in a way that leaves you with good relationships at the companies you don't choose.
The biggest negotiation mistake entry-level candidates make isn't what they say during the counteroffer conversation — it's negotiating without knowing what they actually want. They focus on base salary because it's the number everyone talks about, and they ignore the dimensions that will actually determine how their first year feels.
Before you respond to any offer, build a comparison framework. Get everything in writing. Here's what to capture:
The obvious one, but make sure you're comparing equivalent pay periods. One company might quote an annual salary; another might quote semi-monthly or bi-weekly, which can look misleadingly similar. Convert everything to annual.
Also check whether the role is exempt or non-exempt (for US roles). Exempt salaried employees don't get overtime. Non-exempt employees do — relevant if the role involves occasional crunch.
Entry-level data analyst roles don't always come with equity, but some do — particularly at startups or pre-IPO companies. If equity is on the table, you need:
For annual bonuses, ask whether they're guaranteed or discretionary. "Up to 10% annual bonus" where the median payout is 3% is not the same as "10% guaranteed bonus." Ask what the average payout has been over the last three years.
This is where most candidates make massive errors. Two offers with identical base salaries can differ by $15,000 to $20,000 annually when you properly account for benefits.
Run through each of these and assign approximate dollar values:
This is harder to quantify but often more important than any dollar figure for a first role. Ask yourself:
Tip
Ask to speak with someone on the data team — not your manager, but a peer — before you accept. Frame it as wanting to understand what a day in the role looks like. You'll learn more in 20 minutes of unguarded conversation with a peer than in three formal interviews. This conversation is also where you'll find out whether the team is dysfunctional, overworked, or fantastic.
If offers are in different cities or have different remote policies, you need to adjust for this explicitly. A $70,000 offer in Austin, Texas has very different purchasing power than a $70,000 offer in San Francisco or New York. Use a cost-of-living calculator and normalize everything to a common baseline.
Remote work also has financial implications. Full remote saves commuting costs and potentially allows you to live somewhere cheaper. A hybrid role with three days in-office in an expensive city may cost you $3,000-$5,000 annually in commuting, lunches, and wardrobe — real money at an entry-level salary.
Once you have all of this data, build a simple spreadsheet. Put each company in a column. Put each dimension in a row. Convert as many rows as you can to annual dollar amounts. Sum them up.
You now have a Total Annual Compensation figure for each offer that reflects reality rather than the headline number. In most cases, the ranking of offers is different from what it looked like when you just compared base salaries.
Warning
Don't skip this step because you think you already know which offer is better. Intuition is systematically bad at comparing multi-dimensional options. The spreadsheet will surprise you at least once.
Before you counteroffer, you need to know what the realistic ceiling is. Asking for something wildly above market tells a recruiter that you haven't done your homework, and it can poison the relationship even if they still want to hire you.
For data analyst roles, your primary sources should be:
Filter all data by: your metro area, industry (finance data analyst salaries differ from nonprofit data analyst salaries significantly), and experience level. "Entry-level" or "0-2 years."
Aim to find the 50th, 75th, and 90th percentile figures for your specific market. You'll use these as reference points.
Companies use different pay bands. A Series A startup in Austin calling a role "Entry-Level Data Analyst" might have a band of $55,000-$75,000. A FAANG-adjacent company in Seattle calling the same title "Entry-Level" might have a band of $95,000-$120,000. These are different markets entirely.
Your leverage (competing offer) tells you where you sit in this company's band, but you need to know whether you're being offered at the floor, the midpoint, or the ceiling of their actual range. You can ask directly: "Is this offer at the midpoint of the band for this role, or is there flexibility?" Most recruiters will tell you something useful.
Write these down before you have any conversation:
The walk-away number is the most important. If you don't define it in advance, you'll be susceptible to pressure tactics in the moment. Knowing that you'll walk away from Company A if they won't go above $X means you can negotiate without fear, because you know exactly what "no deal" looks like.
One of the most practically important — and least discussed — aspects of negotiating with multiple offers is sequencing. Getting the order of operations wrong can mean losing leverage entirely or creating unnecessary pressure that damages relationships.
Most offers come with deadlines: "We need an answer by Friday." These deadlines are almost always negotiable, but you need to request extensions professionally and early.
Here's the scenario you're managing: Company A makes you an offer with a five-day deadline. Company B is in final rounds but won't have an answer for ten days. You need Company B's offer before you can use it as leverage with Company A.
The move is to contact Company A's recruiter the day you receive the offer (not at the deadline) and say something like:
"I'm genuinely excited about this opportunity and I want to make a thoughtful decision. I have one other process in a final stage, and I want to give both opportunities the consideration they deserve rather than making a rushed decision I might regret. Would it be possible to extend the decision timeline by [one week]? I want to be fully committed when I accept."
Most recruiters will grant this. They've invested too much in the process to lose you over a week. The ones who say "absolutely not, decide by Friday" are either playing hardball (in which case the deadline is still probably flexible) or genuinely rigid (in which case that rigidity tells you something about how they'll treat you as an employee).
Tip
When requesting a deadline extension, always frame it as wanting to make a deliberate, committed decision — not as "I'm waiting on another offer." The latter is fine to imply, but the former is more professional and less adversarial.
The optimal sequence is:
You want to approach your preferred company first because you're trying to get the job you want at the price you need — not to extract maximum dollars from everyone simultaneously. Trying to run a bidding war with two companies is rarely worth the relationship damage and stress it creates.
Now we get to the actual words. This is where most people freeze, because they don't know what to say, and they're afraid of sounding greedy or naive.
The good news: the structure of this conversation is not complicated. You need to do four things:
Email is actually preferable for initial counteroffers because it gives the recruiter time to consult with the hiring manager, reduces the pressure of a real-time conversation, and creates a paper trail you can reference later.
Subject: Re: Offer for Data Analyst — Meridian Analytics
Hi [Recruiter Name],
Thank you again for the offer — I'm genuinely excited about the Data Analyst role at Meridian Analytics, and I've been very impressed with the team throughout the process. The problems you're working on with the customer segmentation data and the chance to work alongside [specific name or team] are exactly what I'm looking for in a first role.
I want to be fully transparent with you: I've received a competing offer from another company at $72,000 base with a comparable benefits package. My strong preference is to join Meridian — the mission and the technical environment are a better fit for what I want to build in my career — but I'd like to see if we can close the gap a bit on base compensation.
Would Meridian be able to come up to $70,000? That would make it an easy decision for me.
I'm happy to hop on a call if that's easier. And again, I want to reiterate that this isn't a negotiating tactic — I have a genuine preference for Meridian, and I'm hoping we can find a way to make this work.
Best, [Your Name]*
Notice several things about this script:
It leads with specificity. Mentioning the segmentation work and the specific colleague or team signals that you paid attention during interviews. This is not generic enthusiasm.
It discloses the competing offer number. Never disclose the competing company's name unless asked — you don't need to, and naming competitors can create awkward dynamics. But you must disclose the dollar amount. Vague claims of a "competing offer" without a number are treated with skepticism. A specific number is treated as real.
It asks for a specific number that's lower than the competing offer. This is counterintuitive. You're not asking them to beat the competing offer — you're asking them to come close enough that your stated preference for them becomes the deciding factor. If you ask them to beat $72,000 when your stated preference is Meridian, you look mercenary. If you ask them to hit $70,000, you're giving them an easy win that lets them tell their hiring manager "we got the candidate for $2,000 below market."
It ends with a specific ask and then stops. You're not hedging, not offering alternatives, not negotiating against yourself. One number, clearly stated, with a sincere closing.
Sometimes recruiters prefer to have these conversations live. If they call you after receiving your email, or if you'd rather have the conversation in real time, here's how it flows:
Recruiter: "Hi [Name], I got your email. Let's talk about it."
You: "Thanks for calling. I'll keep it simple — I genuinely prefer Meridian, and I want to make this work. I have an offer at $72,000, and I'm asking if you can come to $70,000. If you can do that, I'm ready to sign."
[Pause. Let them respond. Do not fill the silence.]
This is harder than it sounds. Most people experience silence after stating a number as pressure and start backpedaling immediately. Don't. You've stated your position clearly. The recruiter needs a moment to think, or to say they need to check with someone. Let them do that.
Warning
The single most common self-sabotage move in live negotiation is talking after you've made your ask. Candidates say something like "...but I understand if that's not possible, and I'm really excited either way, and I could maybe consider $67,000 if that works better..." The moment you do this, you've negotiated against yourself. State the number. Stop.
A clean acceptance of your number is wonderful and occasionally happens. More often, you'll get one of five responses. Here's how to handle each.
This means they may genuinely not be able to move on base salary. The smart response is not to argue — it's to expand the conversation:
"I understand. Is there flexibility in other parts of the package — a signing bonus, an earlier performance review date, or additional PTO? I want to find a way to make this work."
A one-time signing bonus is often easier for a company to approve than a base salary increase because it doesn't affect the ongoing salary budget. Asking for $3,000-$5,000 as a signing bonus in lieu of a base increase is a very reasonable move and often gets approved quickly.
An earlier performance review (at six months instead of twelve) is valuable because it means your first opportunity for a raise comes sooner. Many companies are happy to agree to this because it costs them nothing upfront and signals their confidence in you.
They moved, but not all the way to your ask. Now you need to decide in real time: is $67,000 enough to choose this company over your alternative? If yes, say so and close it:
"I appreciate the movement. At $67,000 I can make this work — I'll send over my acceptance today."
Don't push again. You've negotiated, they've moved, you have a deal. Trying to squeeze another $2,000 after they've already moved risks turning a successful negotiation into an adversarial one.
If $67,000 isn't enough, say so clearly and without drama:
"I appreciate you checking. I think we're close, but the gap still makes the other offer hard to pass up. Is there any additional flexibility, or is $67,000 the final number?"
This gives them one more shot before you make your decision. If they say $67,000 is final, you either accept it or you don't — but you don't keep pushing.
Great news — they matched it. Before you say yes immediately, think about whether there's any reason to ask for slightly more (you won't always have this opportunity again until your first performance review). You can say:
"That's wonderful — I really appreciate that. Would there be any room to go to $74,000, or is $72,000 the ceiling? Either way, I'm very close to saying yes."
This works because you've already framed yourself as someone with a genuine preference for this company. Asking for a small additional increment after they've matched the competing offer reads as reasonable rather than aggressive. If they say $72,000 is the ceiling, accept it graciously. You've gotten what you asked for.
This happens, and it's frustrating. Some companies — particularly larger, more structured organizations — have rigid compensation bands and genuinely don't move for entry-level hires, regardless of competing offers.
Before you take this at face value, probe once:
"I understand there may be constraints on the band. I have a competing offer at $72,000, and I want to choose Meridian — is there anything outside of base salary that might be possible? Even a signing bonus or professional development budget?"
If the answer is still no, you have a real decision to make. Does the role offer enough non-monetary value — learning, growth, team quality, mission — to justify leaving money on the table? Sometimes yes. Accepting a lower-paying role at a company with an exceptional team and a clear path to promotion can be a better career move than taking the higher-paying role at a company where you'll stagnate.
But if the non-salary dimensions are roughly equivalent, the company that won't move even a dollar when you have a competing offer is sending a signal about how they treat employees. File that information accordingly.
This is the most common response. It's good news — it means they haven't said no. Your job is to express appreciation and give them a reasonable timeframe:
"Of course, take the time you need. I do have a deadline on my other offer — I need to give them an answer by [date]. If you're able to let me know by [one day before that date], I can make sure Meridian gets my full consideration."
This gives them a real timeline without being threatening, and it's honest. If they come back after your competing offer deadline, you've lost your leverage anyway.
For entry-level candidates, the highest-percentage move is often not on base salary at all. Here's why: companies have internal equity concerns. If they have three data analysts who were all hired at $65,000 two years ago, paying you $72,000 creates internal friction if those analysts ever find out. They're sometimes more constrained on base salary than the headline suggests.
But they have much more flexibility on one-time payments, benefits, and role structure. Here are the most negotiable non-salary items:
A one-time payment, taxed as ordinary income, that doesn't affect your ongoing salary band. Ask for 5-10% of base salary. At a $65,000 offer, that's $3,250-$6,500. This is surprisingly often approved quickly because it comes from a different budget than ongoing salary.
If you have student loans or relocation costs, frame the signing bonus as offsetting those. This makes the request feel reasonable and grounded rather than opportunistic.
If one offer is fully remote and another is hybrid, that's worth real money. Calculate the commuting cost difference annually and include it in your comparison spreadsheet. You can also ask a hybrid company to reduce required in-office days:
"I notice the role requires three days in-office. I'm comfortable with that, though I'd find it valuable to have flexibility on which days. Is the three-day requirement fixed, or is there some flexibility depending on team needs?"
Flexible hybrid is worth something even if the number of days stays the same.
For a first data role, this is underrated. A $2,000-$3,000 annual professional development budget lets you pursue certifications that actually accelerate your career, attend conferences where you'll build the network that shapes your next five years, and stay current on a field that moves extremely fast.
If a company doesn't offer one, ask: "Would it be possible to include a professional development budget? Even $1,000 annually would be meaningful." This is almost always approved because it costs so little and signals that you're thinking about growing in the role.
Entry-level titles matter more than people admit because they affect your starting salary in every subsequent role. "Data Analyst I" is weaker on a resume than "Data Analyst." "Associate Data Analyst" is weaker than both. If a company is offering you an Associate title and you have a competing offer with a full Analyst title, ask if they can adjust the title even if salary is fixed.
Sometimes you need time between your current role (or your last semester, or your bootcamp graduation) and your start date. A later start date saves you from financial stress during the transition. Ask for it if you need it. Companies almost always accommodate start date requests.
Note
You can negotiate multiple things at once, but present them as a package rather than a list of demands. "If you can't move on salary, I'd love to discuss whether a signing bonus and professional development budget might be possible" is one ask that covers two things. Don't send five separate negotiation emails on five separate dimensions — it reads as nickel-and-diming.
Everything above applies to any candidate. Now let's address the edge cases that are specific to your situation as someone without professional data experience.
A recruiter might implicitly or explicitly discount your competing offer if it comes from a small startup or a company outside their industry. The way to handle this is to keep the conversation on the dollar figure and away from the company comparison:
"I understand the companies are different contexts, but the compensation difference is real regardless of where it comes from. At $72,000 versus $64,000, that's a meaningful gap I need to address."
You don't need to defend the other company's prestige. The number is the number.
Occasionally a recruiter will push back not on budget constraints but on your credentials. This is their attempt to re-anchor your sense of your own market value.
The response:
"I appreciate that perspective, and I understand the experience question. What I can tell you is that [Company B] made me an offer at $72,000 after the same interview process, so the market seems to be landing there. I'm not asking for something above market — I'm asking you to be competitive with what I'm being offered elsewhere."
You're not arguing about your credentials. You're pointing to revealed market information. Two companies completing full interview processes and making offers is the most credible possible signal of your market value.
Nonprofits, government agencies, and mission-driven companies often use this framing to preemptively close down negotiation. It's sometimes genuine and sometimes a tactic.
Your response depends on how much you care about the mission. If you're genuinely drawn to the mission, acknowledge it and redirect:
"I deeply respect the mission, and it's part of why I applied. I'm not expecting you to match a tech company's total comp package. I just want to see if there's any movement possible — even a signing bonus or an earlier review date — that acknowledges the market context."
If you don't particularly care about the mission and it's just a lower offer, treat it like any other company with budget constraints and make your decision based on the full picture.
If your background is in finance, marketing, operations, or any field where you were using data — even if not in a formal data analyst role — you have domain expertise that is genuinely valuable. Framing your value as a first-time hire from a domain perspective can support your negotiation.
For example: if you're coming from a finance background and you're joining a fintech company, you bring financial modeling intuition and domain vocabulary that a computer science grad without financial background doesn't have. Name that explicitly:
"I want to highlight that while I'm new to a formal data analyst role, I come in with [X years] of finance domain experience that means I won't need onboarding on the business context — only the technical environment. That's something my competing offer also recognizes."
At some point in a negotiation, you may hear a version of: "If the other offer is that attractive, you should probably take it." This is one of the scariest moments for a first-time negotiator because it sounds like rejection. It's not rejection — it's a test.
The company is checking whether your preference for them is real or whether you're bluffing. Your response:
"I want to be clear — my preference is to be here. I've said that throughout, and I mean it. I'm raising the compensation question because I want to make a sustainable decision, not because I'm looking for an excuse to leave. If you're telling me the number is final, I'll take some time and give you my answer by [date]."
This response does three things: it reaffirms your preference (genuine, not desperate), it acknowledges reality (you heard them), and it buys you a small amount of time to think without creating an ultimatum.
If they come back and say yes, the negotiation worked. If they hold firm, you make your decision based on the full picture — which you already built in your comparison spreadsheet.
Key insight
The company calling your bluff is almost never actually telling you to leave. It's a negotiating move designed to make you feel like you've pushed too far. If you've been professional and reasonable throughout, they want to hire you. They're hoping you'll back down. You don't have to — but you also don't need to escalate.
This is the most underrated part of the entire process. The way you decline an offer will be remembered. The data world is smaller than you think, and the recruiter at Company B today may be at Company A in two years, or may be the person who refers you to your next role five years from now.
A professional decline is short, warm, and definitive. Do not leave offers open-ended. Do not ghost. Do not send a one-line email after three days of silence.
Here's the template:
Subject: Re: Data Analyst Offer — Cascade Metrics
Hi [Recruiter Name],
I wanted to follow up on the offer and let you know my decision. After a great deal of consideration, I've decided to accept a position with another organization.
This was a genuinely difficult decision — I have a lot of respect for the team at Cascade Metrics and for the process you ran. I hope we'll stay in touch, and I genuinely mean it when I say I'm impressed by what you're building.
Thank you for the time and consideration.
Best, [Your Name]
Short. Warm. Final. No explaining why the other company was better. No venting about what Cascade Metrics could have done differently. No door-slamming. Just a clean, professional close.
Follow up by connecting with the recruiter on LinkedIn if you haven't already. You want to stay in their network. If networking for data professionals long-term is something you're thinking about — and you should be — building that network early is worth real attention.
This exercise is designed to be run while you have actual offers in hand. If you're reading this before that point, bookmark it and return when the time comes.
Phase 1: Offer Comparison Spreadsheet (60 minutes)
Open a spreadsheet and create columns for each offer you've received. Create rows for each of the following:
Sum rows 1-10 for each company. That's your Total Effective Compensation for each offer.
Phase 2: Market Research (45 minutes)
Look up Levels.fyi, LinkedIn Salary, and Glassdoor for your specific role title, metro area, and industry. Record the 25th, 50th, and 75th percentile figures. Note where each offer falls in that distribution.
Phase 3: Set Your Numbers (15 minutes)
Write down:
Phase 4: Draft Your Email (30 minutes)
Using the script template from Step Four, draft your actual counteroffer email to your preferred company. Personalize it with specific details from your interview process. Read it aloud — does it sound like a human being wrote it, or does it sound like a template?
Phase 5: Practice the Live Conversation (15 minutes)
Find someone willing to role-play as a recruiter. Give them the "calling your bluff" script from Step Eight and practice your response. The goal is to say your number, stop talking, and not backpedal when challenged.
You don't need to name the competing employer, and doing so often backfires. The recruiter may make unflattering comparisons ("Oh, Cascade Metrics — they have really high turnover"), which weakens your position. Keep it to "another offer" and the dollar amount.
Never do this. If you claim a competing offer and it comes out that it wasn't real or was significantly embellished, you've destroyed your credibility and potentially rescinded your offer. Only negotiate with real, current, written offers.
If you receive an offer on Monday with a Friday deadline and you wait until Thursday afternoon to counteroffer, you've given the company almost no time to respond. They'll feel pressured and rushed, which isn't the mood you want them in when they're deciding whether to stretch the budget. Counteroffer within one to two business days of receiving the offer.
Always use email as your primary channel for offers and counteroffers unless the recruiter has established phone as the primary communication mode. Email creates records, gives both parties time to think, and is more professional. A counteroffer sent in a Slack DM or text message looks like you don't understand professional norms.
This is the big one. Candidates who negotiate exclusively on salary often end up at the higher-paying job that's the worse career move. A $5,000 salary difference is less important than whether your first role puts you in a position to negotiate from strength at your second role. Make sure you've evaluated team quality, learning opportunities, and growth trajectory as carefully as you've evaluated compensation. If you're unsure how to assess a team's quality before you accept, evaluating a data team's technical stack and growth potential deserves its own deep read before you sign anything.
First-time candidates frequently don't negotiate because they're afraid of looking ungrateful or losing the offer. The offer will almost never be rescinded because you negotiated professionally. Companies expect negotiation. Recruiters are rarely surprised by it. The downside risk of a professional counteroffer is essentially zero; the upside is real money.
If you only have one offer and no competing process, you can still negotiate — but you need a different strategy. Your anchor becomes market data rather than a competing offer. The detailed version of that approach is covered in negotiating a higher salary without industry experience. For advanced strategy across your full career, the deeper framework is in salary negotiation for data professionals.
If both companies have offered their final numbers and neither will move, you make your decision based on total compensation (your spreadsheet) and role quality. This is why the comparison framework matters so much — when you have to decide without additional leverage, you need clarity on what you actually value.
You now have a complete playbook for navigating your first data analyst offer negotiation when competing offers are in play. Let's recap the key moves:
Build a comparison framework that captures total effective compensation — not just base salary. The offer that looks lower at first glance often isn't.
Research your market before you name any number. Knowing the 50th and 75th percentile for your role, location, and industry tells you what's realistic to ask for.
Set your ideal, target, and walk-away numbers in writing before any conversation. The walk-away number is the most important because it lets you negotiate without fear.
Manage the timing by requesting deadline extensions early, sequencing conversations to approach your preferred company first, and giving recruiters enough time to escalate your counteroffer internally.
Make your counteroffer in writing with a specific number, genuine enthusiasm, and clear disclosure of the competing offer amount (not the company name).
Handle pushback by expanding the conversation to non-salary elements when base is truly fixed, by holding your position when they call your bluff, and by knowing when to close.
Decline gracefully with warmth and professionalism. The data world is small. Leave every relationship better than you found it.
The next immediate steps are to build your comparison spreadsheet today if you have offers in hand, and to draft your counteroffer email before you talk to anyone. The preparation matters more than the script.
Once you've accepted your offer, your attention shifts from negotiation to execution. The work you do in your first ninety days will determine whether you're able to negotiate from strength at your first performance review. What to expect in your first 90 days as a data analyst picks up exactly where this lesson leaves off — go there next.