I am a Senior Software Engineer at a tec
Ask
I am a Senior Software Engineer at a tech company in Boston, MA.
Over the last 9 months, my manager has continuously piled non-promotable "glue work" onto my plate: organizing and running bi-weekly sprint retros, taking and distributing all client meeting notes, onboarding 4 junior engineers, and covering standup when he is out.
This invisible coordination work eats up roughly 12 to 15 hours every week.
In our recent mid-year check-in, my manager told me: "You are doing great on team citizenship, but your core technical project output and P volume are slightly lagging behind peers, which might delay your Staff promotion."
I felt completely blindsided and demoralized.
Can you provide:
1. The exact speakable first line to open our 1-on-1 next Tuesday to formally re-scope and cap this invisible work (clear fact + concrete boundary + written agreement date).
2. The manager's most likely deflections ("We all have to be team players", "Nobody else has the bandwidth") and the exact follow-up comebacks.
3. A structured table / framework to inventory these invisible tasks against official promotion criteria so the trade-offs are undeniable?
Answer
Being told "team citizenship great, technical output lagging" after 9 months of stacking glue work is the classic set-up — the promotion case has to be untangled from the workload that's blocking it. Here's the meeting prep: the line, the comebacks, and an inventory tied to Staff criteria. Take the page to Tuesday.
**1. The line for Tuesday's 1-on-1 (Sept 22)**
> "Over the past 9 months I've averaged 12–15 hours a week on bi-weekly sprint retros, client meeting notes, onboarding four junior engineers, and covering your standups. To hit the technical output and P volume the Staff bar requires, I'm asking to reassign sprint retros, client notes, and onboarding to named owners by Friday Sept 25, and to cap my remaining coordination work at 4 hours a week. I need your answer in writing — a short email confirmation is fine."
**2. If he deflects**
| He says | You say |
| --- | --- |
| "We all have to be team players / this is good for your development" | "Team citizenship is one input. The Staff bar is technical scope and impact. I need protected time and named handoffs. By Friday, please tell me who takes sprint retros and client notes." |
| "Nobody else has the bandwidth" | "Then it's a hiring or priority call you need to make. I need written reassignments for retros and onboarding by Friday, even if the answer is 'we'll rebalance next quarter.'" |
| "Let's revisit after this sprint / next quarter" | "I'll agree to a review date. Please put it on the calendar now and confirm in writing that the 4-hour cap holds until then." |
| "You're doing great, this is just a small adjustment" | "Thanks. I still need a written yes or no on the handoffs and cap by Friday." |
**3. Invisible-work inventory vs. Staff criteria**
| Task | Frequency | Hrs/wk | Beneficiary | Current owner | Maps to Staff criterion? | eassignment / change |
| --- | --- | --- | --- | --- | --- | --- |
| un bi-weekly sprint retros | Every 2 wks, 1.5h each | ~1.5 | Whole team | Me (default) | No — facilitation, not a Sr/Staff bar item | otate to EM or Tech Lead |
| Take & distribute client meeting notes | 3–4 mtgs/wk | ~4–5 | Whole team | Me (default) | No — admin, not promotion work | ound-robin among attendees |
| Onboard 4 junior engineers | Ongoing | ~3–4 | Juniors + manager | Me (default) | Partial — mentorship yes, but at Sr scope, not Staff | Split across team; keep 1 mentee |
| Cover manager's standup | ~1×/2–3 wks | ~1 | Manager | Me (no credit) | No — substitutes for manager duty | eturn to manager or rotating lead |
| **Total** | | **~10–11** | | | | |
| Invisible hours | Capacity not on Staff-track technical output |
| --- | --- |
| ~10–11 hrs/wk | ~25–28% of a 40-hr week |
Staff-track criteria to verify against your company's leveling doc: Technical Impact, Scope, Leadership at Scale, Cross-team Influence. None of the four invisible tasks map to these at Sr/Staff level — that's the case to put in writing on Friday.
**Taking it with you:** 1on1-prep-2026-09-22-b3b5a4cd.pdf
**Limits:** The "Maps to Staff criterion?" column uses generic Sr→Staff-track language. Pull your company's actual leveling rubric and rewrite that column with the exact criteria before Tuesday — that's what makes the trade-off undeniable to *him*, not just to you.