Job search
Your Current Employer Made a Counteroffer: Compare What Actually Changes
Compare the current job baseline with a documented counteroffer and the external offer; check which original reasons for leaving actually change.
Compare a current-employer counteroffer with both your existing job and the new offer. List each change, its approval status and its effective date. Then test whether those changes address the reasons you wanted to leave. A higher salary alone cannot tell you whether the work, manager or schedule will be different.
Start with the actual written terms and your original priorities. Keep verbal proposals and pending approvals visible as unresolved items. This guide uses public career and employer guidance checked October 23, 2026, plus two fictional cases; we reviewed no private offer and made no employment decision or contact. For separate opportunities, browse recent roles on LandOffer.ai.

Reconstruct why you were leaving
Write down your reasons before the counteroffer conversation changes the comparison. Be concrete: “primary on-call one week in three without a secondary” is more useful than “poor balance.” “No ownership of design decisions” is more useful than “no growth.” Record what would count as a meaningful change for each reason.
Indeed’s current-employer counteroffer guide, updated June 16, 2026, recommends reviewing the reasons behind your search and the duties attached to the proposal. Its guidance is a starting point for questions, not evidence of how your manager will behave. A counteroffer does not establish either long-term commitment or a plan to replace you.
Separate the facts you know about your present team from assumptions about the new one. You may have months of incident records at your current job and only an interview description of the new team’s rotation. Apply the same questions, while keeping the evidence quality different. “Written rotation supplied” is stronger than “recruiter said it is usually quiet,” but neither predicts future workload perfectly.
Avoid letting an appealing number erase a nonnegotiable requirement. Equally, do not reject a documented change simply because a general article says counteroffers always fail. Ask whether this proposal addresses your documented concerns under terms you understand.
Build three columns and label the evidence
Use three states: current job, current employer’s proposed changes, and new employer’s offer. The baseline shows which problems the counteroffer leaves unchanged. Copying a new salary into a two-offer sheet can conceal that continuity.
For each state, record base salary, any separate payment conditions, title and level, reporting manager, work scope, location, schedule and start or effective date. Add the document and approval status. Do not turn a proposed promotion into an approved role because a manager sounded confident. Ask who can confirm the change and whether an updated description or compensation notice exists.
Berkeley Career Engagement’s offer-evaluation guidance calls for comparing roles against the same priorities and obtaining missing benefits information. For a counteroffer, add an explicit “unchanged” finding. Existing benefits can remain relevant, but their continuation does not solve an unrelated lack of technical ownership.
Keep recurring base pay separate from a one-time retention payment. If the latter has service, repayment or other conditions, obtain the actual written terms before counting it as available compensation. This article does not determine their legal effect, taxes or enforceability. An uncertain condition belongs with an unanswered question rather than an invented financial value.
Completed comparison: more pay leaves the original problem open
Fictional case: Noah is a backend engineer at invented Cedar Systems. His reasons for searching were frequent unsupported on-call duty and limited architecture work. His new offer from invented Harbor Tools is not yet accepted. The following documents and conversations are stipulated teaching inputs, not real employer records.
| Decision field | Current Cedar job | Cedar counteroffer | Harbor offer |
|---|---|---|---|
| Annual base salary | $142,000 in current compensation record | $158,000 in an approved compensation notice | $154,000 in written offer |
| Separate payment | None supplied | $6,000 retention proposal; conditions not supplied | None stipulated |
| Level and title | Engineer II | Engineer II; manager mentions a possible senior review later | Senior Backend Engineer; written role description |
| Reporting line | Current engineering manager | Same manager | Named platform manager in offer |
| On-call arrangement | One primary week in three; no secondary in Noah’s recorded baseline | No written rotation or staffing change | Written one-in-six primary rotation with a secondary; actual future incident load unknown |
| Design responsibility | Implements designs owned elsewhere | Architecture participation discussed, no assigned deliverable | Written responsibility for an API migration design; review authority described |
| Timing | Existing terms | Base change effective November 1; promotion date unknown | Proposed start November 30; response due November 6 at 5 p.m. Eastern Time |
Noah’s completed change audit marks salary changed and documented, manager and level unchanged, rotation unresolved, and architecture ownership proposed without an assigned deliverable. Cedar’s $16,000 base increase is about 11.27% of $142,000. Its proposed annual base is $4,000 above Harbor’s. These calculations compare stated annual salary rates; they do not model taxes, payment timing or a full first year of earnings.
The $6,000 proposal stays outside that comparison because its conditions are missing. Noah does not describe the senior review as a promotion or assume that a later review will produce a particular result. Harbor’s clearer rotation and design scope are favorable evidence for his stated priorities, while its real operating conditions remain untested.
His finished decision memo reads:
Under these fictional inputs, Harbor remains my preferred option for final review because its documented duties and rotation better address my two original reasons for searching. Cedar has improved pay, but the available counteroffer does not document a change to those work conditions. I am not accepting either proposal in this exercise. My remaining questions are Harbor’s actual escalation support and Cedar’s proposed retention conditions. If Cedar later documented an approved change to the work scope, I would compare that revision separately.
This is a complete comparison with a stated preference and unresolved items. It does not assert that Noah should always leave, that Harbor will be quieter, or that Cedar acted in bad faith. The reasoning follows the supplied evidence instead of a prediction about retention.
Verify who can make the change effective
Employer approval processes differ. As one concrete employer example, UT Austin’s salary-adjustment page describes counteroffers through its base-pay-change process and requires documented offers supporting the action. That is UT Austin’s process; it does not require every technology employer to use Workday or request a competing offer letter.
Ask who approves the change, what document records it and when the revised terms take effect. A manager’s proposal, an HR approval, an effective compensation change and a later pay statement are distinct records. If a new title changes neither level nor duties, label that accurately. If additional responsibility is temporary, ask about its duration and the duties that remain after it ends.
A role change needs operational detail as well as a compensation number. For a transfer, identify the receiving manager, team, start date and work removed from the old assignment. For improved on-call support, identify the rotation owner and escalation coverage. For development opportunities, name the project, decision rights, review support and time allocation being offered.
Written terms make the proposal easier to inspect; they are not a guarantee of permanent workload, future promotion or continued employment. If a term involves a disputed agreement or a repayment obligation you do not understand, preserve the document and obtain appropriate advice before acting. Do not substitute a career article’s general wording for the actual agreement.

