Well these tests are part of their hiring process
so yes I'd say if you want to get hired by them you have to do them.
Certainly that's been the case whenever I've been giving tests as part of a hiring process.
I usually give some sort of coding test to prospective candidates (although I tend to keep them small 30 mins to an hour) and if a candidate refused and pointed me to their github or similar instead
I'd bin their application immediately because: 1)
It makes it much harder to compare code between multiple candidates 2)
The code they offer may not provide examples of the sort of thing I'm looking for 3)
It positively reeks of disinterest on behalf of the candidate.
If you aren't serious about being hired by me, I'm not serious about hiring you.
4)
To me it also says "I can't follow instructions
and I'm going to do things my own way
regardless", not generally traits I'm looking for in an employee.
workplace.stackexchange.com/users/64903/motosubatsu
I have uploaded some code on my GitHub account,
all my code is publicly accessible, so if someone wants to access my account, he/she can review all the code I have written.
I can get someone else code and push into my repo,
having your code public doesn't help to hire a manager to hire you.
Why are these tests necessary?
It helps them filter good from bad, and I don't think anyone gives a really big test that is time-consuming unless you don't know it, if someone is good at something, they should welcome it
and it is a plus that you can add it to your repo, and your knowledge even if you get hired or not.
Is there a way to decline doing them without being disqualified?
Declining means, either you have an attitude or not a team player or too committed to give new company times, all which IMO are red flags.
workplace.stackexchange.com/users/None/
Coding tests that last an hour or so are pretty much the norm when applying for coding jobs these days.
You can't really avoid them if you want a developer role without severely restricting your options.
You could refuse and point them to your Github profile, but this would almost always mean an outright rejection.
There have been times that my inbox was full of these tests
How many roles are you applying for?
If you constantly have an inbox full of these tasks, and it's only one task per company, that implies you have loads of applications on the go at once, and you're getting rejected from the vast majority of them (or turning them down yourself.)
If this is the case, then the real issue here isn't with the coding tests, it's with the number of jobs you're applying for and being rejected for.
If this is indeed the case, then you'd be better off screening the roles you apply for more carefully, and putting more effort into just a few applications, rather than mass-applying and trying to spend every evening of the week churning your way through coding tasks.
workplace.stackexchange.com/users/57339/berry120
is it really necessary to do and the coding tests too?
If a company requests you to do such tests, then it would be expected for you to do them.
It is true that a test may not give all the aspects of a candidate, and that other things are also important when considering a recruit.
However, code test are in some cases the standard procedure of some companies, where the can't easily make an exception for your case and ignore such recruitment protocol.
You can surely try ask if you can do something else.
A nice way would be by politely asking " Is it possible to something instead of the coding test?
I can provide several Git projects to exemplify." , but it is not likely they will agree with you and do it.
If they insist on doing so
and you do not want, then I think you have no choice but to end the recruitment process.
If coding tests are really not something you like, try searching for jobs in companies that do not require such tests.
workplace.stackexchange.com/users/73791/DarkCygnus
From an engineer's perspective who may be interviewing you...how am I meant to evaluate your skill or see how you solve problems if you refuse to do so in my presence?
Let's not mince words here.
I suck at interviews.
I was unemployed for about five months because my interviewing was so terrible (from my perspective; I know I'm a brilliant developer but interpersonal communication has always been a weakness of mine).
But that didn't mean I didn't do any coding exercises; quite the opposite.
I made sure that I met their coding exercise requests, and showcased what I had learned from past experience (including clear documentation of code, READMEs, unit tests, etc).
I wanted them to know what they were getting from hiring me; a diligent worker who regarded themselves as a professional and expert, and one who understands what it means to architect the solution, test it, and deliver it in a way that makes sense to everyone.
By you refusing or failing to do that, you miss the opportunity to really put yourself out there as a stand-out candidate.
I've not heard of many professional institutions hiring someone without asking them some kind of coding exercise.
Let's face it - as a developer, you're going to be paid a lot of money to solve problems, and if you don't showcase how you solve (or at least approach) problems, you're not showing me that you're worth what I'm willing to pay, or more.
workplace.stackexchange.com/users/2909/Makoto
Almost every developer interview involves a coding test.  I don't really see the need for this, as I have uploaded some code on my GitHub account, all my code is publicly accessible, so if someone wants to access my account, he/she can review all the code I have written.  Why are these tests necessary? Is there a way to decline doing them without being disqualified?
Would declining a coding test disqualify me from the interview process?
workplace.stackexchange.com
<code><test>
workplace.stackexchange.com/questions/102596
workplace.stackexchange.com/users/None/
This is a part of the hiring process and is not normally a big test. It is difficult for companies to make an exception. It is expected for you to do this test and you risk an outright rejection if you refuse. For many companies, these tests are simply part of their screening and hiring process. They're unlikely to make an exception for you, and declining to perform a test will likely present a poor image of you to them. You can of course try to present them with examples of your work instead, but it is unlikely to do you any favours.
For many companies, these tests are part of their hiring and screening process and they are unlikely to make an exception for you. It's not really possible to decline these tests unless you want to present a bad image to the company. You could decline to do the test and present examples of your work, but it is unlikely that they'll hire you.