Would senior engineers be interested in working reduced hours or part time?
What are peoples thoughts on this idea? Is this type of thing something that you've seen at other companies, or would be of interest to see at a company?
What are peoples thoughts on this idea? Is this type of thing something that you've seen at other companies, or would be of interest to see at a company?
Years ago, I was in need of a big a salary adjustment, and I offered to work for 3 days at the same pay, and the owner said yes. We were both very satisfied with this arrangement. He kept me and I was still productive, and I had more time to pursue other interests.
I think offering benefits to part-time employees is optional here. Curious about your experience with this.
So a 30-ish hr workweek would be the most beneficial to the employee.
Tried it. It only really works if the developer’s tasks are very independent of the rest of the team.
Basically, if the employee already functions in the same way as an independent contractor or consultant working on an isolated project, shrinking their work hours isn’t a big deal.
But when you have someone working as part of a team and interacting with the rest of the company, it quickly becomes a huge burden for everyone else to work around their schedule. Way too many instances of needing a response or bug fix from someone but they don’t work for several more days, so the team has to do it themselves if they want to make progress. This ends up sorting all of the easier, non-urgent work to the part time person while the time-sensitive work is always stuck to other team members. Great for the reduced hours person, not great for everyone else.
If the company’s work falls into the corner category, it’s easy. If the company’s work is in the latter category (more common) then it ends up being kind of terrible for everyone other than the person who gets reduced hours.
It works for my team as well, so it’s definitely doable.
I'm so freaking burned out. I need some time to get my life back to a comfortable pace, and I constantly consider fully quitting my job, but that seems too drastic.
More importantly, I don't want to 100% stop working because I actually do love working. I just can't figure out how to care for my family, my mental and physical health, and put in 40+ hours at my job.
(Seniority wise, I've got 18 years of experience across many aspects of the industry and I've fought to remain an IC rather than take on management roles, certainly to the detriment of my career growth)
I'm already on a "reduced 30 hr/week expectation" but just submitted notice of needing leave, drastically dropping to reduced part-time hours, or parting ways.
I'd love to hear and learn more about you. You might be a fit for my current employer. Shoot me an email found in my profile if you're interested.
I'm lucky to be in a flexible enough environment and proven myself as an IC who manages themselves, projects and clients reliably.
To the point of the OP: you can't take care of things in your life while working like that. I also think of quitting entirely, simply to take care of myself and others around me. Nobody can or is doing it, and nobody will be able to unless one of us gets out first and can set some kind of force in motion that builds up everyone around us.
You might be in a bubble.
Working more than 40 hours per week is not common at typical companies across the US, no matter what the internet says. If you’re doing the hustle and grind in Silicon Valley or Seattle or NYC then you’re going to be working long hours, but there are many more jobs that don’t require anything like that.
Speaking as an infosec practitioner, we’ve built functions with this model where we have infosec folks as subject matter experts (architecture, appsec, IAM) providing guidance on a 4 day work week. Great perk versus comp and benefits alone, and usually attractive to talent at later stages in life who are optimizing for QoL versus total comp.
I've been passively looking for a job. Job hunting is a slog for me, and I'm not interested.
But seeing this list, I've suddenly perked up. This is exciting.
In the US one could offer comp for health insurance equivalent partial value, or go the other way and carry full health insurance with the part time salary reducing. Or maybe this whole situation favors a setup in nations w/ universal healthcare.
I've had a couple of ostensibly full-time jobs which worked this way in practice - smaller shops, who couldn't compete with big-tech salaries, but happily paid their full-time rate for my expertise and availability, even though they only had a couple days of actual work for me to do each week.
It may not have been intended like this, but an 'experienced senior engineer' can also be a 'freelancer/contractor'. The post doesn't make it sound like that.
You want someone to be part of a 'team' - that'll totally be up to how you interact with someone, not their tax/corp status. If you want to be paying someone senior to help on multiple projects, advise on broader topics, etc., by all means get that. But if the person doesn't want to be in a W2 relationship with you, do you pass them over because of that?
My own experience has shown that to be untrue. I've known plenty of contractor folks who 'care' (however you might measure that) and deliver as much as or more than many employees.
It would need to have a compensation package that incentivizes people to truly just be part-time for you and not seek out side contracts - decent pay and benefits, etc.
[1] - https://meta.stackexchange.com/questions/66377/what-is-the-x...
consultant is very broad. i worked as a consultant for some clients, and it is nothing like the post describes. sure, the described position could be called a consultant, but describing it as a "guru" is much more descriptive and makes clear what they are actually looking for.
I know that I am very privileged to be able to work as I do in my career, and I've worked in warehouses, janitorial duties, etc. so I know how hard it can be to do those kinds of jobs where there isn't the ability to get the same job done in less hours; although I do have to say if you told a warehouse worker at the warehouse I worked at "get X number of pulls done, safely, then go home and I'll pay you for the day anyways" I would imagine they could be working for ~4 hours a day as well (there's a lot of down-time at some of those jobs, due to the fact there is no reason to be quicker). Only on the manufacturing floor where I worked do I think you'd really have to work the full 8-10 hours to get the number of units built, but in that case there was definitely room for process improvement.
This is definitely of interest. In my experience, companies generally derive significant "senior engineer" value for a handful of things but then their time winds up being consumed by a lot of other "this could have been an email/automation tool/non-senior" tasks. If you are in a position to allow a senior engineer to focus on their significant value adds to the company and the work benefits more from parallelism than what could be had from a single senior engineer (i.e. different lines of work with major context overhead) then you could probably derive more value per senior engineer via part-time work.
A side-benefit that is often not considered is that senior engineers in such a situation may choose to work multiple jobs. Assuming there are no conflicts of interest, chances are this is a net benefit for all. The engineer gets to diversity their start-up equity exposure. Their learnings from any one company can cross-pollinate to others. They can enjoy working on a wide range of problems rather than burning out against one. In this case you may get the value of far more experience than you'd get if they were siloed in one company, not dissimilar from the value that derives from other silo breaking endeavors elsewhere in the field.
> join a team and essentially be a guru or advisor to the team
Honestly, it sounds like you already know what you need: an engineer whose value is technical experience. You may already have enough junior engineers that can get "work" done but what you need is someone who understands the domain, the problem, the desired solution, and can efficiently direct that "work" towards a product while upleveling juniors along the way. Chances are you can hire explicitly for that in part-time and you'd get non-trivial interest.
In summary: Yes, I’m interested, but skeptical of many of the places that claim to offer this unless the pay is hourly.
The tricky part has never been finding an employer that is ok with me working 4 days, but being strict with them to not expect 5 days of work from me in 4 days.
I'm not really sure how to reduce time in work without falling off a cliff given that problems at the senior level tend to require so much focus.
You get much greater value out of the employee.
My experience is from the labour market in Australia, the situation here is a bit different than the US as our healthcare & health insurance is decoupled from employment.
There are some very sharp and experienced engineers out there who are not willing to work full time roles any more, and this eliminates them from the running of the vast majority of advertised roles at companies that will only consider people available full time. It's not uncommon to see senior engineers negotiate part-time arrangements after being at a company for a few years.
Untying healthcare from employment will have a HUGE positive impact on work life balance.
Often there is a specific amount of meetings happening, especially in senior staff. Whether or not you work part-time that number typically stays constant (weekly manager 1-1, product meetings, daily scrum, whatever) also the amount of general company spam and administrative topics one has to keep an eye on is constant.
Thus if one goes from fulltime to part time, the only thing one can reduce is the part where the "actual" work happens, in consequence going part-time means doing even less actual work in a day, which can make one feel even worse.
The way out is to really strip down meetings and all those things to the required amount, which helps any organisation, but often isn't easy.
For other kinds of work that can be performed independently with less regular check ins, it doesn't matter as much.
There are ways to structure a company to make varying schedules more or less feasible. If one piece of work is shattered into a large number of small tasks and scattered between teams with a number of maker/checker review points, then it might not be possible to complete a single item of work without e.g. 3 people in different teams reviewing it and approving it. If the content of the work is e.g. a trivial configuration change that takes 1 minute to author, then you end up with a situation where the process will become exponentially inefficient if some of the people involved work in part time schedules or inconsistent timezones. If instead work is structured into larger chunks that can be done by individuals with infrequent synchronisation points, e.g. deeper analysis / design / implementation tasks, then maybe varying schedules or timezones does not impact efficiency as much.
My concern is around all the non-core tasks, which you can't cut away proportionally when working less time, leaving overproportionally less time for the core job.
Interestingly, they all worked in the insurance industry.
The received (mostly uninspected) consensus that the "full time" schedule is immutable and needs to be an all but universal norm, is past is expiration date.
I am to glad to see a rising tide of push back (e.g .for a 4-day week) but we still have only a few variant of FT and most are considered degenerate, often in an almost moral sense that smacks of received Puritan work ethic, especially in the US.
There is a real antiwork sense in which this is a cultural construct which receives in inordinate amount of upkeep on the part of those who require it to benefit from it.
Kudos to your co. for progress!!!
I don't even expect a commitment for a fixed number of hours or fixed monthly pay (although a fixed monthly retainer would make accounting easier), but i am happy to come in on demand as needed (up to a limit)
what i am looking for is a company where i can join a team and make a meaningful contribution that takes advantage of my experience.
i particularly enjoy working with junior developers and want to help them grow.
I'm now working 25% less than my full-time colleagues over 4 days (ie: I work one less day a week, and a slightly shorter work day). I absolutely love it and would never go back.
Of course it helps that I'm lucky enough to be in an industry where a 25% reduction in salary is still more than enough to be able to pay the mortgage and support my family.
I'm actually hoping to ultimately go down to three days a week, just need to make sure it will still work financially.
The twist is this: I live out of the US (CT TZ) and am currently paid a good competitive (for the US) salary in USD. Even if I was paid about half of that, it would be really good for me. If you tell me that in addition I was going to only work part time? Sign me up.
Lately I’ve been thinking about what it would be to work every other week.
Half of the year, getting full weeks of just living life. Amazing. The plus side for the employer is that you get a full week of my attention on a very reliable schedule. This would be the pinnacle of work life balance for me.
...but yeah I'm at a point in my career where I value work/life balance more than money. Would definitely consider less pay for fewer hours per week and fewer weeks per year.
Needs to include health care.
I wish I had more insights to offer, because I personally know quite a few people struggling with burnout as well. Their solutions and mine so far have been just to switch jobs and hope to find a more favorable environment.
Why take reduced pay for reduced hours when I'm already getting full pay for reduced hours.
Selling 5 out of 7 days of my week is not something I'd ever choose. It's something we're all forced into.
So, a consultant?
I rather work a few months and then take a month off.
I have dream of build a replacement for FoxPro/Access/Excel and have the time for it will be great!.
16hrs a week after 630est.
A traditional job would be
7am - up, breakfast
8am - leave home
9am - get into office
5pm - leave office
6pm - get home, see kids
7pm - make + eat dinner
8pm - chores (washing, gardening, etc)
9pm - hobbies / friends start
11pm - bed
a 4 hour day
7am - up, breakfast
8am - start work
12pm - stop work, chores
1pm - hobbies start
3pm - kids back
5pm - cook/eat dinner
6pm - hobbies / friends start
11pm bed
For less pay - no.
but are you going to pay me less?
Then no.
/End thread