spent 6 years at big tech. saw a lot of promo cycles. here's what usually happens when someone gets denied and is given a vague reason.
the actual reasons, in rough frequency order your manager didn't sponsor you hard enough. they put your name in but didn't fight for you when someone else's sponsor pushed back. 'great IC, maybe next cycle' is easier than going to bat. calibration stack-ranking cut you. you were 5th in a group where only 4 get approved. nothing about your work changed. the number just didn't work out. the comparison class. promotions from senior to staff aren't decided in isolation. they're decided relative to who else is being considered. if there are two people with stronger packets, you're third. you actually don't have the scope yet. this one is real but managers rarely say it cleanly. 'impact' is a proxy for scope. if your projects are all self-contained and none crossed team boundaries, you probably didn't hit staff-level expectations regardless of how well you executed. a skip-level you've never talked to had a neutral or vague impression. calibration runs up the chain. your manager's opinion matters less than you think if their manager doesn't have a strong signal on you.
what to do with this
ask your manager a direct question after a denial: 'when you were in the room advocating for me, what was the main objection?' most managers won't volunteer this but will answer it if asked directly.
if they say 'the bar is high' or 'timing wasn't right,' that's not useful. push: 'what evidence would have changed the outcome?'
if they can't answer that, find a new manager. not kidding. a manager who can't articulate the promotion criteria is one who can't help you get there.
one more thing: the feedback you receive after a denial is often post-hoc rationalization, not the actual cause. treat it as a data point, not a verdict.