Well I have a lot of experience with 16 hour/day work weeks (have worked at banks most of my life). Yeah, you're right, it's not fun. It really comes down to the time-sensitivity of your work. For someone in their 20s, I think the perfect balance is less than 80 hours/week but more than 40-50. If you're being paid two standard deviations over US median household income ($120k+), you're going to be expected to put som…
Ask HN: 16-hour work week jobs?
21–30 of 267 posts
Re: Ask HN: 16-hour work week jobs?
#22Re: Ask HN: 16-hour work week jobs?
#23> I sincerely think it is quite unrealistic to ask a knowledge worker consistently deliver at full throttle for 40 hours every week (never mind the enslaving 60+ hours on many companies)
I really disagree with this. Have you tried before?
Re: Ask HN: 16-hour work week jobs?
#24I do find it difficult to progress in my career, however. I've been trying desperately to transition into a full-stack, part-time position, but I feel pretty stuck as a senior level front-end dev. In my experience, this is because I need some weight to throw around when I request working only part-time.
Re: Ask HN: 16-hour work week jobs?
#25Re: Ask HN: 16-hour work week jobs?
#26For most people I know, myself included, you're at your best productivity before lunchtime. Afterwards you might get a few bits and pieces done, but generally it's a waste of time.
Re: Ask HN: 16-hour work week jobs?
#271. A. In my experience it's hard to find unless you're contracting or have extremely rare knowledge.
1. B. We're a rails shop, (mostly) b2b edtech.
2. Not at all just greenfield. Having flexible schedules means that you have to be realistic with scheduling and expectations. You have to work out what will work best with the team and when they need to synchronize with you.
In some cases your work is orthogonal to main development critical paths, so the need for synchronization is less (still important though for staying synced with the culture).
Re: Ask HN: 16-hour work week jobs?
#28People are probably willing to pay you to do this, but not advertising it so much. Most tech companies (at least in the US) are desperate for work. Less than 40 hours is a week is a tough sell because many people feel the onboarding process eats up a lot of time. Primarily, since it's the norm to work 40+ hours (and believe me, it's not difficult to do this and be actually writing code more than 50% of the time) empl…
Re: Ask HN: 16-hour work week jobs?
#29I have been working as a high tier network engineer for the past few years for 40 hours per week (but always looks to go out on my own with a startup idea). I'm starting to really find that 40 hours per week make no sense and i'm actively going to try to find alternatives. Life slips by and there is little point in spending 1/3 of your working day dealing with monotonous bullshit.
If I was working somewhere I was 100% passionate about, I would have no problem working 1/3 of my life. But, it's rare to find a position that completely matches one's values and professional desires.