I am a software engineer (Mid-level, cur
Ask
I am a software engineer (Mid-level, currently $125k base) at a mid-sized tech company in Chicago, IL.
6 months ago, my engineering manager told me in our 1-on-1: "Lead the redesign of our core ingestion pipeline, take over sprint planning, and mentor the two junior engineers, and I'll submit your Senior Engineer promotion ($150k target) in the Q3 cycle."
I stepped up, successfully delivered the pipeline migration on time, ran sprint planning, and spent 10+ hours a week mentoring the juniors.
In our review yesterday, my manager rated me "High Performer", but said: "Due to headcount and budget freezes, we could not push the title change through this round. Keep up the exact same momentum and we will look at it again in the Q1 cycle (6 months away)."
I feel strung along. Operating at Senior scope with mid-level compensation without written guarantee is unsustainable.
Could you provide structured, speakable workplace scripts for:
1. The 1-on-1 opening line: A direct, professional line requesting written confirmation of promotion criteria and an effective date by next Friday.
2. The pushback script if they stall ("budget is uncertain"): How to firmly reset scope back to mid-level expectations (stepping back from sprint planning and extra mentoring) without sounding combative.
3. A written email summary to send immediately after our 1-on-1 to document the discussion.
Answer
"Thank you for yesterday's rating. In March you set the path to Senior Engineer — pipeline redesign, sprint planning, mentoring the juniors — with submission in the Q3 cycle at a $150k target. I've delivered all three. To keep operating at this scope, I need written confirmation of the promotion criteria and a firm effective date by next Friday."
**If they stall on budget / headcount:**
"I appreciate the constraint, and I want to be honest about mine. The senior scope I took on in March — pipeline ownership, sprint planning, the mentoring hours — was tied to the promotion timeline you set. Since that's not in place, I need to step back to mid-level scope starting [date]. I'll stay on for two weeks to hand off the juniors and the planning cleanly, then transition out. I'd rather do a clean handoff than keep absorbing a senior role at mid-level pay without a written timeline."
**Send the same day — written summary email:**
Subject: Summary of our 1-on-1 on [date] — Senior promotion path
Hi [Manager],
Thanks for the conversation today. I'm writing to capture what we discussed so we're aligned.
**What we agreed in our March 1-on-1:**
- Promotion criteria to Senior Engineer: lead the ingestion pipeline redesign, take over sprint planning, and mentor the two junior engineers.
- Title and base compensation change ($150k target) to be submitted in the Q3 review cycle.
**Where we landed yesterday:**
- I was rated High Performer.
- Q3 promotion submission did not happen, attributed to headcount and budget freeze.
- You indicated the promotion would be revisited in the Q1 cycle, ~6 months out.
**What I'm asking for in writing by Friday, [date]:**
1. The criteria for the Senior promotion (title + compensation change).
2. A firm effective date.
3. If a firm date isn't possible, a written alternative timeline with the scope we'd both agree to.
**What I'm committing to:**
- Continuing current scope through the answer deadline.
- A clean handoff if we agree to step back to mid-level scope.
Please reply with any corrections to this summary, or with the written confirmation by Friday, [date].
Best,
[Your name]
---
Six months of senior-level work without a written timeline is the right reason to ask for this in writing. If the written answer doesn't come by Friday, treat that as the answer — and the scope reset in script 2 is what keeps the situation sustainable, not a threat, just the honest move. Other stalls ("let's revisit later," "we'll see how Q1 plays out") need their own short redirect, not the budget script.