ed25519 verify key: 6614c7acfe8e7419bbc26709d7f0fdcc55d8258f205a95173ce37e42e1715462

  • 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle




  • I did one where I went through a few rounds of interviews, technical and otherwise. In talking with the developers, they mentioned that they were trying to integrate a certain client side framework into their backend frameworks build process, without success. Get to the final stages, and the director of engineering asks me to work on this take home project to, you guessed in, integrate the js framework into the build process of the backend framework.

    I sent them a strongly worded rejection email. It was a realreal eye opening experience.


  • Ridiculous take home tests are probably the number one reason I decline to continue interview processes. If you think that building a client, an API, wiring it up to some other third party API, then deploying is a reasonable scope for an unpaid interview challenge then you are very bad at scoping software projects and the most important thing I can do for you is tell you as much.

    I told one start up if I built what they asked for in the interview, I would pursue funding from their investors and launch it as a competitor- it was that similar to what their actual app did.














  • I experienced this too, and landed at a smart company that paid me for the time I spent on the take home project. Yes, it’s less money than I might earn at a more prestigious company who abused my time, but I’ve also successfully selected for a company that has a good working environment.

    They have an engineer for probably 30% less than what I demanded from another company with a dumb hiring practice. The dumb company was willing to give me the money too, but I was annoyed with their process so I told them I would not work for them unless they put a four day work week in my offer.