This. I've been at 32 hrs/week, in two senior SW engineering jobs (sequentially), for 5 years, with appropriate pay reduction. Many/most people I work with do

This. I've been at 32 hrs/week, in two senior SW engineering jobs (sequentially), for 5 years, with appropriate pay reduction. Many/most people I work with don't know I have a reduced schedule, since I take my off time in the morning before most of my colleagues have caught up on Slack (and my guess is they are not clocking in 40 hrs, even at 100% pay). I also contracted for 50-100% time, variable, for about ten years, and got important work done during this time. So it's possible to work very productively with less than a full time commitment. I'm at a stage in my career & life where money is less of a concern than time. My next move will definitely be to average less than 32 hrs/week (ideally 20). My preference would be to work at the same / a similar job and just scale back the salary and the hours, but suspect it will wind up as a series of stressful full-time jobs or contracts with gaps in between to recharge and work on personal things, petering out until I get sick of that rhythm and decide there is enough in the piggy bank. If it plays out this way, that's a shame, because I feel like I add more value to a team the longer I stay; and someone won't benefit from 30 years of experience for a lot less than a full time staff engineer costs. I can't change (much) the cultural things that cause this situation, but it gives me some hope to see it advocated for here.