In other professions where the shared state isn't as big, such as medicine or therapy, you see way more part time style work happen actively in the industry. Be it working for 2-4 clinics part time or just doing half hours so they can focus more on other things in their lives.
Another kind of role that I think works well part time is an advisor / consultant expert role where your hired to verify things are being done correctly in your sub field and are used to train others design wise as a 3rd party. Which is another sr / experienced type of role.
Another type of part time that might work is working on your own project as a solo dev in maintenance mode once your established. But also only lasts so long as competitors get ahead of you.
Part time not working well is something inherent to the job itself unfortunately.
This sentiment is what GP points out is cultural, not practical or factual. If you compensate them well for the hours they work, many part time devs will have superior per-hour output to FTEs and also be grateful for the added flexibility you afford them.
We hired a stellar part time dev recently (contract hire to start, we just increased his rate and verbally stated we are interested in continuing the relationship long-term if he is, and offered written agreement if he is interested), and he has been working out great. The option is open to him to work full-time whenever if/when he wants by planning it ahead of time with us, but our default expectation will remain being part-time so he can pursue his game development on the side.
Finding a great part-time team member is no different than a great FTE, once you and the employee are both free of the cultural negative baggage associated wtih part-timing.
There's your problem.
It sounds like you just amortize the "meetings" differently. Having to answer lots of async emails / slacks can waste just as much time as scheduled meetings.
Sounds like you work at startup rather than corporate. My current job is basically building on something somebody else has already prototyped. I hate it, it makes my days dull. But then one day I realized, that if I could do it as a part time job then I'd have no qualms of not wasting my mental energy, I'd gladly do what is required, clock out and spend my creative energy outside of work or with other part time gigs.
That don’t need to spend lots of
time getting context. They can figure
out how to solve problems matching
your team’s coding style without
extra meetings.
I've worked a variety of enterprise-y developer jobs, and I don't find that to be the case at all. I mean, that context is the job.Coding bits of functionality for an existing business is not a matter of "matching the team's coding style."
Heck, there are often not even engineering "problems" to "solve." It's a matter of figuring out integration with existing systems and processes, understanding the business itself, etc. That's why part-timers don't make sense. They can't just walk in, sit down, and code.
And if you could tee things up for them, to the point where they could just sit down and code, then 90% of the work is already done. And your part-time coder will take longer to deliver... why would management want to wait 2 weeks for a part time person to complete 40 hours of pure coding work, versus 1 week for a fulltimer?
Yeah, I think you could step back from that at some point and be a heck of a part-time asset.
1. Your knowledge of the app and organization would likely decay over time.
2. I'm not sure the the organization would love this move. It would be better than losing you entirely, but probably not as valuable as having you fulltime. From your perspective, 50% of your time is better than 100% of nothing. From their perspective, they're probably going to take the "glass half empty" view.
It might be more work to develop a specification that requires no context to complete than to do it myself.
I too would crave a part time programming job, mind you, but I think that only works on a team that is completely part time.
If my experience is anything to go by, this sort of self-directed collaboration—think "design discussions" rather than "meetings" or "ceremonies"—will end up far more productive for everyone involved.
Doing it in a meeting where everyone has different questions, tangents and other cruft that you have to sit through is extremely inefficient.
Additionally, everyone can focus on producing and consuming information in the downtime between focus-work sessions, without interrupting flow at someone else's convenience.
In all cases, quality documentation is more likely to produce accurate information transfer with less time wasted by everyone involved.
Fix your management and you'll be able to hire part time easily.
It depends more on the personalities, values and organization of the workplace and the team — for any size, if more than 20% of people involved need to spend more than 2 hrs/week in meetings — it is an organizational/ops issue, not an inherent feature of the work.
> more foreign the domain the more time is needed to coordinate work
More foreign to who? If it is foreign to individual team members, then it is a problem of insufficient onboarding/training material and process, poor documentation, or under-qualified hire.
The only way I see real value is if you’re the sold dev/architect or if you can come in and confidently pick up tickets and they’re properly scoped and documented.
If you need developers to spend so much time ideating and figuring out how and what to build, you’re mismanaging those developers imo.
I have successfully gotten 80% four-day-week at a string of engagements... but I work in the non-profit academic sector, and get paid quite a bit less than that $200K+ salary.
I think a four-day-week, or even a three-day-week, makes a lot more sense than tha 4-hours-a-day 5-day-week the OP was suggesting.
Because, yeah, one (or certainly two) meetings could pretty much blow a 4-hour-day. But at the 4-eight-hour-day schedule I've been doing, I feel like there is still plenty of time for meetings and overhead, and I am pretty confident I end up 95% as productive working a four-day 32 hours as I would be working 40 hours. I feel like it would still work pretty well at 3-eight-hour-days too.
Below that -- or trying to work four-hour days instead of fewer eight-hour days, I could definitely see problems with "overhead" or lack of commitment.
I can only speak from my experience working 80% time in several different jobs, in nonprofit/academic environments. As above.
(I enjoy writing code, if writing code was "barely" part of the work I wouldn't still be here. It seems like it would be impossible to get anyone who was good at writing code in a development/engineering job where coding was barely part of the work! But I'm not sure what this has to do with the feasibility of less than full time work as an engineer/developer).
Remote-first, multi-time-zone companies simply don't do meetings. All communication is async and written down. Work gets done without a lot of hemming and hawing and meetings-with-no-agenda-to-talk-about-setting-an-agenda-for-a-future-meeting. It's much more efficient to come to a decision over 7 asynchronous back-and-forths, and people have the opportunity to do some research during the conversation so their decision is better informed. The whole Open Source world [when development is not done within a corporation] works this way.
I think the problem is corporations are obsessed with a definition of productivity as "the person is constantly productive". If you're not in a meeting, or have a ticket in progress, or are doing training, clearly you are just wasting time. You can't be allowed to just ruminate, or research, or play around with an idea, or talk to other teams. They'd rather you be writing code now that will be obsolete in 6 months and take a year to replace, rather than take 2 months to come up with a plan for your code that will take 3 months to write and last for 3 years. We rush into things because we have to have something to show for our work every day, and as a result the quality is poor, and that costs more in the long run.
Having worked for such companies, this is not true, at least in my expreience. Plenty of meetings. Very long ones sometimes, 2 hours is not unusual; 3, 4 hours sometimes on Zoom or Hangouts.
> [non-remote-first companies would] rather you be writing code now that will be obsolete in 6 months and take a year to replace, rather than take 2 months to come up with a plan for your code that will take 3 months to write and last for 3 years.
Hmm. I can assure you some remote-first, multi-time-zone companies would also rather you be writing code now that will be obsolete soon than take substantial time to come up with a plan for code that will last years and serve the product well.
Visibility counts for a lot in some remote-first environments. Depending on the management, they may regard the best form of visibility to be regular code updates, PRs, issues filed etc, rather than taking your time over deeper design and research. If they pay more attention to quantity than effectiveness, that can mean shipping code and iterating every few days is something they are looking to see, and a high priority if you want to keep your job. Async written communication on design is sometimes seen as too much talking, not enough doing.
As a full time senior engineer I’m responsible for oversight and guidance on three separate work-streams, so I have to go to all their meetings. If I were part time then I could be involved in just one of them, and go to only those meetings.
I have a friend that can really work 4 hours a day, but he is a special case where he does not have a family to upkeep and no mortgage. He is also a bit hard on the frugality.
But finding such person is basically 1 in a million. If I post a job with 4h a day which amounts to 1/2 of a normal salary I will probably never get a candidate. If I post a job with normal salary and then start explaining that it is 1/2 hours and accordingly paid, some people will get angry.
I think you're mistaken about that. If you can persuade candidates that it really is 4h a day at 1/2 of a normal salary, you will get candidates who are excited by the job because it opens up their time for other opportunities for hobbies, home life, side projects, open source projects, looking after family, other consulting gigs, education, etc.
However, for developer roles you might find that potential candidates don't entirely believe the ad. I think they'd imagine the employer having unrealistic expectations of what 4h reasonable output looks like, so that they'd feel pressure to work overtime, resulting in closer to 8h anyway while pretending to get it done in less, for 1/2 of a normal salary.
It would be much easier if I get someone CV and he writes cover letter explaining that he would like to try such an arrangement.
I tried to get part time dev for Kibana/Elastic needs like 4 hours - anyone I approached was not even willing to discuss "why" they just said no. People also don't have time to listen to your persuasion, most of the time it is clear cut and goodbye.
You can argue that half time engineers are more than half as productive as a full time engineer because as others have said full time engineers don't work a full 8 hours anyways. While theoretically that's true, as I originally posted, that's not what I've seen. Based on my anecdotal experience, half time engineers are less than half as productive as a full time engineer.
So from both a productivity and economic perspective, it hasn't made sense.
Another factor is that often the cost of developers is not the most significant factor. If a company can get say $100m of value out of $10m of salary cost on engineers, it doesn’t really make sense to instead spend $6m to get $80m of value.
And just adding more people isn’t easy as each person increases communication overhead.
That some people live in houses they couldn't pay for on $150K doesn't mean that $150K isn't possibly a "full time salary". $150K is definitely in the category of "a full time salary", many people make this much or less working full time.
That a skilled engineer could possibly make $150K for working 50% time -- is a choice not available to most people, most people don't even have the choice to make $150K working full time! So a skilled engineer has that option, make would be a (healthy) full-time salary for most of the USA, working only half-time. Or anyway would, if employers would hire like this. That's the point I meant to be making.
Income distribution in the US does continue to get more uneven every year.
However, I'm not "there" yet as a developer. Maybe in a few years after I've proven myself.
Have you considered older workers that are nearing retirement? They're probably looking to lean-out, and a part-time job could give them activity in their lives, while getting you someone who is highly experienced in getting things done. You wouldn't be paying benefits, but probably a higher hourly rate (for less than 40 hours) to compensate.
Or job sharing, where you bring on two part-time workers. My sister did this for many years - it gave her time to raise her children while being able to pay a nanny + daycare. She worked Mon-Wed, and her job partner worked Wed-Fri. The overlap allowed them to coordinate, and they were able to call and send texts to each other at other times.
Who cares if they have 6 jobs, that’s not for you to worry about.
If they get good work done on your project and skip the extra meetings, they’re worth keeping around.
Well yeah. There’s your problem.
I've worked part time for a startup remotely across timezones. I personally credit the technical lead for the most part for its success. Then, the chemistry within the team was really good. When someone says something others tend to get it. And the planning. The tech lead sets up the goals for the quarter and push back on distractions from the business side except on rare occasions. The management was also very competent, they seemed to listen to the engineers.
1) there is a constant amount of overhead that is always needed regardless of how long you work for in a week. Meetings and collaboration to figure out what to build, discuss issues etc. if these take up 10 hours a week a full time dev has 30 hours to do other things where as a half time dev only has 10 hours. So 2 half time dev just doesn’t get as much done as 1 full time. I guess this is also why 2 engineers don’t get twice as much done as 1, all things being equal.
2) Most part time dev candidates I’ve seen aren’t doing just a single part time job, they are doing either multiple part time jobs or a full time job + part time job. Either way the mental energy is already gone.
Maybe there is a way to make part time work, I just haven’t figured it out yet.