How to Negotiate Your Tech Salary: Scripts, Tactics and Real Numbers
Most engineers leave $20,000 to $50,000 on the table in every offer they accept. Not because they lack skills. Because nobody taught them that negotiating is expected, prepared, and completely normal.
This guide fixes that. You will find 40 numbered questions covering every stage of a tech salary negotiation — from the first recruiter call to signing the offer — with real salary benchmarks, word-for-word scripts you can use in English, and the mechanics behind why each tactic works.
If you are a software engineer, product manager, data scientist, or engineering manager in Latin America working with international companies, this is written for you.
Part 1: The Mindset Foundation
1. Is it really safe to negotiate? Won't the company rescind the offer?
Yes, it is safe. Offer rescissions for negotiating in good faith are vanishingly rare in tech. Companies invest weeks of recruiter time, interviewer hours, and hiring manager attention to generate an offer. They are not going to throw that away because you asked a professional question about compensation.
The data confirms this. A Fidelity survey found that 85% of people who countered on salary got at least some of what they asked for. Studies of tech candidates show that those who negotiated earned an average of $24,000 more per year than those who accepted the first offer.
The only scenario where pushing back creates risk is if you are rude, make an ultimatum you cannot back up, or misrepresent a competing offer. None of those are negotiating — those are mistakes. Polite, data-backed negotiation does not get offers pulled.
2. What is the real cost of not negotiating?
Run the math. If you accept a $90,000 offer when the band goes to $105,000, you leave $15,000 on the table in year one. But that $15,000 compounds. Your next raise is calculated as a percentage of your current salary. Your next external offer is often anchored to what you currently earn. The gap widens every year.
Over a five-year career, that single decision not to push back costs $80,000 to $120,000 in cumulative earnings. For LATAM engineers who may be transitioning from local to international compensation for the first time, this multiplier effect is even larger.
3. What percentage increase is reasonable to ask for?
In tech, 10% to 20% above the initial offer is standard and expected. If you have a competing offer or strong market data, 15% to 25% is defensible. Anything above 30% over a written offer needs extraordinary justification — a competing offer with verifiable numbers, a unique specialization, or a role change in scope.
For context: the average accepted counter-offer in tech raises the original number by 12.45%, or roughly $27,000 a year.
4. Why do companies make offers below the top of their band?
Every role has a compensation band with a floor and a ceiling. Companies almost never open with the ceiling for two reasons. First, they want room to negotiate — the initial offer is a probe to see if you will accept. Second, if you perform above expectations, they want to have upward mobility to give you a raise without reclassifying the role.
The practical implication: the first number you receive is rarely the real number. There is almost always flex, and the only way to access it is to ask.
5. Does my current salary affect what I can ask for?
Legally, many US states (California, New York, Colorado, Massachusetts) prohibit employers from asking about your salary history. Regardless of the law, your current salary is irrelevant to what the market pays. If a senior engineer role in a US company pays $140,000, it pays $140,000 whether you currently earn $60,000 or $130,000.
Never anchor yourself to your current number. The correct anchor is market data for the role, level, and location.
Part 2: Research and Preparation
6. Where do I find reliable salary data?
Use multiple sources and triangulate:
- Levels.fyi — the most accurate source for total compensation at tech companies, broken down by level, location, and year. 2026 medians: Software Engineer (mid-level) $226K total comp, Senior Engineer $312K, Staff Engineer $457K.
- Glassdoor — useful for base salary ranges at specific companies; less accurate on equity.
- LinkedIn Salary — good for PM and non-engineering roles.
- Blind (TeamBlind) — candid salary posts from verified employees, particularly useful for FAANG and mid-size tech.
- Payscale and Radford (now Mercer) — used by HR teams internally; public versions give market ranges.
- remoteok.com and Himalayas — remote-first job boards that display salary ranges, increasingly required by US pay transparency laws.
For LATAM-specific international remote data, Howdy, Mismo.team, and Gold Penguin publish annual benchmarks by country and seniority.
7. What are the real salary ranges I should be targeting in 2026?
US-based roles (total compensation including equity and bonus):
| Level | Years of Experience | Base Salary | Total Comp |
|---|---|---|---|
| Junior / L3 | 0–2 | $75K–$92K | $95K–$140K |
| Mid-level / L4 | 2–5 | $110K–$145K | $160K–$220K |
| Senior / L5 | 5–8 | $145K–$185K | $220K–$320K |
| Staff / L6 | 8+ | $180K–$240K | $320K–$500K |
| Principal / L7 | 12+ | $220K–$300K | $450K–$700K |
Remote roles for LATAM engineers (paid in USD, working for US/EU companies):
| Level | USD Annual Total |
|---|---|
| Junior (0–3 years) | $30K–$55K |
| Mid-level (3–5 years) | $55K–$85K |
| Senior (5–8 years) | $80K–$120K |
| Senior+ / Lead (8–12 years) | $100K–$150K |
| Staff / Engineering Manager | $130K–$180K |
AI/ML engineers command a 20–40% premium above general SWE rates at every level.
8. How do I find the specific band for the exact company making me an offer?
Four approaches, in order of reliability:
- 1Levels.fyi company page — search the company and filter by level. Look at offers from the last 12 months.
- 2Ask the recruiter directly — "Can you share the full compensation band for this level?" Some will, especially at companies with pay transparency policies.
- 3State pay transparency laws — if the role is posted for California, Colorado, New York, or Washington state residents, the posting must include the salary range by law. Find the original job posting even if you found the role elsewhere.
- 4Talk to current employees — reach out on LinkedIn or Blind. Most engineers are willing to share range information with peers.
9. What should I know about total compensation before I start negotiating?
Base salary is one component. In tech, the full package includes:
- Base salary — your fixed annual cash
- Annual bonus — typically 5–20% of base, often tied to company and individual performance
- Equity (RSUs or options) — at public companies, Restricted Stock Units vested over 4 years. At startups, options with a strike price and exercise window.
- Signing bonus — one-time cash, often used to cover unvested equity you leave behind
- Benefits — health insurance, 401(k) match (US), vacation, parental leave, equipment budget, learning budget
For LATAM engineers working remotely, the equity component deserves close attention. Many recruiters underplay it. A $30,000 RSU grant at a stable public company is real money — $7,500 a year in stock on top of your base.
10. What is the difference between RSUs and stock options, and which should I negotiate harder on?
RSUs (Restricted Stock Units): Standard at public tech companies. You receive shares that vest on a schedule (typically 25% per year over 4 years). They have real value the day they vest because the company is already public.
Stock options: Common at startups. You receive the right to buy shares at a fixed price (the strike price). They have potential value but require the company to exit (IPO or acquisition) to be liquid. 90-day exercise windows after departure are the norm — negotiate this to 10 years if possible.
Which to push harder on: RSUs at public companies are more negotiable in volume and carry more immediate value. Options at early-stage startups matter more in percentage terms — focus on the strike price, vesting schedule, and what happens to your options if the company is acquired before you vest.
Part 3: What to Say (and What Not to Say)
11. What do I say when the recruiter asks "what are your salary expectations?"
This is the most important question in the entire process, and most candidates answer it wrong.
The goal is to avoid anchoring yourself to a low number before you know their budget. Here are three scripts that work:
Script A — Deflect to their range:
"I'm focused on finding the right fit for this role, and I trust that your comp package is competitive for the level. Can you share the band you're working with for this position?"
Script B — Give a range anchored to market data:
"Based on what I'm seeing for senior backend engineers with this stack in the current market, I'm targeting somewhere in the $130K to $150K range for base. Does that align with where you're thinking?"
Script C — Acknowledge and defer:
"I want to make sure I'm looking at the full picture before throwing out a number — base, equity, bonus. Once I see the complete offer, I'll be in a much better position to have that conversation."
Never say: "I'm currently making X and looking for a bump." Never give a number lower than your actual target to seem "reasonable." The first number in a negotiation becomes the anchor. Make sure it is your number, not theirs.
12. What do I say the moment I receive the offer?
Do not accept or reject on the spot. Thank them, express genuine excitement, and ask for time.
Script:
"Thank you so much — I'm really excited about this opportunity and the team. I want to give this the thought it deserves. Can I have until [specific date, 3–5 business days] to review everything and come back to you?"
This is not stalling. This is professional and expected. Use those days to research the band, compare against competing offers if any, and prepare your counter.
13. How do I counter an offer in writing?
Written counters work well for documentation and for removing the social pressure of a live phone call. Keep it short, warm, and data-backed.
Email counter script:
Subject: Re: Offer — [Your Name]
>
Hi [Recruiter Name],
>
Thank you for the offer. I'm genuinely excited about this role and the team — it's exactly the kind of problem I want to be working on.
>
After reviewing the complete package and looking at current market data for this level, I'd like to discuss bringing the base salary up to $[target number]. Based on what I'm seeing for comparable roles — particularly at [Company B / Levels.fyi data for this level] — $[target] reflects the market rate for someone with my background in [specific skills].
>
I'm fully committed to making this work and I'm confident we can get to an agreement. Is there flexibility to move in that direction?
>
[Your name]
Note the structure: warmth, specificity, data-back, forward commitment. No ultimatum. No apology.
14. How do I counter on a phone call?
Phone counters are faster and often more effective because you can read the recruiter's reaction and adjust. Keep your counter simple, state the number, state your reasoning, and go quiet.
Phone script:
"I really appreciate the offer, and I'm excited about the opportunity. After looking at market data for this role and level, I was hoping we could get the base to $[target]. That's in line with what I'm seeing for comparable positions. Is there room to move there?"
Then stop talking. Silence is your most powerful tool. Let the recruiter respond. Filling the silence with justification weakens your position.
15. What do I say if they say "that's the highest we can go on base"?
This is where most candidates fold. Do not. If base is truly maxed, switch to other levers.
Script:
"I understand there may be limits on base. Are there other places we can look — like the equity grant, the signing bonus, or an accelerated review at six months instead of a year?"
If they confirm base is firm and there is no flex elsewhere, you need to decide whether the package works. But do not assume the first "we're at the top of our band" is final — it often is not.
16. What do I say when I have multiple offers?
Having two offers is the single most powerful negotiation tool in tech. Use it transparently and without bluffing.
Script:
"I want to be straightforward with you — I have another offer on the table at $[number]. I'm genuinely more excited about this role and this team, which is why I'm having this conversation. Is there anything you can do on the compensation side to make this easier for me to choose?"
This creates urgency without being aggressive. It is honest. It gives the company a concrete number to beat. And it works — companies routinely improve offers when they know they are competing.
The rule: only use this script if the competing offer is real.
17. What do I say when they ask "can you share your other offer in writing?"
You are not obligated to provide documentation of a competing offer. A professional answer:
Script:
"I'd rather not share the specifics of another company's confidential offer, but I can confirm the number I mentioned is accurate. I'm being completely transparent about where things stand."
Most recruiters accept this. If they push further, it usually means they want to verify before escalating to the hiring manager for additional budget.
18. How do I ask for a signing bonus?
Signing bonuses are designed to cover two specific situations: equity you are leaving behind at your current employer, and the gap between what they can offer in base and what you need.
Script:
"One thing I'd like to address is that I have unvested RSUs at my current company that I'll be walking away from — roughly $[amount] that would vest over the next [X] months. I'm not asking for a dollar-for-dollar match, but could we look at a signing bonus to help offset some of that?"
If you do not have unvested equity, you can still ask:
"Given that base is capped at [X], would it be possible to include a signing bonus to bridge the gap for year one while I demonstrate my impact?"
19. How do I negotiate equity specifically?
Most candidates accept the initial equity grant without question. This is a mistake.
Script to request more equity:
"I've been looking at equity grants for this level on Levels.fyi, and the initial grant seems a bit below what I'm seeing for comparable roles. For a senior engineer at a company of this stage, I'd typically expect something in the range of $[X] to $[Y] in RSU value. Is there room to bring the grant closer to that range?"
For startups, additional questions to ask:
- "What does the vesting schedule look like, and is there an acceleration clause on acquisition?"
- "What's the current preferred share price and the most recent 409A valuation?"
- "What is the exercise window after departure? Is it possible to extend that to 10 years?"
- "What percentage of the company does this grant represent on a fully diluted basis?"
20. What if I genuinely have no competing offer — am I powerless?
No. Market data is almost as powerful as a competing offer when it is specific and credible.
The key is to cite real numbers, not vague assertions. "The market pays more" is weak. "Levels.fyi shows the 75th percentile for this level at your company's competitor is $147,000" is strong.
Script:
"I don't have another offer I'm weighing right now — I've been focused on this opportunity specifically. But I've done a lot of research on current market rates. Levels.fyi and Glassdoor show comparable roles in this market ranging from $X to $Y. I'm hoping we can get to [target], which is solidly within that range."
Part 4: Negotiating Specific Roles
21. How should a junior developer (0–2 years, LATAM) approach negotiating their first international offer?
The first international offer is the most important one because it sets the base for the next five years. Most junior LATAM devs undersell themselves on the first offer because they compare to local salaries.
Do not compare to local. Compare to the role. A junior developer working full-time for a US startup is doing junior developer work, and they should be paid junior developer rates.
Target range: $35,000–$55,000 USD annually for a fully remote junior role. Closer to $55,000 if you have strong English, relevant experience, or a specialized stack.
Script:
"I'm very excited about this opportunity. Looking at similar roles for junior engineers at remote-first companies paying in USD, I'm targeting around $45,000 to $55,000. I understand I'm earlier in my career, but I'm confident I can deliver from day one. Is the offer in that range, or is there room to get there?"
22. How does a senior engineer (5–8 years, LATAM) negotiate a competitive offer from a US startup?
At this level you have leverage: you are not easy to replace, you have done it before, and the company has already invested heavily in evaluating you.
Target range: $90,000–$130,000 USD for remote senior roles at funded startups. Up to $150,000 at growth-stage or later-stage companies.
Three things to negotiate simultaneously:
- 1Base salary (push to top of band)
- 2Equity grant (ask for the 75th percentile for this level on Levels.fyi)
- 3Signing bonus (especially if you have unvested equity)
Script:
"I appreciate the offer. To give you a complete picture of where I'm landing: looking at Levels.fyi and Glassdoor data for senior backend engineers at growth-stage startups, I'm seeing base in the $115K–$130K range and equity grants in the $100K–$150K band over four years. The current offer is a bit below that on both dimensions. I'm hoping we can get base to $120K and the equity grant to $120K in RSU value — that would put us squarely in the market. Is that doable?"
23. How does a product manager negotiate differently from an engineer?
PMs have more qualitative leverage (customer insight, strategy, cross-functional influence) but less technical credentialing than engineers. The key is to anchor on business impact.
PM salary ranges (remote, USD, 2026):
- Junior PM (0–2 years): $50K–$70K
- PM (2–5 years): $70K–$110K
- Senior PM (5–8 years): $100K–$140K
- Principal/Group PM (8+ years): $130K–$180K
Script for a PM counter:
"I'm really excited about this role. I've been looking at comparable PM positions at companies of similar stage and size, and I'm seeing base salary in the $[range] range. The product area I'd be owning maps to [revenue impact / user base], and I have direct experience moving the needle on [specific metric]. I'd like to discuss bringing the base to $[target]. Is that within range?"
24. How do engineering managers negotiate differently?
Engineering managers have a unique argument: they multiply team output. One strong EM can increase the throughput of 6–10 engineers. Make that argument explicit.
EM salary ranges (remote, USD, 2026):
- EM (managing 4–8 engineers): $120K–$160K
- Senior EM (managing 8–15 or multiple teams): $150K–$200K
- Director of Engineering: $180K–$250K
Script:
"I understand the range for this EM role. I want to make sure the comp reflects the scope I'd be taking on — managing [X] engineers across [Y] teams, owning [product surface], and being accountable for [deliverable]. At the companies I'm comparing against, a scope like that at a similar stage typically commands $[range]. I'd like to see if we can get to $[specific target]."
25. How do data scientists and ML engineers negotiate?
AI/ML is commanding the largest premium in the current market. The shortage of qualified practitioners, combined with the business impact of AI features, means data scientists and ML engineers can negotiate more aggressively than general SWEs.
2026 benchmarks (remote, USD):
- Data Analyst: $55K–$90K
- Data Scientist (applied): $85K–$130K
- ML Engineer: $110K–$160K
- AI Research Engineer: $140K–$200K+
The key data point to cite: Levels.fyi shows ML Engineers earning 30–50% more than SWEs at the same level at the same company. If you are in this category, make that explicit in your negotiation.
Part 5: Negotiation Mechanics and Tactics
26. What is anchoring and how do I use it?
Anchoring is the tendency for humans to rely heavily on the first number they hear in a negotiation. Whoever throws the first number creates the reference point for everything that follows.
The application: when you have to give a number, make it high. Not unreasonable — but at the top of the market range, not the middle. If the band goes to $140K, you anchoring at $148K pulls the final number up. Anchoring at $120K "to seem reasonable" pulls it down.
Research shows that higher anchors produce higher final settlements even when both parties know the anchor is aspirational.
27. Why does silence work so well after making a counter?
After you state your ask, the psychological pressure is on the other person to respond. If you speak first to fill the silence, you are essentially negotiating against yourself — either justifying the number (which implies insecurity about it) or softening it (which implies you never meant it).
The recruiter or hiring manager is trained to wait you out. Be more patient than they are. State your number clearly, then stop. If ten seconds feels uncomfortable, remind yourself that it feels exactly as uncomfortable for them.
28. What is the "flinch" tactic and should I use it?
The flinch is a deliberate expression of surprise or mild disappointment when you receive an offer below your expectations. Used professionally, it is not theater — it is honest feedback that signals without confrontation.
Example: When a recruiter says "The base would be $90,000," a pause followed by "Hmm — I'll be honest, that's a bit lower than I was expecting based on my research" signals your position without rejection.
The flinch creates an opening. Recruiters often follow with "let me see what I can do" before you have even made a formal counter.
29. What is the "exploding offer" and how do I handle it?
An exploding offer has an artificial deadline: "This offer expires in 24 hours." Legitimate companies almost never do this. It is a high-pressure tactic designed to prevent you from gathering competing offers or doing market research.
How to respond:
Script:
"I want to approach this professionally and give it the attention it deserves. In my experience, strong companies allow candidates a few business days to review an offer thoroughly. I'd like [3–5 days]. Is that workable?"
If they hold firm on a short deadline, weigh the signal that sends about the company culture. Desperate urgency in hiring is a yellow flag.
30. How many rounds of negotiation is normal?
Two rounds is standard. Three is acceptable. After three rounds on the same dimension without movement, you are at the ceiling or the company will start to see you as difficult.
The structure typically looks like:
- Round 1: Your counter on salary/total comp
- Round 2: Their improved offer, your counter on one remaining lever (equity or signing)
- Round 3 (if needed): Final ask or acceptance
Do not re-open a dimension you already agreed on. Once you shake hands on base, the conversation moves to equity. Revisiting agreed terms damages trust and goodwill.
31. What is the "good cop / bad cop" recruiter dynamic, and how do I use it?
In some negotiations, the recruiter will say "I would love to get you more, but I'm not the decision maker — let me take this to the hiring manager." This is partly true and partly a tactic. The recruiter does need to bring your ask upward, but they also have more influence than they let on.
You can use this structure productively by making it easy for the recruiter to advocate for you internally. Give them the language they need to make the case.
Script:
"I completely understand — I appreciate you going to bat for me. The data point that might help is [Levels.fyi shows this level at $X, I have an offer from Y at $Z]. If it helps to have that in writing, I'm happy to share."
You are making the recruiter your ally, not your adversary.
32. Should I negotiate the job title in addition to comp?
Yes — title affects your career trajectory far more than it affects the company's budget. Titles determine your level at the next company, what roles you can apply for, and how quickly you can advance.
If the comp is capped but they have flexibility on title, pushing from "Engineer" to "Senior Engineer" or from "PM" to "Senior PM" often comes with a higher band range, access to equity refreshers, and stronger positioning for your next move.
Script:
"I understand you may have limits on the base salary at this level. I'm wondering if there's a path to the Senior [role] title — based on my background with [specific experience], I believe I'd be coming in and immediately operating at that level. Would that conversation be worth having with the hiring manager?"
33. How do I negotiate remote work terms, timezone flexibility, and equipment?
These are negotiable and often overlooked. For LATAM engineers, timezone overlap requirements can significantly affect which teams you can work with and the quality of your day-to-day experience.
Script for timezone flexibility:
"I want to make sure we're aligned on working hours. My productive window is [X to Y hours UTC-3]. Is there flexibility in how we structure overlap with the US team, or is there a hard requirement for East/West Coast hours?"
Equipment budget:
Most remote-first companies offer a home office stipend of $500–$2,000. If not mentioned, ask:
"Is there a home office or equipment budget included for remote employees?"
34. What is a retention bonus and when can I ask for one?
A retention bonus is a cash payment tied to staying at the company for a specific period (typically 1–2 years). It is different from a signing bonus and is rarely offered upfront — but you can create the conditions for one.
If you have been at a company for 2+ years and receive an outside offer, presenting that offer to your current employer often triggers a retention conversation. This is one of the highest-leverage moments for LATAM engineers who have built institutional knowledge.
Script (to current employer):
"I've been approached with an offer I want to be transparent about. It's meaningful financially. Before I consider it seriously, I wanted to have a direct conversation about whether there's a path to getting to [target comp] here. I'm genuinely invested in this team."
35. How do I negotiate a raise at my current company if I have no other offer?
Harder, but not impossible. The arguments that work:
- 1Market data — "Based on current benchmarks, my role at this level is paying $X–$Y. I'm at the low end of that range and I'd like to discuss catching up."
- 2Expanded scope — "Over the last year I've taken on [X, Y, Z] that weren't in my original role. I'd like to discuss whether my comp reflects the actual scope I'm carrying."
- 3Specific accomplishments — "I led [project] which resulted in [measurable outcome]. I'd like to tie that impact to my compensation."
Script:
"I'd like to request time to discuss my compensation. I've been tracking market rates for this role and doing an honest self-assessment of my impact here. I have some data I'd like to walk you through — can we schedule 30 minutes?"
Part 6: Common Mistakes
36. What are the most expensive mistakes tech candidates make in salary negotiation?
Mistake 1: Anchoring to current salary
When asked "what are you making now?", saying your number before knowing their range. Your current salary is irrelevant to market rate. Deflect this question.
Mistake 2: Giving a range when asked for a number
If you say "$110K–$130K," they will offer you $110K. If you must give a range, anchor the bottom at your real target.
Mistake 3: Apologizing for negotiating
"I feel bad asking, but..." is not a negotiation opener. It undermines your position before you make it. State your ask confidently and do not qualify it with apologies.
Mistake 4: Focusing only on base salary
The most common and most costly. At growth-stage and public companies, the equity component can dwarf the base salary difference you spent all your negotiating capital on.
Mistake 5: Bluffing about competing offers
Recruiters talk to each other. Comp benchmarks are visible at Levels.fyi. If you invent a competing offer and get caught, you lose credibility and potentially the real offer. Never bluff.
Mistake 6: Accepting too fast
Taking the first offer without even asking "is there any flexibility?" is leaving money on the table for zero upside. The worst they can say is no.
Mistake 7: Negotiating before you have the offer
Discussing comp expectations in the first recruiter screen before you have cleared technical rounds shifts the balance of power to the employer. Get the offer first. Then negotiate.
37. What language mistakes do LATAM engineers make when negotiating in English?
Being too apologetic: Spanish-speaking cultures sometimes use more hedging in professional conversations. In English negotiation, being overly apologetic ("I'm sorry to ask, but could we maybe...") reads as insecure and weakens your position.
Accepting an offer verbally before thinking: "Oh, that sounds great!" on the phone before you have processed the numbers. Train yourself to say "Thank you, let me look through everything and come back to you" as an automatic response.
Translating "I need" literally: "I need to earn more" sounds personal and emotional. "The market rate for this level is X" is professional and data-backed. Use market language, not personal-needs language.
Over-explaining: In negotiations, more words usually mean more risk. Say what you need, support it with one data point, and stop. Filling the silence with justification usually hurts you.
38. What do I say if the recruiter tells me the number I asked for "isn't in their budget"?
This often means it is not in their initial approval, not that the money does not exist. The budget is a proxy for approval authority, not a fact about company finances.
Script:
"I appreciate you being transparent. Can you help me understand what the process looks like for getting additional budget approved, and what information would help make that case? I want to work with you to find a path."
This repositions the conversation. You are asking them to help you solve the problem together, not arguing about the constraint.
39. What is the right way to decline a counter and hold firm?
If after two or three rounds you are not making progress and the number is simply too low, say so clearly and without drama.
Script:
"I appreciate all the time you've invested, and I have a lot of respect for the team. I want to be honest: the package, as it stands, is below where I need to be to make this move. I don't want to drag this out if we're too far apart. Is there any room we haven't explored? If not, I may need to withdraw my candidacy — and I genuinely hope we can work together in the future."
This does two things: it creates one last opening for a final push, and it closes gracefully if they cannot move. Never burn a bridge.
40. What do I do immediately after accepting an offer to set up my next negotiation?
Negotiation does not end at acceptance. Set yourself up for the next one:
- 1Get everything in writing — base, bonus target, equity grant with vesting schedule, signing bonus, start date, and any verbal promises about scope or title.
- 2Clarify the equity specifics — RSU number, cliff date, vesting schedule, current fair market value. Do not accept "you'll get equity" as a complete answer.
- 3Set a performance review date — if they cannot hit your target now but the role is right, ask for a 6-month formal review with a comp adjustment tied to defined performance milestones.
- 4Document your accomplishments from day one — every project, metric, and impact statement. Your next negotiation — internal or external — runs on this data.
Script for asking for a written summary:
"Before I send back the signed offer, could you send a written summary that includes the base salary, equity grant details, signing bonus, and the expected bonus target? I want to make sure we're aligned on all components."
Quick Reference: Scripts by Situation
| Situation | Opening Line |
|---|---|
| Asked for salary expectations before offer | "Can you share the comp band for this level? I want to make sure we're in the same range." |
| Received the offer | "Thank you — I'm excited. Can I have [date] to review it fully?" |
| Countering on base | "Based on market data for this level, I'd like to discuss getting to $[X]." |
| Base is maxed, ask for equity | "If base is at the ceiling, is there room to improve the equity grant?" |
| Base and equity maxed, ask for signing | "Could we look at a signing bonus to bridge the gap in year one?" |
| Have a competing offer | "I want to be transparent — I have another offer at $[X]. I'd rather be here. Is there room to match it?" |
| No competing offer | "I don't have another offer, but market data shows $[X]–$[Y] for this level. Can we get to $[X]?" |
| Pressure to decide fast | "I want to give this proper attention. Can I have [3–5 days]?" |
| Final answer before walking | "I appreciate everything. At this package level, I may need to withdraw. Is there any room we haven't looked at?" |
The Compounding Math: What Every $10,000 You Negotiate Is Really Worth
Most engineers think about negotiation in year-one terms. The real number is much larger.
If you negotiate $10,000 more in base salary at age 28:
- Year 1: $10,000 more
- By year 5 (with 3% annual raises applied to the higher base): $53,000 more in cumulative earnings
- By year 10: $115,000 more in cumulative earnings
- Next company offer is anchored $10K–$20K higher based on your current salary
- 401(k) matching (if applicable) is also higher
- Bonus targets (percentage of base) are higher
The $24,000 average gain from negotiating in tech is not a one-time event. It is a permanently higher floor that compounds for the rest of your career.
Final Notes for LATAM Engineers
The negotiation gap between LATAM engineers and their North American peers is not a skills gap. It is an information gap and a confidence gap.
You have already cleared the hardest bar: you passed a technical interview process conducted in English at a company that hires globally. The company wants you. The only question is at what price.
The scripts in this guide are not manipulation. They are the normal language of professional comp conversations in the US tech market. Every engineer at FAANG, every PM at a Series B startup, every data scientist at a growth-stage company uses some version of these scripts.
The engineers who negotiate do not get fired. They get respect and, on average, $24,000 more per year.
Use the scripts. Run the research. Make the ask.