>>wfwefw+J3
I suspect that that's very team-dependant (in a company with thousands of engineers in tens of offices, most things are). Personally I got promoted based on debugging / code cleanups / reliability work, and I don't remember the last time I worked outside my self-assigned working hours (~10am-6pm) (Aside from on-call shifts, where I got one false-alarm on a weekend a few weeks ago). If one of my teammates messaged me asking for code review at midnight and it wasn't a "the site will be down if this doesn't land right now" issue, then I'd reject their code on the basis that we should all be in bed :P
My understanding of the "get promoted or leave" thing is "engineers hired as juniors are expected to get to mid-level in under 5 years (with a half-way milestone at 2 years)"; once you're mid-level it's up to you if you want to carry on climbing. Personally once I got there I switched to a "work more efficiently in fewer hours and keep the same overall productivity" approach instead of trying to get promoted into the senior levels, and that's worked out nicely so far :)