Get these tips as a free eBook by joining the newsletter here.
These tips may only apply to programmers and others who must endure the so-called technical interview.
Tip #16: “Recruiters Are Often Wrong”
While recruiters want us to succeed and get the job, they can be very wrong about what a technical interview entails. This isn’t necessarily their fault, as the company they’re trying to place us at might not have been accurate. They can say it’s very technical, not at all, or in between. The test can be an oral, written, or computer-based. Every single detail they tell you can be completely off. Be prepared for anything. And then tell the recruiter afterward what it actually entailed. They’ll be grateful, even if you bombed it because of what they told you.
Tip #17: “Expect Unfairness”
Technical exams are often unfair. They can expect you to know things that you haven’t needed to do in years (if ever), without warning. Sometimes they ask questions that don’t even relate to the job. In the real world, you can look up something you don’t know, but sometimes you can’t in these tests. You can be expected to write code by hand, as if you do that on the job. In many cases, the testing environment does not mirror the real world. You can be unfairly expected to achieve things without the tools you would have on the job.
Tip #18: “Cheat If You Have To”
Due to the previous tip, if you have to cheat to dodge the unfairness, I personally consider it fair game. Two wrongs can indeed make a right. Cheating usually takes the form of looking up answers on your smartphone if you are left alone to take the test. Given the inability to prepare for these tests, it’s only fair. Just don’t get caught.
Tip #19: “Memorize Definitions”
Many tests consist of being asked to recite definitions of technical terms, as if this is something you spend time doing while employed. It pays to have recently re-memorized many common terms for exactly this reason. Keep an ongoing and organized list of them on a computer or phone and commit it to memory when job hunting. A snappy answer works wonders compared to a disjointed one, delivered without confidence as you search your memory for a term you haven’t seen in months or years.
Tip #20: “You Can Refuse a Test”
You do not have to take a test. Of course, refusing means you do not get the job. Most tests are oral and not too bad, but the handwritten or computer tests are a disaster. You can politely decline the position because, in my experience, fewer than 10% of jobs require it and you can find one that does not. It is not worth the aggravation.