I went through a brief phone screening initially, which went well. I was then told that they require all candidates must complete a 4 hour programming challenge. I was hoping based on the previous interview here that the company would have updated their programming challenge. My hopes were dashed, and I was faced with the dumpster fire that is dev.xys infamous "PHP pay date calculator". Where to begin here? The exercise asks you to solve in an OO manner, while providing an interface you must code against which doesn't lend itself to OO design. The provided interface could have been all static functions actually, as not a single instance variable is required or used. In hindsight, I wish I had not wasted 3 hours of my life that I will never get back or get paid for, to unit test and solve an exceptionally poorly designed problem. Like the other interviewer here, I also completed and submitted functioning code, only to be ghosted. I will also be posting my solution on github to prevent future candidates from wasting their time on this drivel. Was the problem with my code that it had 100+ assertions? Did I choose a composer holidays package which offended the interviewers? We may never know. If this challenge is the type of work done at dev.wasteyourtime, I suppose we could consider this a bullet dodged. The fact that this company is aware that the problem/solution is out there and freely available and that they haven't updated their challenge speaks volumes about them. Perhaps the actual test is to find those willing to simply copy pasta an existing solution? Perhaps the point of the test is to find candidates just under qualified enough to not threaten the positions of incompetent managers? Again, we may never know. Run, don't walk away from this company.