Would senior engineers be interested in working reduced hours or part time?
41–50 of 127 posts
Re: Would senior engineers be interested in working reduced hours or part time?
#42I’m considering it. Gumroad is the main example I can think of where they hire for 20-25 hours per week. It’s easier to find places that hire for 32 hours per week (a 4- or 4.5-day work week). For the latter, I am concerned that the companies end up expecting basically the same output (i.e., it’s a hiring marketing gimmick) since the positions are salaried. I saw one company that said they manage their 4-day weeks by…
Re: Would senior engineers be interested in working reduced hours or part time?
#43I do think the biggest obstacle to part time work in the US is that health care is tied to employment. Health insurance can easily cost $20k+ a year for a family, and it'll be hard for employees to stomach the salary cut they might have to take to make the numbers work.
Re: Would senior engineers be interested in working reduced hours or part time?
#44My 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.
Re: Would senior engineers be interested in working reduced hours or part time?
#45Needs to include health care.
Re: Would senior engineers be interested in working reduced hours or part time?
#46Re: Would senior engineers be interested in working reduced hours or part time?
#47Often 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.
Re: Would senior engineers be interested in working reduced hours or part time?
#48It 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.
Re: Would senior engineers be interested in working reduced hours or part time?
#49I guess there are many who would like to work part time, however that requires a different working structure. 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 i…
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.