|
Why Are You Not Prepared for an Interview? Wednesday, June 06, 2007
First off, I have to say this post is pointless. If you are reading it, then you obviously don't fall into the category being addressed.
Why don't candidates prepare for stinking job interviews? Why do they lie so badly on their resumes? I'm trying to add 3 Java/J2EE developers to my team. I would think that if you are going to a Java job interview, you might Google for "java interview questions" and actually read a few pages. From my experience, as a job candidate, you could probably pass most interviews even if you knew absolutely nothing by simply doing that. So, the simple rules for getting a job: Don't put crap you don't know on your resume. You will be busted. Don't put every damn technology you have ever touched on your resume. I will not think you are a "Jack of All Trades", I will more likely think you can't keep a job. Write your resume so that it is focused on the job you are trying to get. If you are looking for J2EE work, leave off the VB, MS Access, etc... Stuff in the middle is ok, Ruby/PHP/Python. Being well rounded is good. Just don't give me the kitchen sink. I know PHP, Perl, VB, I don't advertise it. Be very careful about how you put "team projects" on your resume. I don't care what your team did. I want to know what you have done. In an interview, the more I here the "we" word, the less I think you personally have done. Be able to write code. If I prepared to interview you (I probably didn't, I'm busy) I will simply make you write some code and ask you questions related to your future job, and completely ignore your resume (its full of lies anyway). Be able to answer questions about everything on your resume. If I did not prepare (more likely), I will be shooting from the hip, and we will focus on your resume. My experience is pretty broad, I'll instantly know if you are feeding me crap. And here's the gist of things. Even if you don't really know anything, if you spend an hour with Google and the job description, you can gain enough knowledge to pass most interviews. Hell, if you've at least prepared for the interview, you are well ahead of most. Why can't candidates at least lie well? <willCode4Beer/> posted at 9:26 AM permalink
12 comments |
Contributors
Under the Wheel
Why Are You Not Prepared for an Interview? Process Overkill, A Developer Strikes Back Parsing currency into a BigDecimal emulated by a synthetic accessor method Write once debug everywhere...
Behind the Wheel
|
