I've been through a few of these coding tests over the years and absolutely refuse to partake in them anymore. If a company cannot take the time to review my extensive portfolio, peruse my github repos or assess some of my many answers on Stack Overflow they are not worth the effort.
Every test ends up being more of a how fast can you search/read scenario than actually testing any kind of useful metric. The optimal answers are usually some unreadable leetcode that would never fly in any reasonably maintainable code base.
Programming is about solving problems, not memorizing algorithms. If I am unsure about the best way to accomplish a task, there is guaranteed to be a question posted online with 20+ answers where the real subject matter experts have hashed out every conceivable detail. I consider checking this no different than looking up API documentation. Sure, I remember commonly used expressions but should I be expected to memorize every feature of every language or library I've ever used?! By this logic a writer would never use a thesaurus either.
The problem, as I see it, is that these tests are usually administered by HR people who have never written a line of code in their life. I've been a developer since before most of them ever touched a computer. I first learned to code from a book, before the internet even existed. Yet I'm expected to validate my knowledge for their sake. No thanks.
In the freelancing world, I would never provide any code to a potential client until I'm hired for the job. Period. I may, however, whip up a proof-of-concept and send a sample video but this is my choice rather and never a requirement. If a job post demands unpaid samples or testing, the get flagged as inappropriate.
The only way we as developers can change the hiring landscape is to collectively boycott these abhorrent practices. Remember, we write the rules. We create the tools that make the world run. If they want to make use of our skills they need to prove they are worth the dedication, not the other way around.
I say, the next time an interviewer demands a coding test, ask them to provide the definition of a few obscure words and see if they can answer without a dictionary. Maybe then they'll have a better concept of the unreasonable expectations put on us... "I'm sorry, do you not know every detail about the language you use every day? hmm. And how many languages do you know? Oh, just 1 or maybe 2, pfft".
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've been through a few of these coding tests over the years and absolutely refuse to partake in them anymore. If a company cannot take the time to review my extensive portfolio, peruse my github repos or assess some of my many answers on Stack Overflow they are not worth the effort.
Every test ends up being more of a how fast can you search/read scenario than actually testing any kind of useful metric. The optimal answers are usually some unreadable leetcode that would never fly in any reasonably maintainable code base.
Programming is about solving problems, not memorizing algorithms. If I am unsure about the best way to accomplish a task, there is guaranteed to be a question posted online with 20+ answers where the real subject matter experts have hashed out every conceivable detail. I consider checking this no different than looking up API documentation. Sure, I remember commonly used expressions but should I be expected to memorize every feature of every language or library I've ever used?! By this logic a writer would never use a thesaurus either.
The problem, as I see it, is that these tests are usually administered by HR people who have never written a line of code in their life. I've been a developer since before most of them ever touched a computer. I first learned to code from a book, before the internet even existed. Yet I'm expected to validate my knowledge for their sake. No thanks.
In the freelancing world, I would never provide any code to a potential client until I'm hired for the job. Period. I may, however, whip up a proof-of-concept and send a sample video but this is my choice rather and never a requirement. If a job post demands unpaid samples or testing, the get flagged as inappropriate.
The only way we as developers can change the hiring landscape is to collectively boycott these abhorrent practices. Remember, we write the rules. We create the tools that make the world run. If they want to make use of our skills they need to prove they are worth the dedication, not the other way around.
I say, the next time an interviewer demands a coding test, ask them to provide the definition of a few obscure words and see if they can answer without a dictionary. Maybe then they'll have a better concept of the unreasonable expectations put on us... "I'm sorry, do you not know every detail about the language you use every day? hmm. And how many languages do you know? Oh, just 1 or maybe 2, pfft".