loading...

On coding challenges.

twitter logo github logo ・1 min read

As a dev candidate who's been unemployed for a while now, I see a lot of companies wanting you to take these timed tests to implement some challenge or algorithm. These have been criticized for not meaning much.
And I myself am not sure if I want to feed into a culture that perpetuates this kind of meaninglessness, however, should I bite the bullet for the sake of a job or hold out on principal?

twitter logo DISCUSS (1)
markdown guide
 

The first question you should answer is...what are your goals?

I agree with you in the sense that they might not mean much, i.e., you might not even utilize those skills at your job. But I also believe that knowing how to solve those challenges helps display a particular way of thinking and problem solving.

If the key to getting the jobs you want entail knowing how to solve those problems, then I say bite the bullet. In that sense I don't think it's meaningless.

Who knows though - you might be able to find a job where you won't need to prove that knowledge. But it's as they say, better safe than sorry.

In any case, best of luck on your journey!

Classic DEV Post from Apr 23 '19

The Amazing Secret to Crafting Conference Submissions that Don't Suck

How to write a quality submission that might not get rejected.

John Best profile image
Experienced ASP.NET developer passionate about learning Software Engineering, being an effective team member, and carving out my own little niche in the world. I enjoy working with jQuery, Angul...

👋 Hey dev.to reader.

Do you prefer sans serif over serif?

You can change your font preferences in the "misc" section of your settings. ❤️