[MattGaiser]

I would be interested in knowing how much a WFH preference correlates with how much engineering teams work together.

As I have never worked for an engineering team that did anything other than parcel out work and expect people to go and do it. Yes, there was some pair programming for tough parts and we do architecture together, but as a general rule I don't meaningfully talk to any other engineers for completing my features except maybe to ask 10-20 minutes of questions.

So the "working together" part to me mostly consists of me being in a meeting which is not all that technical and where I don't care what the decision is. I have far more hours sitting in meetings playing on my phone than I have genuinely engaged in collaborative development.

But on the other end you have companies like Pivotal which are 100% paired code writing.

[orwin]

I'd say that if you're an ops/devops/architect, you need to work between 20% and 60% of your time with someone else. If you're a dev, i think roughly 20% is quite enough (unless you only do peer programming).