Re^7: Certifications are dumb.

When I'm interviewing for a position, one of my first goals is to find out whether or not those weasel words in the job description mean:

- We are looking for somebody who communicates well and will fit in with our existing team.
OR
- Will you shut up and do what you are told?

I try not to go in with preconceptions about the employer when I see them, though, since it is often the recruiter that adds that sort of crap to the posted description.

Comment on Re^7: Certifications are dumb.

Replies are listed 'Best First'.
Re^8: Certifications are dumb. by BrowserUk (Patriarch) on Apr 09, 2008 at 16:13 UTC
When I'm interviewing for a position, ... It's a good point. Many people forget that the interview is as much about them interviewing the company as it is about the company interviewing them. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^9: Certifications are dumb. by amarquis (Curate) on Apr 09, 2008 at 17:55 UTC
Yeah, dragonchild mentioned the (valid and true) employer side of the story, that the employer is assuming a lot of risk when they make a big hire. But the other side of the coin is that the potential hire is as well. A bad fit is terrible for both parties. I expect potential employers to be happy to discuss all aspects of the position with me, and I try to be as up front as possible when I'm interviewing a potential employee. The cost of making a bad hire is just too great not to do otherwise.	[reply]


more useful options
	PerlMonks