A compensation table arrives, but you cannot tell which parts recur. Pressure to accept or counter bluntly makes a careful reply harder. Give each email one job: clarify the components, make one evidence-backed revision request, or record the final decision. Use 100 fictional compensation units only to compare the components, then replace them with your written terms rather than market assumptions. For broader preparation, see Resume & Interview Preparation.
Prepare the negotiation in 90 minutes before opening a draft email
Session A takes 55 minutes: 25 to audit the offer, 20 to collect evidence and 10 to choose one priority, target and private floor. Session B takes 35 minutes: 20 to draft and 15 to edit. The checks are 25 + 20 + 10 = 55, 20 + 15 = 35, and 55 + 35 = 90.
If time is short, use a 45-minute minimum: 15 for the audit, 10 for evidence, 10 for writing and 10 for checking. Request an extension only if the deadline is unclear or unworkable.
Component | Fictional units | What to clarify |
|---|---|---|
Fixed | 72 | Recurring |
Target variable | 12 | Earning rule |
Joining bonus | 8 | Payment and clawback |
Benefits | 8 | Cash status |
The total is 72 + 12 + 8 + 8 = 100 fictional units. The fixed target is 80 and the private floor is 76 if other terms remain unchanged.
Hypothetical evidence: Graduate Software Engineer; Java, SQL and REST APIs; 6-month backend internship; 3 shipped API modules; 18 passing integration tests. Replace these details. Evidence must match the submitted resume and remain defensible, as the fresher resume guide explains.
Ask for clarification without negotiating in the same email
When recurring and one-time components are unclear, ask facts first. Mixing four questions with a counter obscures the reply. Keep the email within 90 to 120 words and use the existing thread unless asked otherwise.
Subject: Clarification on Graduate Software Engineer offer
Dear [Recruiter Name],
Thank you for sharing the written offer for the Graduate Software Engineer role. I remain interested in the opportunity and would like to clarify four points before I respond:
1. Is the 12-unit variable amount a target, and what determines payout?
2. When is the 8-unit joining bonus paid, and does a clawback apply?
3. Which items make up the 8 benefits units?
4. When is the first compensation review?
Once I have these details, I will send my response by our already agreed deadline, [Deadline].
Regards,
[Candidate Name]
A useful reply supplies a term, date or policy reference. If partial, ask only the remaining question. Do not add a counter, expense story or competing-offer claim.
Request one specific revision after the components are clear
Recurring target is 72 fixed + 12 variable = 84 units. Requesting 80 fixed while retaining the variable gives 80 + 12 = 92 units. The 8-unit bonus with a 12-month clawback and 8 benefits units stay outside this recurring comparison.
Subject: Compensation revision request: Graduate Software Engineer
Dear [Recruiter Name],
Thank you for clarifying the offer components. I remain very interested in the Graduate Software Engineer role. My 6-month backend internship, work on 3 shipped API modules, and hands-on use of Java, SQL and REST APIs align closely with the advertised responsibilities.
Would you be able to revise the fixed component from 72 to 80 units while retaining the clarified variable terms? I believe this focused revision better reflects the relevant experience I would bring to the role. I would be happy to discuss the structure and understand what may be possible.
This is my primary request for the offer.
Thank you for considering my request.
Regards,
[Candidate Name]
Use only true evidence and actual offer values. If fixed pay cannot move, ask once for a written review after 6 months instead of 12, with written criteria. Do not stack pay, bonus, location and title requests. Rehearse a call with the HR interview questions and answers guide.
Use one response map for yes, partial yes and no
Compare each written response with the private 76-fixed-unit floor:
At 80 fixed + 12 variable fictional units, verify the revision and move to acceptance.
At 76 fixed + 12 variable fictional units, the floor is met. Check that every other term is unchanged.
At 74 fixed + 12 variable fictional units, the result is below the floor. Use the one written-review fallback or decline.
At 72 fixed + 12 variable fictional units, do not resend the same counter in different words. Decide using the role, learning, location, risk and alternatives.
The floor stays private. State the request, never “my minimum is 76”. New facts may change your decision; an invented offer or deadline should not. For any verbal change, request an updated letter or an email naming the revised component. A later-action promise is not a written revision.
Accept only after the revision is written clearly
Compare versions: name, title, location, fixed and variable components, bonus conditions, joining date, probation, notice terms and deadline.
Subject: Acceptance: Graduate Software Engineer offer
Dear [Recruiter Name],
Thank you for sharing the updated offer. I am pleased to accept the Graduate Software Engineer role with the written joining date of [DD Month YYYY]. As recorded in the revised document, the compensation includes 80 fixed units, 12 target-variable units, and an 8-unit joining bonus with the stated 12-month clawback.
Please let me know which documents or onboarding steps I should complete next. I look forward to joining the team.
Regards,
[Candidate Name]
Do not add a new request. If a change was confirmed on a call, recap it and wait for the revised document before accepting.
Decline without arguing, oversharing or closing the door unnecessarily
A final written proposal of 74 fixed + 12 target-variable fictional units is below the private 76-fixed-unit floor. Do not mention that floor, expenses or negotiation history.
Subject: Regarding the Graduate Software Engineer offer
Dear [Recruiter Name],
Thank you for the offer and for the time you and the team invested throughout the process. After careful consideration, I will not be able to accept the current compensation structure.
I appreciate the conversations and the opportunity to learn more about the Graduate Software Engineer role. I wish you and the team well.
Regards,
[Candidate Name]
Do not criticise, threaten complaints or invent another offer. Reassess a materially revised written proposal. Otherwise, close professionally.
Short version: choose the email that matches the stage
Use this six-step sequence:
Audit recurring, one-time and non-cash components.
Collect 2 to 3 defensible evidence points.
Clarify before countering.
Make one request.
Use a private floor.
Accept or decline after final terms are written.
Send-check: one purpose, one primary request, no more than 4 clarification questions, a subject naming the role or purpose, and 60 to 140 words. Check names and figures twice, then read aloud calmly. These are editing targets, not universal employer rules.
Now create a private four-row table with your real fixed, variable, one-time and benefits components. Draft clarification in 15 minutes, then wait for facts before drafting a revision. Keep confidential details out of public tools and shared documents.
After your draft is ready, the Interview & Resume Preparation Course offers structured resume work, technical and HR preparation, one-to-one resume review and mock interviews. Treat it as optional preparation: it cannot guarantee a salary revision, shortlist or placement.
