3 ms·
Hey - I was the primary author of Staffjoy! We had a few different algorithm iterations. One of our biggest learnings was that it's hard to build a generalized
by philip1209 7y ago
Hey - I was the primary author of Staffjoy!
We had a few different algorithm iterations. One of our biggest learnings was that it's hard to build a generalized auto-scheduling algorithm. While most companies have similar needs at a surface level - things like local labor laws, cross-functional roles, breaks, and business quirks mean that you end up customizing the algorithm for most customers.
For the best auto-scheduling - Kronos is the incumbent, and Legion.co is probably the most advanced disruptor.
- Dowwie 7y agoThanks for replying! You gave money back to investors and open sourced your work. That's commendable behavior! I never forgot that story. As usual, the solution seems straightforward from 30,000 feet but once we go into the details, it turns out to be much more complicated. Noted about Kronos and Legion. Have you done any further scheduling related work since Staffjoy?