Form3 interview questions

I was approached by Form 3 directly on LinkedIn to chat about a role to support the development and improvement of the L&D Function. I had an initial chat with them, which seemed great, and then a second, more formal interview. I followed up twice after the interview, once to thank them and once to inquire if I was still being considered before Christmas. I didn't receive a reply to either message and I'm assuming I was unsuccessful. It was disappointing and discouraging to be ghosted and I was surprised to have this happen in this day and age . Perhaps I was not the right fit or didn't interview well but even a template rejection message is kinder and more considerate of a candidate's time and effort.

TL;DR: Don't waste your time, just bullshit. I was contacted by a recruiter through LinkedIn, and we set a meeting. She called me, and asked me the common questions like: Previous experience, Salary expectations, etc. The same day she sent me the an email with the tech task. This tech task is public on their Github. There is no deadline to deliver it, however they won't evaluate you as the people from HR says. Without previous experience in Go (they say it's not needed, but it's false) I completed the task in 3 days, but they don't care, they expect that you don't have personal life (red flag here already...) they won't pay attention to the effort you made delivering a code following the best practices: DRY solution, unit test + integration tests, reusing http connections, docker running the unit test integration tests, etc. PAY ATTENTION TO THIS: I shared my task with friends before sending it to them. I always like to have a pre-feedback/review before sending anything and no one had problems running the project, but the feedback their provide was that the docker-compose was not working in their Ubuntu laptops/or M1 I suppose. I was using macbook (old i9 one) same one as my colleagues and it worked like a charm. Maybe was the host.internal.docker that in linux doesn't work out of the box, but that's not my problem if you don't say that in your "should" and it's not reason enough to refuse a task. Another argument to refuse my candidature was that the code is not production ready. Seriously? Did you expect to invest one person alone 4 weeks at least (for free) to have production ready code? Software is made in teams, where you have PRs and code reviews, and maybe even a QA. It's unrealistic. I said that to them as well, still waiting for an answer. They should improve their process, sometimes it's not enough with a cool, hipster tech blog, and ego-podcasts.