Independent clarification case: a transfer promise needs an owner
Separate fictional case: Leena is a data engineer at invented Quarry Analytics. Her main reason for leaving is a mismatch between her assigned support queue and the data-platform development work she wants. Her current base is $128,000. A new employer offers $138,000 with a platform-development scope, while Quarry’s manager proposes $140,000 and a transfer. Leena has accepted neither offer.
Her first record says “transfer proposed; receiving manager, allocation and effective date unknown.” She completes the following unsent clarification, addressed only to role placeholders:
To: Current manager and designated HR partner
Subject: Clarifying the proposed data-platform role and effective terms
Hello,
Thank you for discussing a counteroffer with me. My comparison currently records proposed annual base pay of $140,000 and a possible transfer from support work to the data-platform team. I have not treated the transfer as approved.
Please confirm the role title and level, reporting manager, transfer effective date, and the approval still required. Could you provide the updated responsibilities and specify whether my existing support queue will end or continue alongside the new assignment?
For the platform work, please identify the initial project, expected allocation, review support and success measures. Please also clarify whether the pay change depends on completing the transfer and whether any separate retention payment or repayment condition is involved.
My other offer currently requires a response by November 12 at noon Pacific Standard Time. Please let me know what written confirmation can be available before then. This request asks for clarification and does not communicate acceptance, withdrawal of notice or rejection of another offer.
Thank you,
Leena Example
The example then supplies an invented written clarification: HR confirms the $140,000 base and transfer effective December 1; the receiving manager is named; the role remains Data Engineer II; the support queue transfers to another team; the first project is a pipeline-reliability redesign with a documented review partner. No retention payment is offered. These are fictional replies, not messages we sent or received.
Leena closes four unknowns: approval owner, reporting line, effective date and removal of the old queue. She keeps future project load and team working relationships as uncertainties. Her audit now says “scope change documented,” rather than “manager promised better work.” The $2,000 annual base difference versus the external offer remains a separate observation.
Her completed memo is: “The stipulated counteroffer now addresses the work-scope reason I recorded before searching. Staying is my provisional preference under this case’s assumptions, subject to reviewing the final documents and reconciling the resignation status with HR. This conclusion would change if the support queue remained attached or the transfer were still awaiting approval.” It illustrates when new evidence can change the comparison without predicting success or deciding a real worker’s choice.
Keep deadlines and prior commitments explicit
Record the current employer’s response request and the external offer’s deadline separately, including timezone. Berkeley’s decision-time guidance recommends asking for an extension before the original deadline and notes that the employer decides whether to grant it. A request does not silently extend an offer.
Leena’s fictional noon PST deadline is 20:00 UTC on November 12, 2026. If she requests two additional days, her record must still show the original deadline until a revised one is confirmed. Neither a pending internal approval nor an unsent email pauses the external clock.
If you already accepted the new job, flag that commitment before treating the counteroffer as an ordinary open negotiation. Berkeley discusses the professional consequences of reneging in its student recruiting context. That guidance does not decide your individual contractual obligations. Review what you agreed to and seek appropriate help where necessary; do not use a holding acceptance merely to buy time.
Keep resignation status explicit as well: notice submitted, withdrawal requested, or employer-confirmed continuation are different entries. Record the actual acknowledgement rather than assuming that considering a counteroffer cancels the notice. No message in either example is an actual acceptance, resignation withdrawal or instruction to change employment records.
Save a dated comparison naming the documented changes, unchanged conditions, pending approvals and next decision deadline. If neither option fits your priorities, browse recent roles on LandOffer.ai and use the specific unresolved work condition to guide the next search.
Sources and Further Reading
Public full sources checked October 23, 2026. No paid service, private offer review, account action or employer contact was performed. Employer procedures and university recruiting guidance retain their stated scope.
- Indeed: handling a counteroffer from your current employer, updated June 16, 2026.
- Berkeley Career Engagement: evaluating offers.
- UT Austin Human Resources: salary adjustments and counteroffers, an employer-specific process example.
- Berkeley Career Engagement: decision timing and commitments.


