Freelancers that do any type of work will encounter the type of clients that request some “proof” that you have the skills you say you have. Freelancers who write code, however, might encounter that on a more regular basis than others. Somehow, it has become a thing that gets asked from coders.
And you might be thinking “hey, they just want to test out my skills, it’s not so bad, right?” But code tests are being so regularly misused that they have become a red flag for any freelancer programmer. We’ll be looking into strategies to respond to them, but first let’s cover why they’re bad:
Why are Code Tests a Bad Sign for Freelancers?
1. They are often not legitimate
More often than not, coding tests are just a way for shady websites or companies to scam you into doing free work. The scenario goes like this: the client asks you do a test, which might take anywhere between a day and two weeks to do. Usually, the test will also be funnily specific. After you submit the code, one of two things happens: you either never hear from that client again or they reject your application.
What ends up happening is them having your code. Scammers then might proceed to do the same with several other freelancers and have a whole project completed – without a single penny spent.
2. Even when they are legitimate, they’re not paid
Even if, and that is a big if, a client is legitimately asking you to do a coding test for test for them, one part of the situation described above remains the same – you’re not getting paid. Even if you’re starting out and have little to no way to show your experience (more on that in the next paragraph), working for days and not getting paid is a big no-go. That’s another reason why code tests are bad even if they’re not a straight up scam.
Here are a few tips to avoid the freelancer’s nightmare of not getting paid.
3. There are plenty other ways to show experience
Thirdly, asking you to a test comes from an assumption that is wrong. The assumption is that there are no other ways to prove you can code than having you do a specific test for the company. Anybody who thinks that has no idea how freelancing programmers work.
There are a huge number of ways to prove you can put your code where you mouth is. Between the classical interview, a GitHub profile, your portfolio and client testimonials, there are enough ways to prove your experience to remove any doubt.
How to Respond to Free Code Test Requests
Now that we’ve summarized why code testing is a red flag, let’s look at the four best strategies to dealing with that kind of request:
1. Point to your credentials, testimonials and experience
First and foremost, provide proof. As we just covered, there are a number of ways you can show off how good of a coder you are without actually participating in a test. That’s the first step you should take when someone asks you to do a test.
“I don’t usually do code tests, as I have worked on a number of projects relevant to the skillset you are looking for.”
Attach your GitHub profile, describe previous projects, maybe even add testimonials on top.
2. Offer to do the test at your standard fee
If your client is still not convinced and still insist on doing the test, there are two reasons for that. Reason number one: they still want to scam you. Reason number two: they are inexperienced in working with coders and don’t realize you’ve provided enough proof.
If you think that reason two is more likely, you might want to still stick with the client. But you still don’t want to waste your time. So offer to do the test at your standard pricing fee. If the clients still want you to do the work and are legitimate, they will either realize the position they’ve been putting you in (because they’re in it themselves now), they’ll agree and pay or they’ll decline. Either way, you have nothing to lose.
3. Decline
Finally, the third strategy (and one of the most important lessons you’ll have to learn as a freelancer) is to say “no”. Sometimes, it’s better to walk out while it’s still not too late. That is especially the case if the client seems shady in any way. After all, you already have one red flag – they asked for code testing, which is often a scam. If there’s something else that makes you feel uncomfortable, declining the project and moving on is likely the best decision.
Have you been asked to do code testing? How did that go? Share your stories with the community in the comment section below the article!
