[sean2]

I think you misunderstood the parent posts. It's that your impact on a particular project doesn't become visible for a few years. If you think you quit after delivering your project near to budget and timeline, then you're left thinking you did a pretty good job, but only later is it possible to see if your architectural decisions are easy to maintain; if your API is easy to use; etc. The Senior Roles are supposed to have grown in knowledge about how all their decisions play out over a long time period, but if they've never stick around to observe the consequences of their decisions, then that might lead a recruiter to suspect whether they have learned what a Senior would be expected to know.