Why You Should Never Consent to a Coding Test in an Interview - Deepstash

Bite‑sized knowledge

to upgrade

your career

Ideas from books, articles & podcasts.

Why You Should Never Consent to a Coding Test in an Interview

Software engineering interviews often involve some kind of coding test or programming exercise. But it is not really useful.

  • Writing an algorithm to generate factorials or to sort a linked list can be easily memorised beforehand. It offers no insight into a candidate's skill. 

STASHED IN:

1

MORE IDEAS FROM THE SAME ARTICLE

Many companies still fall back to outdated and utterly predictable hiring practices. Being interviewed by someone with a list of precise technical questions is pretty much always red flag. 

More rewarding subjects to discuss would be the coding paradigms used in modern software enginee...

A good software engineer often doesn't know the answer to a specific question but knows where to find the answer. There is only so much knowledge anyone can hold in their head ready to recall.

If a task has been automated in a pre-written library, there's no need in reinventing the wheel. P...

IDEA ABOUT

Discover and save more ideas by creating a

FREE

Deepstash account.

Develop a

reading habit

, save

time

and create an amazing

knowledge library

.

GET THE APP:

MORE LIKE THIS

High Paying Computer Languages.

Software developers choose the highest-paying programming languages to set an extraordinary career.

6

STASHED IN:

25

Marcus Lemonis

“People, Process, Product”

4

STASHED IN:

41

  1. Screening call or on-site interview: lengthy when done by HR and short when it’s someone technical, also not a good time to fire all your questions.
  2. Technical interview: where your knowledge is assessed by professionals of the field.
  3. Technical assessment,...

1

STASHED IN:

184