🚀 Resource Lesson: Recruiter Phone Negotiation Scripting
Part 1: Resource Lesson (Deep Dive Theory)
1. 🎯 Executive Summary & Objectives
The goal of this module is to master the verbal communication required during initial phone screens and verbal offer calls with tech recruiters. As a Senior Software Engineer, your objective is to maintain leverage by gracefully deflecting early salary requests, framing your value around technical scope, and tactfully buying time to review verbal offers without committing prematurely. This requires C1/C2 level phrasing to project confidence and executive presence.
2. 🧊 Warming Up
Reflective Questions:
- Have you ever felt pressured by a recruiter to state your expected salary before knowing the full scope of a role?
- How do you usually respond when a recruiter says, “We’d love to offer you the role, are you ready to accept?”
Sample Answers:
- Yes, in the past I blurted out a number that was too low because I was caught off guard.
- I usually say thank you, but I realize I should explicitly ask for the total compensation breakdown in writing before showing too much excitement.
3. ⚙️ Contrastive Analysis & Theory
Negotiating on the phone requires a strategic framework, split into two primary phases:
Phase 1: Initial Screen (Deflection)
- Goal: Avoid naming a number first. Anchor on mutual fit.
- Formula: Acknowledge the question + Pivot to role scope / interview performance + Ask for their budgeted range.
Phase 2: Verbal Offer Call (Stalling & Appreciation)
- Goal: Do not accept on the spot. Express gratitude, validate the offer, and ask for time.
- Formula: Express immense gratitude + Request the offer in writing (Total Comp breakdown) + Propose a timeline to follow up.
4. 🛠️ Real-World Engineering Context Comparison
| Context / Situation | Junior / B1/B2 Phrasing | Senior / C1/C2 Executive Phrasing |
|---|---|---|
| Recruiter asks for salary expectations early | ”I am looking for around $150,000." | "Right now, my primary focus is finding a role where I can drive significant technical impact. I’m open to competitive market rates—could you share the approved range for this position?” |
| Recruiter presses for a number again | ”Well, maybe $160,000 is okay." | "I’d prefer to wait until we’ve both determined there’s a strong mutual fit. I trust that your team offers competitive compensation for this level of engineering scope.” |
| Receiving a verbal offer | ”That sounds great! I accept." | "Thank you so much, I’m thrilled about the opportunity to join the team. Could you please send over the written details outlining the base, equity, and sign-on so I can review the full package?” |
| Buying time to review | ”I need time to think." | "I appreciate the verbal offer. I always take a couple of days to discuss major career moves with my family. I’ll get back to you by Wednesday with any questions.” |
5. 🎭 Role-Play Dialogue
Scenario: A Senior Backend Engineer is on an initial screening call with a Tech Recruiter at a Tier-1 tech company.
Recruiter: “We’re really excited about your background with distributed systems. Before we move you to the technical screen, I need to check your compensation expectations. What number are you targeting?” Engineer: “Thanks, I’m also really excited about the architectural challenges your team is tackling. At this stage, I don’t have a specific number in mind. I’m more focused on the scope of the role and ensuring there’s a mutual fit.” Recruiter: “I understand, but I just need to make sure we’re in the same ballpark so we don’t waste your time.” Engineer: “I completely understand. Since I’m currently evaluating a few different opportunities, I’m looking for a competitive total compensation package aligned with the market. Could you share the approved salary band for this specific Senior engineering tier?” Recruiter: “Sure, the base band is roughly 210k, plus RSUs.” Engineer: “Thank you for sharing that transparency. That range sounds perfectly aligned with what I’d expect for this level of responsibility, and I’d love to move forward in the process.”
6. 💬 Let’s talk about the role play
- Why didn’t the Engineer give a number when first asked?
- How did the Engineer pivot the conversation back to the recruiter to get the salary band?
- Notice the tone of the Engineer—was it defensive or collaborative?
7. 📚 Bilingual Technical Vocabulary
| English Word | English Definition | Vietnamese Translation |
|---|---|---|
| Deflect | To skillfully avoid answering a direct question by changing the subject. | Chuyển hướng, lảng tránh khéo léo |
| Total Compensation (TC) | The complete pay package, including base salary, bonuses, and equity. | Tổng thu nhập |
| Leverage | An advantage or power in a negotiation (e.g., competing offers). | Lợi thế thương lượng |
| Equity / RSUs | Shares of company stock given as part of compensation. | Cổ phần / Cổ phiếu thưởng |
| Sign-on Bonus | A one-time payment given when an employee starts a new job. | Tiền thưởng ký hợp đồng |
| Anchor | The first number proposed in a negotiation, setting the baseline. | Điểm neo (mức giá khởi điểm) |
| Scope | The scale, impact, and responsibilities of the engineering role. | Phạm vi / Quy mô trách nhiệm |
8. 🚫 Common Anti-Patterns & Pitfalls
- Anti-Pattern 1: The Apologetic Deflection: Saying “I’m sorry, I can’t tell you my salary.” Correction: Be confident, not apologetic. “I’m prioritizing the role’s scope over a specific number right now.”
- Anti-Pattern 2: The Premature Acceptance: Saying “Yes, I’ll take it!” on the phone. Correction: Always ask for the written offer and time to review the Total Comp breakdown.
- Anti-Pattern 3: Focusing only on Base Salary: Forgetting that RSUs and bonuses make up a huge portion of tech compensation. Correction: Always speak in terms of “Total Compensation.”
💻 Practice Workspace: Recruiter Phone Negotiation Scripting
Part 2: Practice Workspace (Active Execution)
1. 🏗️ Scenario & Engineering Context
Context: You have just finished the final rounds of interviews for a Staff Software Engineer position. The recruiter calls you to deliver the good news. They say:
“We loved your system design interview, and the team wants to extend an offer. We’re looking at $180,000 base salary. How does that sound, and are you ready to accept?”
You know the market rate for a Staff Engineer with your experience is closer to $210,000 base, plus substantial RSUs. You do not want to accept on the spot, but you want to express excitement and keep the door open for negotiation once you see the full package in writing.
2. ✍️ User Practice Workspace
Your Task: Write exactly what you would say in response to the recruiter.
NOTE
Draft your response below:
3. 💡 Progressive Socratic Hints
Hint 1: Tone / Structure
Start by expressing genuine enthusiasm and gratitude. Validate the offer without committing to the numbers.Hint 2: Lexical Focus
Use phrases like "Total Compensation," "written breakdown," or "review the full package." Avoid saying words like "unhappy," "low," or "no."Hint 3: Grammar / Phrasing
Use future-oriented and collaborative phrasing: "Could you send over the written details so I can review...", "I usually take a day or two to look over..."📝 Assessment Exam: Recruiter Phone Negotiation Scripting
Part 3: Assessment Exam (C1/C2 Benchmarks)
❓ Section 1: Multiple-Choice Questions (MCQs)
1. When a recruiter asks for your salary expectations during the first call, the best C1/C2 approach is to:
- A. State a number slightly higher than your current salary.
- B. Say it’s confidential and you cannot share it.
- C. Pivot to the scope of the role and ask for their approved salary band.
- D. Give them your absolute minimum acceptable number.
Answer Key
**Correct Answer: C**. Deflecting the question professionally and pivoting to the role's scope while asking for the salary band maintains your leverage.2. Which phrase is the most appropriate when receiving a verbal offer over the phone?
- A. “That’s great, I accept!”
- B. “I need to see it in writing before I can say anything.”
- C. “Thank you so much! Could you please send over the written details so I can review the full package?”
- D. “That base salary is too low for me.”
Answer Key
**Correct Answer: C**. This expresses gratitude, validates the offer, and professionally stalls for time to review the complete package.3. What is the primary reason you should not give a number first?
- A. To make the recruiter angry.
- B. You might anchor yourself too low and leave money on the table.
- C. You don’t want to pay taxes on a higher amount.
- D. It’s illegal.
Answer Key
**Correct Answer: B**. The first number thrown out sets the anchor. If you state a low number, the company will likely match it, costing you potential compensation.4. When a recruiter presses you for a number for the second time, you should:
- A. Apologize for being difficult and give a number.
- B. End the call.
- C. Reiterating your focus on mutual fit and trust in their competitive compensation.
- D. Give a massive, unrealistic number to scare them.
Answer Key
**Correct Answer: C**. Holding your ground politely and reiterating your focus on the role and trust in their market competitiveness shows executive presence.5. Total Compensation (TC) typically includes:
- A. Base Salary only.
- B. Base Salary and health insurance.
- C. Base Salary, Equity (RSUs/Options), and Bonuses.
- D. Equity only.
Answer Key
**Correct Answer: C**. TC is the sum of Base Salary, Equity, and any bonuses (target bonus, sign-on bonus).🧪 Section 2: Fill-in-the-Blank Technical Drills
- “Right now, my primary focus is finding a role where I can drive significant technical ________.”
- “I’m open to competitive market rates—could you share the ________ salary band for this position?”
- “Thank you so much, I’m ________ about the opportunity to join the team.”
- “Could you please send over the written details outlining the base, ________, and sign-on so I can review the full package?”
- “I trust that your team offers ________ compensation for this level of engineering scope.”
Answer Key
1. impact 2. approved 3. thrilled 4. equity 5. competitive🔍 Section 3: Error Identification & Sentence Refactoring
Identify the error in tone, grammar, or strategy in each sentence, and rewrite it to meet a C1/C2 executive standard.
- Error: “I want $150,000 for this job.”
- Error: “Sorry, but I don’t want to tell you my salary expectations yet.”
- Error: “Yes, I will take the job for $180,000.”
- Error: “I need time to think about this offer.”
- Error: “What is the base salary you can give me?”
Answer Key (Suggested Refactoring)
1. "I'm looking for a competitive total compensation package aligned with the market for this level." 2. "Right now, I'm more focused on ensuring there's a strong mutual fit and understanding the technical scope of the role." 3. "Thank you for the verbal offer, I'm thrilled. Could you please send over the written breakdown so I can review it?" 4. "I appreciate the verbal offer. I typically take a couple of days to review major career moves; I will get back to you by Wednesday." 5. "Could you share the approved compensation band, including equity and bonuses, for this position?"🗣️ Section 4: Real-World Scenario & Short Answer Roleplay
Prompt: You are on a phone screen for a Principal Engineer role. The recruiter asks: “We really need to know your salary expectations before proceeding to the technical interviews. Can you give me a rough range?”
Write a 2-3 sentence response that deflects the question, maintains a positive tone, and asks for their budget.
🏆 Section 5: Model C1 & C2 Executive Script Benchmarks
C1 Level (Senior Software Engineer):
“I’m incredibly excited about the prospect of joining the team and tackling these scaling challenges. At this point, I don’t have a specific number in mind, as I’m prioritizing the scope of the role and team fit. Given the market, I’m looking for a competitive total package. Could you share the budget you have allocated for this level?”
C2 Level (Staff/Principal Architect):
“Thank you for the transparency. My primary driver right now is finding an environment where I can drive architectural alignment and mentor a growing team. I’m actively evaluating a few opportunities and am confident we can align on compensation if the mutual fit is there. To ensure we’re calibrated, could you provide the approved compensation band—including base and equity—for this specific scope?”
📊 Section 6: CEFR C1/C2 Self-Assessment Evaluation Rubric
| Criteria | B1/B2 (Needs Work) | C1/C2 (Executive Level) |
|---|---|---|
| Deflection Strategy | Gives a number or apologizes for not giving one. | Confidently pivots to scope, fit, and requests the salary band. |
| Tone & Presence | Defensive, uncertain, or overly eager. | Collaborative, calm, grateful, yet firm on reviewing written details. |
| Vocabulary | Uses simple terms (“money”, “pay”, “want”). | Uses precise terms (“Total Compensation”, “approved band”, “equity”). |
| Buying Time | Accepts verbally or asks for “time to think”. | Expresses excitement, requests written breakdown, and sets a follow-up timeline. |