Usually, not always, but usually the interview is separate in 2 if not more parts.
The initial interview, that it's more than present the CV and nothing more in front of HR. HR does not know about technical concepts, neither they care about it. In fact, some HRs hate programmers. So the first part of the interview is easy to cheat.
The second interview, it's the technical interview and IT'S EASY (if you are not cheating). If you are aimed to be a Programmer JR. then the questions usually are easy and mistakes are allowed. Instead, if you are aimed at a seat of seasoned/expert, then the questions are hard (but easy for an expert). And you couldn't fool the interviewer.
What I had seen (in the technical interview).
and if I ask something different, they feel shocked if not angry because I shot a special question: "this question is not fair!". Truly, it is.
And I have seen a lot of pages, videos, and whatnot about "10 questions asked in an interview". They don't work!.
- Q: What is the meaning of "Object"?.
- A: Object is an instance of a class.
- Q: Well, technically yes but what is the meaning of it? What is an instance for example?
- A: Errm...
They count but they are not a free pass for the interview. I don't care if the candidate has a bachelor, or even a master or a Ph.D. and most companies are not caring about it.
I have seen a lot of examples of it. People whining about their life, a sick child, feeding their family. I don't care. If they are not prepared, then it's their fault. Brown noses are not loved anymore too.
We (technical interviewers) could smell a candidate with no experience a mile away.
A few companies only do a simple interview with HR and it includes a generic exam and yes, some companies hire a mediocre programmer. But it's different to be hired than to keep working. So, even if the candidate is hired, there is no warranty to keep the job.
In my experience, I have seen candidates fired in the first week and some of them in the first or second month. Because you can't fool the team.
For example, a bad programmer will try to hide their inefficiency by:
- Taking works that it does not involve programming such paperwork.
- Adding comments to an existent code.
- Trying to be kind and social but finally everybody found that you are phony.
- Executing automatic tasks.
- Asking for help for basic knowledge.
- Waiting to be trained (for free) by the company.
- Copy and Paste programmers (they could last for a bit longer but not for much).
- Or they simply freeze. And it is sad.
For example, if you ask an artist or a writer if he or she is good at programming, they could say "now, I suck at programming". And it is a reality, some people are bad programming but they admit it.
Let's say you are good at learning concepts by memory. So, how about to study system administration?.
However, it's really sick to see the insanely amount of "programmers" that try to enter the market by faking knowledge and experience.
Also, there are a lot of small businesses that hire mediocre IT (IT in general), they don't have much infrastructure but they need somebody to fix the computers, printers and such. Where? Find a small business, usually in a small city or town.
Aggressive-Passive= a nice way to say, they are aggressive.
- Candidate: And who are you to decide who is fit for the job? (or who is mediocre)
- Interviewer: It is my job.