The New Senior Hire Has No Ramp-Up Time

DEV Community

You're the new senior hire, and there's no ramp for that

👋 I'm Parsa Jiravand — I work in IT, and this is Best Practice. One article every day, one soft-skills episode every week. It all lives at bestpractic.org — come join us. It's your second week, and someone's just asked what you think the team should do about the deploy pipeline that everyone agrees is held together with duct tape. You don't know whose duct tape. You don't know if the last three people who tried to fix it got overruled, or burned out, or promoted somewhere else for trying. You have an opinion forming anyway, because that's the job you were hired to do, and you can feel the gap between how much you actually know and how much weight your answer is about to carry. That gap is the whole first month now, and it didn't used to be this wide. The job changed shape before you noticed For a long time, "new senior hire" meant someone who'd clear a short, forgiving runway — a few weeks to read the code, sit in on standups, get a feel for who actually makes the calls versus who just talks in meetings — before anyone expected an opinion that mattered. That runway is the thing that's gone missing. Hiring has leaned harder toward senior roles this year, and junior postings have thinned out alongside it, which means a lot of teams aren't backfilling a ladder anymore — they're hiring one person to be the judgment, directly, because there's no one two rungs down to grow into it. If you got the senior title, you weren't hired to eventually know how the system breaks. You were hired already knowing it, and the first month is everyone — including you — finding out whether that's actually true here, on this particular pile of decisions someone else made before you arrived. That's a different test than the one the title implies. "Senior" sounds like it's testing your judgment. What it's actually testing, for the first several weeks, is your judgment about a system you have none of the history for. Those aren't the same skill, and the gap between them is exactly the thing nobody warns you about when they hand you the title. What's actually happening underneath Here's the part that's uncomfortable to say out loud: the people around you are reading your first few answers as a referendum on whether the hire was right. Not consciously, mostly. But the first opinion you give in a room gets weighted more than the fortieth will, because it's the only data point anyone has yet. And the thing most people do with that pressure is try to prove the title immediately — have a strong take in week two, fix the thing everyone's been complaining about, show you were worth it. It reads as confidence. It's actually the single easiest way to spend credibility you haven't earned on a decision you don't have the context to be right about. The quieter problem is that nobody tells you this is happening, so you don't know you're being read at all. You think you're just answering a question honestly. The room thinks you're declaring your operating style. What works The move that buys you the most room, and costs you nothing, is asking the people who've been there what's already broken that nobody's fixed. Not "what should I know," which gets you a tour. Specifically: "What's the thing people here already agree is a problem, that just hasn't gotten prioritized?" That question does three things at once. It gets you the map, for free, from someone who's already drawn it — which is faster than re-deriving it from the codebase. It signals that you're looking for consensus before you push, which reads as judgment rather than ignorance, even though you're asking because you genuinely don't know yet. And it tells you, by what people say and what they visibly don't say, where the actual landmines are — the thing everyone agrees is broken but is also someone's project, or someone's old decision, or tied to a person who's still in the room. The second move is narrower, and it's about the first opinion you're asked for in a room full of people who don't know you yet. ...

Powered by Readybot.io