Pivotal has nearly 100% of developer time spent pairing. This requires entire teams to be in sync on in/out and lunch schedules, else there will be non-pairing time. That's not the end of the world, but most teams don't have code review, favoring the live review of paired development. While at Pivotal, I did observe the rare team with an 8AM start instead of 9, but as far as I know everyone opted into being on an alternative schedule, and it was for out-of-time-zone client work to enable better communication with the client.

I imagine there can be exceptions. The rules are meant for productivity - if someone is more productive on a slightly different schedule I imagine they'd be for it, assuming their actual motivations are honest with their claims.

I'm the only one at my company who comes in several hours before opening hours. I also leave several hours before closing. I made a personal request for this and my company obliged.

Ironically, I'm writing this nearing midnight on a Sunday...from work.

E:

@ezl

I'm pretty sure the point of the parent's question was an implied: "If I was an employee there, how would this work for [people like] me?"

it doesn't. companies don't need a system that works for everyone. they need a system that works for their employees.

that early is fine if you don't have kids... or have kids who start school at some stupid time like 7am.... my kids don't start school until 8:50... so starting before 9 is completely unrealistic unless i get a massive pay rise to cover child care for 2 kids before school 5 days a week

Similar for me. My energy buildup starts at 12:00 and peaks at around 19:00-20:00 so I start as late as possible and try to put as much meetings as possible in the morning.

The simple answer is don't work there.

Maybe it doesn't have to work for you? It's a team sport.