I'm in a similar situation, so I guess I can answer. I start in a new role soon and particularly requested a team with no more than 1 day wfh/week. I work in a

I'm in a similar situation, so I guess I can answer. I start in a new role soon and particularly requested a team with no more than 1 day wfh/week. I work in a applied ML and really, the technical aspects of the jobs are the 'easiest', ie. most well defined. In most cases focus + time will be sufficient for me to produce technical work. However, the real challenges lie at the intersections of models, infra, code, product and users. The goal is rarely is to build the best solution, it's to build the right solution. Solutions to these can only be found by collaborating with people who own each specific part. Intense whiteboarding, pair programming, brainstorming, etc were the most interesting parts of my job. All of them have been reduced to a shadow of what they were during remote work. Also, if I'm going to spend 50% of all my waking hours with a group of people, then I better like spending time with them. Being cooped up in a room my myself all day isn't fun at all. (and I have a huge community outside work, but it I don't like waiting for the other 50% to enjoy it) My coworkers are my good friends and if they weren't then I'd go somewhere else. (not drinking the Koolaid. I have no allegiance to corporate, just my nuclear peer group) A 'flexible or remote-optional team' is a lie. Remote and in-person are diametrically opposed office cultures. Both require very different cultural traits to flourish. Ones that try to stay on the fence will inevitably converge into one of the two or end up as a complete disaster. ( coordinated 3 days at work, 2 days at home etc can work...but that's just at-office culture with benefits)