I am a mid-level software engineer. Over
Question
I am a mid-level software engineer. Over the past two quarters, I've spent ~30% of my time on uncredited team glue tasks (onboarding interns, writing documentation, coordinating release retro logistics) while peers focus exclusively on tier-1 feature code.
In my 1-on-1 this Thursday, I want to formally request project realignment.
Can you provide:
- An exact, speakable first-line opening for Thursday (Facts + Specific shift + Date for written confirmation)?
- The most probable deflection ('You're just so good at communication, we need you on this') and the exact response?
- A clear table mapping current invisible tasks to the requested realignment?
Answer
"Over the last two quarters about 30% of my time has gone to onboarding, docs, and release retro coordination — all uncredited. I'm asking to reassign those three starting next sprint, with a named owner for each, so I can return to tier-1 feature work alongside my peers. I'd like a written answer on the reassignment and a start date by [date]."
If they say: "You're just so good at communication, we need you on this."
That's a reassurance deflection — flattering, but it skips the decision. The exact reply:
> "I appreciate that. I'm still asking for a specific decision: reassign those three tasks, or formally credit them, with a written start date by [date]."
If they push again ("but who else could do it?"):
> "That's what I'm asking us to figure out by [date]. Please give me a named owner per task, or a date we'll decide together."
Mapping your invisible work to the request
| Task | Frequency | Time cost | Who benefits | Current attribution | equested |
|---|---|---|---|---|---|
| Onboarding new interns | each cohort (~quarterly) | [hrs per cycle] | New hires + manager (visibility, retention) | Implicit, on me | swap: H-led onboarding or rotating engineer |
| Writing team documentation | weekly | [hrs per week] | Whole team + future hires | Implicit, on me | swap: docs owner rotation; credit: named in goals |
| Coordinating release retro logistics | per release (~monthly) | [hrs per release] | Whole team + release captain / PM | Implicit, on me | swap: release captain or PM owns |
Before Thursday
- Fill in the `[hrs ...]` cells with your best estimate so the "30%" claim is anchored, not round-numbered.
- Pick a written-answer date about a week out for `[date]` — that's the only placeholder that changes what you'll actually say out loud.
Want me to tighten the opening to under 30 seconds for the live 1-on-1, or is this length fine?