I think this article would be more insightful if you actually said what was the technical interview questions you actually failed.
Everyone fails it's a common thing you can only learn from your failures and do better next time. Also a technical interview for a junior developer and they fail you on we don't like your style????
That is ridiculous theres a reason why it is called "junior" you are meant not to have a clue and eventually gain experience and learn from the projects you build.
What was the exercise and what did you come up with?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think this article would be more insightful if you actually said what was the technical interview questions you actually failed.
Everyone fails it's a common thing you can only learn from your failures and do better next time. Also a technical interview for a junior developer and they fail you on
we don't like your style
????That is ridiculous theres a reason why it is called "junior" you are meant not to have a clue and eventually gain experience and learn from the projects you build.
What was the exercise and what did you come up with?