tl;dr - He won't hire you because he has a hyper-focus on the process of the interview rather than the process of finding a suitable individual for the opening. His attitude can be summed up in this one line, "Most people looking for jobs don't deserve them."
Yes. But it could be true that most people looking for jobs don't deserve them, and yet it would still be important to remember that the interview is nothing but a process for finding a good match.
I think it can be tricky. We know the process doesn't always work. Some companies, e.g. Google, believe that it's better to adhere to a tough hiring process and reject most people even if a certain number of those people who are rejected may be brilliant engineers. But what I think is important to remember is that the goal is to hire the right person for the job. The hiring process you use may or may not be an effective and efficient means of finding that person. But certainly having a very narrow view, say by having a very strong focus on the process and little else, is a sure way to miss the right person at least some of the time.
Now who are you? What are you going to give me in return? Why should I tell you that I love my job and my career. Why should I tell you about my vision and plans? What are you really looking for in that.
The hiring should be a lot simpler:
- You have a problem. You need someone with the right skills, and hire him.
- I have a problem (need money). I pick a job that I have the skills for.
Thinking the way you do, accepting your daily bull-shit and philosophy (worse, making myself sound like I enjoy and I belong to it) is only a sign for me that you are the wrong person to work for.
Why should I tell you about my vision and plans? What are you really looking for in that.
These 'where do you see yourself in 5 years' questions sound like straight from a 'HR for dummies' book. I would really appreciate if an interviewer reading this post explained me what such cliches are trying to test, other than BS skills. Cliche question => cliche response.
I'm not from HR, but my guess is that a question like that is for learning whether the candidate is goal-oriented or just goes by living day-to-day. I agree that it's a cliche question, and could be phrased more originally and/or specifically in most cases, but it is not _totallt_ useless.
It's a great question and I ask that question all the time. However, unlike the blog writer, I am looking to weed out those that are looking to become managers soon. If you are looking to get a development job as a stepping stone to a management position in 3 years, then you're probably not a software engineer I am looking for. (One of many factors, of course...)
This is what I fear. I fear that some hiring manager is going to make a career choice for me. I chose to interview with his company for a specific position, my choice of career path.
What do I say? If I reach to high I endanger my own prospects at being hired. A buddy of mine answered the "see yourself in 5 years" question with "Probably working at Google". Needless to say he wasn't hired.
If I reach too low I sound like a deadbeat. If I answer with something like "Working at the position you are hiring me for" I sound like I have no vision and no drive.
There isn't a right answer to this question. Because the only right answer is "cliche".
That's funny, I gave similar answer when interviewing with my current company, and I got hired. Turns out it's been the best company I've ever worked for.
The question is a test for you, but the answer you give, is also a test for the employer.
(This post is not defending the original article, just discussing this specific comment.)
Having never read an HR for Dummies book, and as a pure technical interviewer, I still frequently ask this question. The point is to not think of it as an adversarial question, like I'm going to mark you off for a bad answer.
It's simply to know how you want your career to proceed. Do you want to be an expert at some specific part of the programming world, an experienced generalist (consultant?), an architect, a manager or product lead, start your own startup, ... ?
This is a very important question for you and your manager to be on the same page about. It helps your manager know how to motivate you and what kinds of work will excite you to move your career forward. And it helps you evaluate via small experiences whether your vision matches up with your skills and what you actually enjoy.
I am glad that there are people like you for whom 'running your own company' isn't a bad answer. I think most people are afraid to tell the truth and choose the cliche path about climbing the ladder of success in company X, being afraid of rejection. And to be honest: how many companies out there want someone who tells them right away that experience and money obtained during their job is only to quit on the first moment they feel it's enough to run something on their own?
I am glad that there are people like you for whom 'running your own company' isn't a bad answer.
I answered this way in a recent interview (and got the job). The company owners response was "I think working with us will help you learn a lot about starting your own company." At that point I really wanted to work with them.
And to be honest: how many companies out there want someone who tells them right away that experience and money obtained during their job is only to quit on the first moment they feel it's enough to run something on their own?
Lots of people say it, few do it. It also depends on the job. A job at a small company/startup needs self starters, jack of all trades kind of people. These same people are often the ones who want to do their own thing one day.
This is how I got hired. The manager talked with me for a while, and then looked me straight in the eye and said: in three years, you need to either be a technical lead or start your own company or you're going to be miserable. If you pick which of those paths you want, we'll help you get there through the work you do here.
So honestly, the question is: would you want to work for a company that wants you to lie to them? or a company that wants you to grow and roots for you when you do?
Clearly you met guys with an awesome attitude toward their potential co-workers.
I doubt most of interviewers who ask the cliche setup* do it because they hope the best for you and are glad they found the perfect match, probably they just brought it from their previous experience with job seeking, or have read them in an average HR manual.
*
- what was your biggest success in your field?
- what are your weaknesses?
- where do you see yourself in 5 years?
A long time ago a kind of douchebag asked me them while clicking checkboxes on the screen after every answer. Needless to say I had no motivation to even care to go further in the process. A few years later I've heard from girlfriends just after graduation (non-technical field), they got them on every single one of their interviews, mostly asked by HR managers with no particular work experience. The first one is exceptionally funny when the interviewee is a post-grad.
These 'where do you see yourself in 5 years' questions sound like straight from a 'HR for dummies' book.
Many of these open ended questions came about from large companies hiring physiologist to help build and identify a profile of an individual that the company would like the hire. Organizations such as the FBI use similar strategies as well. The problem is that many smaller organizations that did not want to spend the money or simply did not know to spend the money on professionals started to emulate the larger companies, but they did not posses the answer keys once they had the answers they just left it up to the interviewer to divine whether it was the right answer or not. Read that last sentence again and then read the definition of a Cargo Cult. you will laugh at the mental image I promise. You see, these interviewing practices are simply the same mentality that created Cargo Cults, somewhere along the way they lost the intelligence and are just emulating the process in ritual and then divining the results.
haha, exactly. Mostly that's why I fail to treat these HR questions seriously. In our branch a similar cult would be companies blindly going social - without proper expertise and assets, not knowing what value exactly they want to bring, but it must be social, because everyone big does social. And in the end - they count followers and likes, but are clueless which data and how affects their business.
I ask this question to better understand whether we can provide an environment that will be right for the candidate in 5 years. I dont want to hire someone that wont have a shot at achieving their long term goals with us because it wouldnt be fair to them.
On the flip side, I just hired a new finance person. I wanted someone who can eventually become a controller then CFO. I have no idea if they are really capable of it, but I want them to at least want it and to have demonstrated some activities to have tried working towards it.
It's funny that I had the reverse response. Your post makes you sound like a dick and he sounds like someone who is being totally reasonable. He's looking for excellent people that will fit in well with his team (i.e. won't waste time, has sufficient energy and passion, thinks clearly, communicates well and doesn't sit around loathing their career). Technical skills are important, but putting together a successful team takes more than that. And even if it didn't, it only makes sense, given a pile of resumes with roughly equivalent skills, to filter out the people you don't like to be around. Sucks if you need the job and you're not that type of person, but that's life.
csomar's response is, IMHO, the right reaction to the blog post author's rambling.
What I've found out by experience is that usually recruiters with such restricting requirements aren't ready to back up said requests with the appropriate money. He wants top notch, highly motivated talent. How much is he willing to pay? That's definitely a part of the equation but he's not even mentioning it. If he offers 200-300% the market price then he's right to ask that much skill and dedication, otherwise his pretenses are absolutely unjustified.
- I don't get that he's asking for the moon. He just wants competent people who have a reason to work beyond money and aren't going to be a PITA to him and his team. That seems pretty fundamental to me. Why should it command double or triple an average salary? I don't get it.
- The market will decide. If what he's looking for is rare, he'll have to pay more to get it. If it's not, he'll pay the going rate. Uninformed speculation about what he may or may not be spending on talent seems pointless.
More often than not programmers, even the very good ones, have never learn how to sell themselves. So, they end up working for a fraction of their real value. If this guy ever found someone good via this method, it's almost certainly one of that kind.
well if he wants people who "aren't going to be a PITA to him and his team" He (and I bet its a he) is going to have to stop presenting as such a PITA to work for.
No. He is being an ass in the way he is stating it.
- You send me a stupidly long resume
- forget it. You have annoyed me
- More likely, I will ignore the whole thing
- If you can’t nail it in one sentence, do I really want to look forward to your rambling emails every day?
WOW. Okay Sir. Something else? Now there is nothing wrong with what he is asking for. Can you tell that politely
- Please send me a short and concise resume. Include x, y, and z. That's what matter for me.
- Long emails won't be read fully, because I'm short on time. I might not answer your email because I get lot of them, and I just can't answer them all.
- This doesn't mean your email is not important. It is. Please send it. We'll be in touch.
I think you are missing the point that this is simply intended to provide insight into what is going on inside the head of the person who is doing the hiring. They might be excruciatingly polite in what they say to you directly and personally, but in their mind they are thinking "Why is this fool wasting my time with this stupidly long resume." He's telling the world in blunt terms the reality of what it takes to get hired and how people are going to see you. He's not composing a personal letter to you.
The article's author is just breathing "I'm a dick." There's no need to word the things like he does. "You've annoyed me." Really? Sounds like a drama queen. He should smoke a bowl and get laid once in awhile.
If you want to hire talented people who will carry your company to the top, tone is important. It's not what you say, it's how you say it.
This title could have been written in inverted form: "Why I Will Hire You". Whether someone uses exclusionary or inclusionary principles says a lot about their character to me. It's always good to look out for yourself, and I don't advocate hiring incompetent people, but I'm really thrilled with the people that work around me, and I would never talk to them like this guy does. Never.
Then talk to me about the advantages of working for you. If I'm to work for you for the money, then state that you are offering $200K/year. If I'm interested in health care, then you should have some health insurance package. A good one probably.
I'm skilled, you can see that from the projects I did, worked on, my blog, Github and source code.
Then hire me for a couple of months and see how I fit in the team. Certainly, you should apply your hiring skills to figure out if I'll be a right fit, otherwise you'll waste lots of time hiring/firing/figuring.
Hiring someone for a couple of months just to see how they fit in the team seems the very definition of "wasting lots of time". Nice for you, you get a few months work. Totally sucks for everyone around you if it doesn't work out.
This works when you've narrowed down the candidates to single digits. When you have a pool of dozens, however, you need some way to screen them. He is sharing his screening methods, not his methods of attracting talent (eg, salary, health care, etc). That is an entirely different matter.
But software is a team sport and you do need an element of interviewing for personality, goals, and attitude as well as skills and aptitude.
Seriously, you figure that from a 2 hour interview? I fall in love with a girl which I thought/seemed/was told was a very good one. Turns out she's a complete slut. Knew that only after 2 weeks getting out with her.
Get the person to work with you for few weeks or may be a couple of months. Scan his history (blog, projects, education, work history, github...) and figure out if he'll match your team ethics and he really know what he does.
Exactly. Anyone who thinks they're smart enough to know if a candidate will be a perfect fit after a couple of hour-long interviews, a skills tests and even consensus amongst the team has obviously been promoted to their own special level of incompetence where a quick glance at their own job title is enough to reassure them that they are right and everyone else is wrong. I love those people, as they are easily fooled.
I think there's a business opportunity here, insulating companies from the risks of hiring in order to give them more time to judge the candidate. For example, a recruiter offers the company a skilled, vetted employee, with the promise of paying their salary for the first year. If the company doesn't like them, lay off the worker, risk free. If they like the employee, the pay back the recruiter twice the first year's salary. I think paying twice first year's salary is a pretty good deal for eliminating a huge portion of risk from the hiring process. And you get to learn about the candidate by working with them for a year, instead of asking meaningless questions for a few hours.
Right there is no substitute for a dating period. People should know this, if you think you have the right candidate but have some reservations tell them, give them 2 weeks to prove themselves and you may be surprised at how much talent you where missing. As well, use it with all candidates, remember that person that was a star in the interview but turned out to be a flop? yeah the 2 weeks works for them as well, you can send them packing in the two weeks once you realize your error.
I disagree with most of this post, and I'm glad I didn't apply to any position with him as an interviewer. Specifically:
You can’t tell me why you like your current job - Maybe I hate my current job, and took it to pay the bills. Maybe I actually did take it because I like the challenge. Sure, I could and should give more details about it, but that's a valid response, which shouldn't be thrown out so quickly. While the interviewee should do his/her best to give good answers, it's the interviewer's job to ask intelligent follow-up questions; there's a give and take in an interview.
No career plans or vision - My career plans for most of my life were "keep my options open". That served me very well. It sounds like this interviewer is only interested in people who have been completely focused on a single goal since kindergarten, ignoring everyone else. His loss, I guess.
How many people have you interviewed? I haven't done a lot, but when I was interviewing a lot of people for a couple positions it seemed like everyone said they were "creative" or "liked a challenge."
Claiming they were creative didn't really disqualify, but it didn't make anyone stand out unless they had a couple examples.
You ask general generic questions and you will get general standard answers. Try asking engaging questions that can get more specific answers. Like "can you give me an example where you devised a creative solution to a problem?"
Some employers might be better prepared to ask engaging questions, but the reality is that most interviewers are like the guy in that article. You can fight it all you want, but people who are serious about finding good jobs are better off if they can sell themselves rather than waiting for some HR guy to ask the right questions.
This is a very confrontational and adverserial style of interviewing and hiring.
I get the impression that author is looking for reasons to make the candidate a 'no hire' rather than using those silly questions such as 'tell me a time when....' as a starting to point to open a two way conversation.
My tip is to approach interviews with a positive mind WANTING the candidate to succeed and display their strengths rather than wanting them to fail. You should hire based on positives, not on lack of negatives!
This post really demonstrates how broken interviewing is. These are TERRIBLE and yet still WIDELY USED filters with a high chance of introducing false negatives in the hiring process.
Two examples:
1. The multi year career plans he hints at in a number of places. I personally would be more interested in a candidate with a passion and genuine interest in the job on offer, rather than someone using it as a stepping stone on their ten year plan to get to something tangentially related. I personally don't know what I'll be doing in ten weeks let alone ten years, but a developer it'll probably an interesting and challenging variation of what I'm doing now rather than being somewhere in management.
2. The long CV example is one example of a commonly used signal that tells you precisely nothing about the quality of the candidate. It is a completely arbitrary rule that is no way correlated with their skills or personality. After an initial filter, would it really be so bad spending 5 or so minutes considering and comparing the candidates on offer if that improved your outcomes by even a small percent?
Long CV definitely tells me something about the quality of the candidate.
If I am interviewing someone fresh out of school, I can forgive a rambling resume. However, for an experienced person, I am looking for some ability to present information concisely. It's like a design skill: can you present a focused view of the most relevant information? If you think that more than two pages of information is required to advertise yourself for a job, then you are quite likely lacking that skill.
I still think that a one-page limit is where it's at. Don't put down obvious bullet points. If you were a Windows system admin, don't waste a line on writing that you administered an active directory server. Of course you did that as a Windows sysadmin. No, tell me what you did that made you different than a run-of-the-mill person doing the same job.
One page resume might work for people with not so much experience but it is very hard to put 25+ years of work in one page except obvious "I solve your problems for money" :-).
Just plain listing all places of work with dates can be 20+ lines
How much insight can you get from
1995-1996 Company X , Senior Consultant , project Y ??
This. My Aunt was a career counselor for the past several decades. She won't let me use a resume longer than one page.
You don't need to list ever job you've had since your first part-time job flipping burgers during high school. Just try to figure out what they care about and list that prominently. If they want to know more, they'll ask about it. That said, make sure you summarize things in a way that doesn't make it appear that there are large gaps in your resume, though you may still have problems if your most relevant experience was ten jobs ago.
For a tech job, you want to focus on things like what tools you've used, what problems you've solved and any awards or achievements that you can brag about. If you really feel that you can't leave anything out, put a note on there with a link to an online copy of your CV which, unlike a resume, is supposed to list everything. Then watch how many hits it gets to see how little people care.
As someone who reads a lot of resumes, I regularly see two types of resumes:
1) Those that are roughly 1-2 pages per 10 years of experience with care taken to emphasize relevant and recent experience. Skills and knowledge that I actually care about are placed such that I cannot help but notice them on a first glance. Thought is clearly present in this resume.
2) Those that are roughly 13-21 pages (I have one on my desk that is 17 pages for work experience dating to an internship in 1996). Each job is discussed in mind numbing detail without ever giving me any of the details that I may actually care about. Each job includes an "environment" section that lists every tool that was in the building while that project was going on. Spelling and grammar issues are present. Any skills section will be overloaded with undefined in-house tools and frighteningly basic items (such as a senior developer/architect who lists 11 years of experience with FTP and EMAIL).
When you see an interviewer complaining about resumes that are too long and waste time, understand that they're complaining about the latter. I can easily accept minor issues. It is a huge warning sign when their resume makes me wonder if it is their judgement or motivation that is seriously lacking.
> When you see an interviewer complaining about resumes that are too long and waste time...
No. I'd love to agree with you, but I've seen articles from people just like you (or so they claim) that complain about resumes longer than 1 page. Resumes that include/don't include a cover letter. Resumes that are too short. Resumes that don't cover experiences outside employments. Resumes that do include those experienced.
You see, you mention #2. This guys clearly has a lot of experience. He probably didn't just create that resume just for your job. He's probably been updating a single resume whenever he needs. This means, that resume has gotten him employed at every company on that list.
Think about that.
It's not a problem with people applying, it's with who does the hiring.
While every interviewer has different opinions on what should/should not be present, that's not what I'm talking about. I'm not cargo culting, I'm complaining about receiving garbage.
Extreme length is commonly a sign that the person is too lazy to ever prune or clean up things. And my complaint about excessive length is "if they cannot bother to revisit it, why should I?"
I'm aware that every resume is not created from scratch just for me. Still, I should be able to create a guess as to who the person is, what they're looking for, and (generally) why they might be a good fit. If not, why am I reading their resume at all? What am I possibly getting out of it?
While updating resumes usually means adding, that doesn't have to mean that a 1/2 page discussion on tweaking spreadsheets for a law office in 1992 will stand there until retirement. Do I really need to see that someone has experience with Visual Studio 2010, 2008, 2005, 2003, 2000? How about every version of every Office product that they have ever used?
How about a skills section that lists 4 versions of MS DOS? Sure, there's a possibility we have a legacy system to update, but really, if you want to include that stuff, separate the (likely to be) relevant information so that I can find it easily without wading through crap like your Code Warrior Certification in 1995.
I'm not your mother and I'm not going to do the equivalent of cleaning your room just to find out if you might be worth a phone call.
> I'm not your mother and I'm not going to do the equivalent of cleaning your room just to find out if you might be worth a phone call.
And you shouldn't. But, what you say conflicts, in some way, with your stated goal:
> I should be able to create a guess as to who the person is, what they're looking for, and (generally) why they might be a good fit.
And guess what? That 15-page resume is looking for a place where a 15-page resume will fit in.
My point was that every person who has ever talked about the hiring process and how to put together a resume with the "I read resumes every day" credential is giving you advice on how to get the interview with them: nothing more.
With that in mind, why should I customize my resume for you? Rather, I should write a resume that represents me. If you don't like the resume, you won't interview with me. And that, hopefully, means I wouldn't fit in.
Listen, I've had interviews canceled on me because I play board games (at a company that promotes the fact that they have XBox 360s).
So, I'm not saying you are wrong. I'm just saying that your advice is, at least in my opinion, advice on what you look for. You have no need to defend what your criteria is, I wasn't attacking it. I apologize if you think I was.
In some ways, you should thank the 15-page resumes coming in. They make your decision much easier (I'd assume). If that person adjusted their resume merely to get the interview, are they really the type of person you want to hire?
I will go into every interview expecting that we are equals. You know what you or your company already is and what it wants. I know what I am and what I want. Then, we decide together. Interviewing/recruiting does not give you high-status.
The interview failures described in the article occur when neither party understands this.
It blows my mind that so many people don't understand that as an interviewee they are just as responsible for deciding if this relationship is a good fit as the interviewer. Otherwise you may end up jumping through the correct hoops only to get hired by a guy like this.
I find many interviewers have no idea that it's a two way street as well. I guess it shortens the interview for me though. I don't want to work for someone who only wants answers, not a conversation.
What a completely horrible way to interview and speak to people.
No career plans or vision Why would this matter to the interviewer? I just can't get over how ridiculous of an answer he provides. Why would he care what my career plans and vision (whatever that is) are? Who can honestly plot out the next 10 years of their life? Very few, and I'd be wary of anyone who claims they could.
I'm not surprised this person is not finding the right candidates for his company, but I think he has no clue why.
I'm not surprised this person is not finding the right candidates for his company, but I think he has no clue why.
Where does he say that he is having trouble finding people?
While I agree that the example he provides is a rare case, it's not entirely a stupid question. (However, as I said elsewhere about other interview questions, it definitely could use a more original approach.) I think many interviewers are worried about hiring someone who is just going to use the company as a year-long hopping stone, and therefore won't be committed.
The guy is rejecting more than 99% of people who make it to an onsite interview. Clearly they aren't finding the right candidates. And they must be totally desperate if they're willing to still do interviews with that low a hit rate.
As someone who has done the interviewing thing, I can see where this article is coming from. I don't really buy into all of it though. All this stuff about being a great communicator. That is cool but not always required. I have spent a lot of time working with amazing people who are crap communicators and crap people who are great communicators.
But - I am sure a lot of people interviewing use indicators like these so it it worth knowing about them.
Finally, on the CV thing. This is a hard issue because agents look for buzz words. If you've done a lot of stuff you need to write a lot to get all the buzz words in. That is the only way the agent will forward our CV. Then - you cannot tailor the CV to the job because you did not submit one for that job, you submitted one for buzz words.
Yeah, it tends to make me a bit irritable after the 500th time I've seen a resume touting the candidate's skills with DreamWeaver, so I sympathize. But while the article is a well-intentioned rant, it's still a rant.
In short, if you're looking for a job, try to put yourself in the position of the interviewer and adjust your approach accordingly. Don't go in cold, and don't assume the interviewer will make allowances for you.
The thing about this interview process is that you'll lose those candidates who have potential and can thrive in correct environment but:
a) Currently work in a job that they don't really like and, hence, are looking to switch (because they cannot come up with a satisfactory answer for: "You can’t tell me why you like your current job")
Also, since they don't know much about your company besides second-hand information, they cant answer: "why you think this job will give you the same passion". Interview is a conversation, you'll have to tell them what your company culture is and how it can benefit potential employees.
b) Candidates who are fresh out of college / don't have much experience.
c) Candidates who are probably good enough for your job but aren't good enough to pass the, very high bar, you've set up for them.
So it depends on the profile for which you're hiring and the prerequisites you are looking for. I personally won't mind if an interviewee can't answer most of these questions but can do the job I'm giving and has done something simiiar to it in the past with reasonable success and is a good cultural fit in my organisation based on what I can deduce during the interview.
You know what I really hate? Being asked about my career plans or vision. Wanna know what my career plans are?
To create something cool and reach financial independence in X amount of years. But first I need to pay for food for the next couple of months until somebody better than Your Company starts begging for programmers and sending me emails. And to be honest, your project likely won't be able to hold my interest for more than a few months, it will become boring and routine, nothing like anything fun I'll be working on in my own time.
Most interviewers hate that answer. (which is why I freelance, it's perfect)
PS: I have yet to give the answer that directly, but I should try every time I go in to talk about a freelancing project and it turns into an interview.
For someone who said he doesn't want to a long resume that rambles on forever he sure had a long blog post that rambled on with very little content.
Attacking each point:
You send me a stupidly long resume
Some recruiters/HR desks look for resumes with specific keywords, and we need to tailor our resumes to get past those (admittedly retarded) filters. As an interviewee, I understand that and have made my resume longer to get past them to the people that actually look at it. As an interviewer, I've rarely looked at the resume until the interview, and only scanned over it to look for things that I can ask about, in addition to our normal quetions.
You can’t tell me why you like your current job
You don't have to like your current job. Especially in this economy, some people are glad to have jobs. Of course, it'd be nice if you like your job, but then again, that's why he's interviewing. Whether or not a person likes a previous job has nothing to say about whether or not he'll like his next job, unless, of course, you're looking for a spineless twit who will go with the flow regardless of how they treat him.
It's more important to recognize a cultural fit and find someone that will get along with the employees, but again, this can vary wildly. I worked at a startup and we interviewed a manager from a large corporate company to be our BA. We went into the interview thinking there's no way we'll like this guy, but it turned out he was awesome, and a great cultural fit too.
No career plans or vision
Not everyone has a long-term. Not everyone knows what they'll be doing in five years, especially when they're younger. My first two jobs, I told them I'd be gone within a year and a half. I don't remember saying it, but when I quit a year a half later, they aid I told them that during the interview and they just didn't believe me. The better question is what will it take to keep me here for five years, and what is your firm going to do for it as well? Of course, people most likely can't answer this question until they've had a few jobs under their belt, so they realize what they like and don't like.
No skills
There's really the primary thing that matters.
Answer my skills with conjecture
I didn't read this far, but it sounds like 'Don't BS me'. I'll agree there as well.
I agree with csomar. I probably wouldn't work for you.
>If I have to spend more than 30 seconds finding out what you have accomplished, forget it.
Well then, Don't expect me to even bother writing a cover letter or tailor my resume. In fact, if your only going to be scanning over my resume in 30 seconds why, on earth, should I even spend any time filling out your form to send you my resume? When I send people my resume, I at the very least expect them to read through it. If my skill set matches what you are looking for and you are thinking of an interview, I expect you to at the very least Google my name, or check out my website/github which I conveniently include as a QR code.
>The worst answers? “Well I like the challenge” or some other BS.
Well, Enjoy working with the worst developers possible. Most of the best guys I know will take a job with worse pay, less benefits, and further commute if the work sounds interesting (read: challenging). "I enjoy the challenge" is probably one of the best answers to why you want to work somewhere. Unless, of course the work you do involves mundane repetitive tasks every single day then you probably don't want developers that enjoy challenge, because they will leave very quickly.
You take this stance of "I have the elixir of life and you will bend over backwards to get it because you are desperate". So the only people that do end up bending over are the ones who are really desperate.
-He expects he won't hire me in the first five minutes? If in the first five minutes I get that vibe I no longer wish to have the job.
-Tailor-made resume for his job? As if people are supposed to create new resumes for every job that they apply for? Get serious. Plus different companies expect different style of resumes since there is no standard and what amounts to close to standard changes every couple of years. What he wants is people to magically read his mind to craft a resume just for him to meet his expectations.
- He won't hire if I can't say why I love my current job? If I love my current job then there's not much reason to leave it, now is there? Plus, he claims to have a BS detector but he seems to be asking for BS from the applicant.
- No career plans or vision? For most people laying out five year plans is BS, which means he won't hire you. What good does such a question do for anyone anyway? Looking back over my career I've only had one job that I actually planned for. The rest are from changes in things I can't control with changes in what interests me.
- I agree with the no skills part. As someone who's been on the hiring side of the table there's nothing more annoying when someone can't back up what's on their resume.
- "Don’t sit there and tell me what you would do in the future. I didn’t ask what you would do, I asked what you did." Um, yes you did, it was two bullet points ago.
- He apparently requires the perfect candidate. I wonder how many people he actually manages to hire and how many of them stay for their "career"?
- He talks of bad advice out there discussing the topic of his post and he seems to assume his will not get lumped into that list. I would say it's the same as any other post on the topic, some good and some bad.
He sounds a lot like the kind of guy that has a high turnover rate of first-year hires who leave for more money and he can't figure out why.
"If I have to spend more than 30 seconds finding out what you have accomplished, forget it."
Not to worry. I will only work for someone who can manage to conquer problems of scale such as skimming a resume and finding pertinent points. If you are unable or unwilling to do so, we'll eventually have a problem and I'll be better off elsewhere.
I am expecting you to be one of the 99%+ people who I know I won’t hire in the first 5 minutes.
If you can't narrow down resumes and phone interviews to candidates with better than a 1% chance of being accepted, then your interviewing pre-screening process is flawed. What other processes in our everyday work will also be flawed?
You send me a stupidly long resume
90% of all written correspondence (from customers, users, collaborators, vendors, etc.) is too long. Do you think they're all stupid, too?
You have annoyed me.
You're a manager. Your job is to properly deal with issues that would annoy others. Why would anyone want to work for someone so easily annoyed?
...do I really want to look forward to your rambling emails every day?
Do I really want to look forward to your sour attitude every day?
You can’t tell me why you like your current job
If I liked my current job, I wouldn't be here.
I don’t hire awesome people who don’t have the right skill mix.
Here's a clue: technologies change. By definition, anyone with the "right skill mix" won't have the "right skill mix" for long. Amesome people adapt. But how would you even know that if you don't hire them?
No career plans or vision
I've been programming for 33 years and still have no idea what I want to do when I grow up. This is an interview for an open job, not Dr. Phil.
If you don’t think well on your feet, spend some time reading through and practicing situational interview questions.
Are you serious? I'm a programmer, not an Americas Got Talent contestant. What you see is what you get.
If you are missing even one, I’m probably going to pass you up for someone who doesn’t.
Wait a minute. You want to hire perfect people, but you also want them to have "career plans or vision"?
I have a super BS detector
Obviously not, since so many of your questions can only be answered with BS.
The End
That's just about the only thing you've said that I agree with.
You sound like you have a serious attitude problem. I can't imagine working for someone like you. But thanks for writing this. You've solved many problems in advance. I won't be applying. And I don't imagine many people like me will be either.
> Do I really want to look forward to your sour attitude every day?
This sums it up for me. The author sounds like a grumpy person who would be terrible to work for. I also suspect many of these rejections are self-fulfilling prophecies. When you're actively looking for a reason to reject candidates, you're probably going to find one.
You summed it up well, this guy needs to stay as far away from interviewing as possible. This attitude is why people can't find the 10Xers, they interviewing process is set up to filter them out. Your observation here:
Here's a clue: technologies change. By definition, anyone with the "right skill mix" won't have the "right skill mix" for long. Amesome people adapt. But how would you even know that if you don't hire them?
gets to the heart why they cant. 10Xers are not a technology they are personality and a attitude. Hell some of them are not ever that great at some of the technologies they use, but they know how to use the parts they need to get them to the finish line. They know the principles of elegance in clean code, and simple systems that are only as complex as they need to be.
These people are not showing up to the door of people that interview like the author, and if they do they are not taking the position and probably recommending to other 10Xers to go ahead and avoid the interview.
I get the feeling from reading the article, that the author has not learned how to spot technical talent and is growing frustrated with it.
Interviews are a two way street. If I am applying for a job, my role during the interview is to convince you why I am a worthwhile hire, your role during the interview is to convince me that you are a worthwhile employer. If he was one of my clients I would disassociate myself from him very quickly.
As for his 5 points, I wonder if he realises that all 5 inversely apply to him just as much as they do to the candidate being interviewed.
1.Show me you can get things done. This means you can set realistic deadlines for projects and meet them consistently. You must be a good motivator.
2.Show me you are intelligent. I will ask you questions to discern how in touch you are with todays market. I don't care if you've interviewed a dozen people for this job, I want to know if you've actually read my resume.
3.Show me how I fit into your vision. Truthfully, we’ll work best together if you sincerely think I am the best person for this job in the long run. I want to know how you can help me succeed in my career, Tell me.
4.Be highly skilled. If your job advert says that you need a highly skilled Developer then don't have me sitting in a corner refactoring shitty code for the first 6 months.
5.Be Passionate. If I feel like the interview process is boring you, I will end the interview prematurely but politely.
this is absolutely true. almost 100% of job ads are terrible. They are focused exclusively on what the company wants. Instead the ads should be marketing to attract the best. The ads should explain why someone great would want to work there.
Obviously not, since so many of your questions can only be answered with BS.
Then we get to his example of a "good" answer for career plans: yet another instance of "In this many years, I see myself that many steps up the corporate ladder. … communication … leadership … responsibility …"
Also this: "Let me know your passionate or don’t waste my time." (you're!)
This is why I love being a contractor / consultant. Clients don't ask for a little lap dance and a smile before we can do business, like this guy seems to expect.
They have a job to do that they think I can do, I give a quote, they say yes or no (usually yes, if we went this far). I do it, they pay me.
No resume-this, resume-that, what's your vision, are you passionate, what do you love or hate. I hate being in an office with a stranger in the middle of the afternoon, talking about my passions.
It's great how the same sort of folks who put out these diatribes on how easy it is to run afoul of their hiring processes will also complain about how very difficult it has been to find qualified candidates.
90% of all written correspondence (from customers, users, collaborators, vendors, etc.) is too long. Do you think they're all stupid, too?
"
I agree with most of your post, but after doing a lot of interviews as the hiring manager, I have to agree that resumes should be short. I won't exclude a candidate just for sending a resume that is long, but as a general rule, don't expect me to go past page 2, especially for an entry-to-mid level position.
Pretty much exactly right. 1 difference for me, though. I already know what I want to be when I grow up:
A programmer!
Yes, I've reached the end of my career. I'm where I want to be, and I don't want to change. I don't want to be a manager, team leader, or otherwise do anything other than programming. If there were any change I wanted, it would be 'do fewer non-programming things'.
THANK YOU! I feel the same way. Why is it that people who supposedly love programming are somehow expected to no longer want to be programmers at some point in their career? Being a great manager / team leader takes a whole different skill set than being a great coder.
There's a difference between "excellent at communicating" and "obviously does not care".
An excellent example of the latter is the presence of spelling errors that could have been fixed with spell-check, completely random font changes due to copy-and-paste, etc. These typically are just the superficial signs that no thought was put into the content.
It's like showing up for an interview in a dirty t-shirt and sneakers. I'm not looking for excellent fashion sense; I'm looking for a basic awareness of the world around them.
Of the 100 people who look at his website searching for employment 90 are disinterested due to his poor grammar, spelling, and punctuation skills. Another eight realize that a professional services site with HTTP 403 and 404 errors isn’t that professional. One more reads the "official company blog" and concludes that the owner is a douche bag. The remaining 1% apply simply to keep their H1B status alive.
So in his own special way that guy is telling the 1% to f*ck off. Well played.
I find it amusing that he starts off with a rant about long resumes. Then half of what follows goes on to talk about all the extensive information you have to communicate on your CV just to get an interview.
I severely disagree with the attitude conveyed. People would do well to remember that a work arrangement is mutually beneficial, always. You take a job because it is in your interest to do so. You are offered a job because it is in their interest to do so. No one employs someone while taking a loss on them, yet companies treat interviewees as if they would be lucky to land such a wonderful job.
If this attitude came out in my interview, I'd immediately walk out. If you're treating me in this way before I even work for you, odds are it's not ever going to get better, only worse.
I really don't understand the offence some people seem to be taking from this blog post. The author's listing, directly and to the point, what he wants to see from interviewees.
You might not like the tone of the author's writing, but having sat on the other side of the interview table, it is thoroughly depressing when a candidate tells you "Yeah, I just want a job - money, isn't it?", when you know that the role available is great, and someone who wants to care about will really enjoy it.
It is all perspective , you like to think that role is great but maybe is not so much as you think. Maybe you just don't know better
Don't get me wrong; we all have to pay the rent. There there are indisputably times when, guess what, one just needs a damned job that'll pay the bills.
But for a lot of smaller companies with cool little projects? Yeah, I think it's totally reasonable for them to discriminate on that level.
Given that most people need a job to pay the bills, it seems that "I need the money" has to be one of the most truthful answers in a job interview (or "I want more money"). That's why it's a job and not just a fun thing to do. A lot of talented people probably wouldn't have a job if they didn't need it, but since they do they curtail their own desires to fit the needs of an employer in exchange for money. A lot of really great work gets done this way, but somehow it seems bad to say it.
It seems somewhere along the line, every person who is aspiring to become someone great in the industry gets the wrong cue. They see some conceited individual writing blog posts about how great they are, and they assume mimicking this style of writing will make them equally as great. The truth is: most of us barely tolerate this attitude from those who are truly great because we don't have much choice. Until you are truly great (i.e. on the cover of time magazine, and solving the largest problems we all face with ease), you would do better to present yourself with humility.
That you thought it appropriate to write a blog post with simply the title of "Why I won't hire you," is the reason "Why I will never interview with you." (And, for many others as well, I'm sure.) It has little to do with the content (although in fact, the content only gets worse with conceit and self-inflating statements) and everything to do with your attitude.
Who wants to work for someone who already thinks they're better than the majority of humanity? I'd want to work for a manager who knows how to communicate effectively without being abrasive, and who has excellent skills in resolving conflict and helping their team grow to their maximum potential. Everything about your blog post suggest the opposite combined with such a level of hubris, that I could only imagine working for you would be the worst job I've ever had.
The best developers I've ever worked with tend to lack career plans. If you're sufficiently happy with your life that you don't need a change strategy, that's pretty cool.
Are you sure they didn't? Perhaps, like me, they have already finished their career plan and they are working their dream job.
That's the thing these interviews fail to take into account. They assume that everyone wants more, when that's not always the case. Happiness means knowing when you have what you want, and enjoying it.
If there were more engineers than jobs and we were all fiercely competing for scraps, I would say ok - it's a "buyers market" and we are forced to put up with attitudes like this.
The situation is very different however. In my experience, top talent either a) have their own company or b) are well-looked after by their current employer (at least one would hope so) so they need to actively lured away; how about you tell me why I SHOULD work for you rather than give all the reasons why I can't?
127 comments
[ 3.8 ms ] story [ 218 ms ] threadI don't know about that, but my experience suggests that most CVs you get for a job interview will be unsuitable.
@Llambda - isn't the process of the interview also the process of finding a suitable candidate?
Because you are a dick.
Now who are you? What are you going to give me in return? Why should I tell you that I love my job and my career. Why should I tell you about my vision and plans? What are you really looking for in that.
The hiring should be a lot simpler:
- You have a problem. You need someone with the right skills, and hire him.
- I have a problem (need money). I pick a job that I have the skills for.
Thinking the way you do, accepting your daily bull-shit and philosophy (worse, making myself sound like I enjoy and I belong to it) is only a sign for me that you are the wrong person to work for.
These 'where do you see yourself in 5 years' questions sound like straight from a 'HR for dummies' book. I would really appreciate if an interviewer reading this post explained me what such cliches are trying to test, other than BS skills. Cliche question => cliche response.
What do I say? If I reach to high I endanger my own prospects at being hired. A buddy of mine answered the "see yourself in 5 years" question with "Probably working at Google". Needless to say he wasn't hired.
If I reach too low I sound like a deadbeat. If I answer with something like "Working at the position you are hiring me for" I sound like I have no vision and no drive.
There isn't a right answer to this question. Because the only right answer is "cliche".
The question is a test for you, but the answer you give, is also a test for the employer.
Having never read an HR for Dummies book, and as a pure technical interviewer, I still frequently ask this question. The point is to not think of it as an adversarial question, like I'm going to mark you off for a bad answer.
It's simply to know how you want your career to proceed. Do you want to be an expert at some specific part of the programming world, an experienced generalist (consultant?), an architect, a manager or product lead, start your own startup, ... ?
This is a very important question for you and your manager to be on the same page about. It helps your manager know how to motivate you and what kinds of work will excite you to move your career forward. And it helps you evaluate via small experiences whether your vision matches up with your skills and what you actually enjoy.
I answered this way in a recent interview (and got the job). The company owners response was "I think working with us will help you learn a lot about starting your own company." At that point I really wanted to work with them.
And to be honest: how many companies out there want someone who tells them right away that experience and money obtained during their job is only to quit on the first moment they feel it's enough to run something on their own?
Lots of people say it, few do it. It also depends on the job. A job at a small company/startup needs self starters, jack of all trades kind of people. These same people are often the ones who want to do their own thing one day.
So honestly, the question is: would you want to work for a company that wants you to lie to them? or a company that wants you to grow and roots for you when you do?
I doubt most of interviewers who ask the cliche setup* do it because they hope the best for you and are glad they found the perfect match, probably they just brought it from their previous experience with job seeking, or have read them in an average HR manual.
*
- what was your biggest success in your field?
- what are your weaknesses?
- where do you see yourself in 5 years?
A long time ago a kind of douchebag asked me them while clicking checkboxes on the screen after every answer. Needless to say I had no motivation to even care to go further in the process. A few years later I've heard from girlfriends just after graduation (non-technical field), they got them on every single one of their interviews, mostly asked by HR managers with no particular work experience. The first one is exceptionally funny when the interviewee is a post-grad.
Many of these open ended questions came about from large companies hiring physiologist to help build and identify a profile of an individual that the company would like the hire. Organizations such as the FBI use similar strategies as well. The problem is that many smaller organizations that did not want to spend the money or simply did not know to spend the money on professionals started to emulate the larger companies, but they did not posses the answer keys once they had the answers they just left it up to the interviewer to divine whether it was the right answer or not. Read that last sentence again and then read the definition of a Cargo Cult. you will laugh at the mental image I promise. You see, these interviewing practices are simply the same mentality that created Cargo Cults, somewhere along the way they lost the intelligence and are just emulating the process in ritual and then divining the results.
And I still got the job.
On the flip side, I just hired a new finance person. I wanted someone who can eventually become a controller then CFO. I have no idea if they are really capable of it, but I want them to at least want it and to have demonstrated some activities to have tried working towards it.
What I've found out by experience is that usually recruiters with such restricting requirements aren't ready to back up said requests with the appropriate money. He wants top notch, highly motivated talent. How much is he willing to pay? That's definitely a part of the equation but he's not even mentioning it. If he offers 200-300% the market price then he's right to ask that much skill and dedication, otherwise his pretenses are absolutely unjustified.
- I don't get that he's asking for the moon. He just wants competent people who have a reason to work beyond money and aren't going to be a PITA to him and his team. That seems pretty fundamental to me. Why should it command double or triple an average salary? I don't get it.
- The market will decide. If what he's looking for is rare, he'll have to pay more to get it. If it's not, he'll pay the going rate. Uninformed speculation about what he may or may not be spending on talent seems pointless.
- You send me a stupidly long resume
- forget it. You have annoyed me
- More likely, I will ignore the whole thing
- If you can’t nail it in one sentence, do I really want to look forward to your rambling emails every day?
WOW. Okay Sir. Something else? Now there is nothing wrong with what he is asking for. Can you tell that politely
- Please send me a short and concise resume. Include x, y, and z. That's what matter for me.
- Long emails won't be read fully, because I'm short on time. I might not answer your email because I get lot of them, and I just can't answer them all.
- This doesn't mean your email is not important. It is. Please send it. We'll be in touch.
This title could have been written in inverted form: "Why I Will Hire You". Whether someone uses exclusionary or inclusionary principles says a lot about their character to me. It's always good to look out for yourself, and I don't advocate hiring incompetent people, but I'm really thrilled with the people that work around me, and I would never talk to them like this guy does. Never.
I'm skilled, you can see that from the projects I did, worked on, my blog, Github and source code.
Then hire me for a couple of months and see how I fit in the team. Certainly, you should apply your hiring skills to figure out if I'll be a right fit, otherwise you'll waste lots of time hiring/firing/figuring.
If you were hiring someone to dig a hole for you, this may be true.
But software is a team sport and you do need an element of interviewing for personality, goals, and attitude as well as skills and aptitude.
Seriously, you figure that from a 2 hour interview? I fall in love with a girl which I thought/seemed/was told was a very good one. Turns out she's a complete slut. Knew that only after 2 weeks getting out with her.
Get the person to work with you for few weeks or may be a couple of months. Scan his history (blog, projects, education, work history, github...) and figure out if he'll match your team ethics and he really know what he does.
Because you are a dick.
You do realise that you're being just as confrontational as the post's author?
You can’t tell me why you like your current job - Maybe I hate my current job, and took it to pay the bills. Maybe I actually did take it because I like the challenge. Sure, I could and should give more details about it, but that's a valid response, which shouldn't be thrown out so quickly. While the interviewee should do his/her best to give good answers, it's the interviewer's job to ask intelligent follow-up questions; there's a give and take in an interview.
No career plans or vision - My career plans for most of my life were "keep my options open". That served me very well. It sounds like this interviewer is only interested in people who have been completely focused on a single goal since kindergarten, ignoring everyone else. His loss, I guess.
Claiming they were creative didn't really disqualify, but it didn't make anyone stand out unless they had a couple examples.
I get the impression that author is looking for reasons to make the candidate a 'no hire' rather than using those silly questions such as 'tell me a time when....' as a starting to point to open a two way conversation.
My tip is to approach interviews with a positive mind WANTING the candidate to succeed and display their strengths rather than wanting them to fail. You should hire based on positives, not on lack of negatives!
This post really demonstrates how broken interviewing is. These are TERRIBLE and yet still WIDELY USED filters with a high chance of introducing false negatives in the hiring process.
Two examples:
1. The multi year career plans he hints at in a number of places. I personally would be more interested in a candidate with a passion and genuine interest in the job on offer, rather than someone using it as a stepping stone on their ten year plan to get to something tangentially related. I personally don't know what I'll be doing in ten weeks let alone ten years, but a developer it'll probably an interesting and challenging variation of what I'm doing now rather than being somewhere in management.
2. The long CV example is one example of a commonly used signal that tells you precisely nothing about the quality of the candidate. It is a completely arbitrary rule that is no way correlated with their skills or personality. After an initial filter, would it really be so bad spending 5 or so minutes considering and comparing the candidates on offer if that improved your outcomes by even a small percent?
Sigh....
If I am interviewing someone fresh out of school, I can forgive a rambling resume. However, for an experienced person, I am looking for some ability to present information concisely. It's like a design skill: can you present a focused view of the most relevant information? If you think that more than two pages of information is required to advertise yourself for a job, then you are quite likely lacking that skill.
I still think that a one-page limit is where it's at. Don't put down obvious bullet points. If you were a Windows system admin, don't waste a line on writing that you administered an active directory server. Of course you did that as a Windows sysadmin. No, tell me what you did that made you different than a run-of-the-mill person doing the same job.
You don't need to list ever job you've had since your first part-time job flipping burgers during high school. Just try to figure out what they care about and list that prominently. If they want to know more, they'll ask about it. That said, make sure you summarize things in a way that doesn't make it appear that there are large gaps in your resume, though you may still have problems if your most relevant experience was ten jobs ago.
For a tech job, you want to focus on things like what tools you've used, what problems you've solved and any awards or achievements that you can brag about. If you really feel that you can't leave anything out, put a note on there with a link to an online copy of your CV which, unlike a resume, is supposed to list everything. Then watch how many hits it gets to see how little people care.
1) Those that are roughly 1-2 pages per 10 years of experience with care taken to emphasize relevant and recent experience. Skills and knowledge that I actually care about are placed such that I cannot help but notice them on a first glance. Thought is clearly present in this resume.
2) Those that are roughly 13-21 pages (I have one on my desk that is 17 pages for work experience dating to an internship in 1996). Each job is discussed in mind numbing detail without ever giving me any of the details that I may actually care about. Each job includes an "environment" section that lists every tool that was in the building while that project was going on. Spelling and grammar issues are present. Any skills section will be overloaded with undefined in-house tools and frighteningly basic items (such as a senior developer/architect who lists 11 years of experience with FTP and EMAIL).
When you see an interviewer complaining about resumes that are too long and waste time, understand that they're complaining about the latter. I can easily accept minor issues. It is a huge warning sign when their resume makes me wonder if it is their judgement or motivation that is seriously lacking.
No. I'd love to agree with you, but I've seen articles from people just like you (or so they claim) that complain about resumes longer than 1 page. Resumes that include/don't include a cover letter. Resumes that are too short. Resumes that don't cover experiences outside employments. Resumes that do include those experienced.
You see, you mention #2. This guys clearly has a lot of experience. He probably didn't just create that resume just for your job. He's probably been updating a single resume whenever he needs. This means, that resume has gotten him employed at every company on that list.
Think about that.
It's not a problem with people applying, it's with who does the hiring.
Extreme length is commonly a sign that the person is too lazy to ever prune or clean up things. And my complaint about excessive length is "if they cannot bother to revisit it, why should I?"
I'm aware that every resume is not created from scratch just for me. Still, I should be able to create a guess as to who the person is, what they're looking for, and (generally) why they might be a good fit. If not, why am I reading their resume at all? What am I possibly getting out of it?
While updating resumes usually means adding, that doesn't have to mean that a 1/2 page discussion on tweaking spreadsheets for a law office in 1992 will stand there until retirement. Do I really need to see that someone has experience with Visual Studio 2010, 2008, 2005, 2003, 2000? How about every version of every Office product that they have ever used?
How about a skills section that lists 4 versions of MS DOS? Sure, there's a possibility we have a legacy system to update, but really, if you want to include that stuff, separate the (likely to be) relevant information so that I can find it easily without wading through crap like your Code Warrior Certification in 1995.
I'm not your mother and I'm not going to do the equivalent of cleaning your room just to find out if you might be worth a phone call.
And you shouldn't. But, what you say conflicts, in some way, with your stated goal:
> I should be able to create a guess as to who the person is, what they're looking for, and (generally) why they might be a good fit.
And guess what? That 15-page resume is looking for a place where a 15-page resume will fit in.
My point was that every person who has ever talked about the hiring process and how to put together a resume with the "I read resumes every day" credential is giving you advice on how to get the interview with them: nothing more.
With that in mind, why should I customize my resume for you? Rather, I should write a resume that represents me. If you don't like the resume, you won't interview with me. And that, hopefully, means I wouldn't fit in.
Listen, I've had interviews canceled on me because I play board games (at a company that promotes the fact that they have XBox 360s).
So, I'm not saying you are wrong. I'm just saying that your advice is, at least in my opinion, advice on what you look for. You have no need to defend what your criteria is, I wasn't attacking it. I apologize if you think I was.
In some ways, you should thank the 15-page resumes coming in. They make your decision much easier (I'd assume). If that person adjusted their resume merely to get the interview, are they really the type of person you want to hire?
The interview failures described in the article occur when neither party understands this.
I find many interviewers have no idea that it's a two way street as well. I guess it shortens the interview for me though. I don't want to work for someone who only wants answers, not a conversation.
No career plans or vision Why would this matter to the interviewer? I just can't get over how ridiculous of an answer he provides. Why would he care what my career plans and vision (whatever that is) are? Who can honestly plot out the next 10 years of their life? Very few, and I'd be wary of anyone who claims they could.
I'm not surprised this person is not finding the right candidates for his company, but I think he has no clue why.
Where does he say that he is having trouble finding people?
While I agree that the example he provides is a rare case, it's not entirely a stupid question. (However, as I said elsewhere about other interview questions, it definitely could use a more original approach.) I think many interviewers are worried about hiring someone who is just going to use the company as a year-long hopping stone, and therefore won't be committed.
But - I am sure a lot of people interviewing use indicators like these so it it worth knowing about them.
Finally, on the CV thing. This is a hard issue because agents look for buzz words. If you've done a lot of stuff you need to write a lot to get all the buzz words in. That is the only way the agent will forward our CV. Then - you cannot tailor the CV to the job because you did not submit one for that job, you submitted one for buzz words.
In short, if you're looking for a job, try to put yourself in the position of the interviewer and adjust your approach accordingly. Don't go in cold, and don't assume the interviewer will make allowances for you.
a) Currently work in a job that they don't really like and, hence, are looking to switch (because they cannot come up with a satisfactory answer for: "You can’t tell me why you like your current job")
Also, since they don't know much about your company besides second-hand information, they cant answer: "why you think this job will give you the same passion". Interview is a conversation, you'll have to tell them what your company culture is and how it can benefit potential employees.
b) Candidates who are fresh out of college / don't have much experience.
c) Candidates who are probably good enough for your job but aren't good enough to pass the, very high bar, you've set up for them.
So it depends on the profile for which you're hiring and the prerequisites you are looking for. I personally won't mind if an interviewee can't answer most of these questions but can do the job I'm giving and has done something simiiar to it in the past with reasonable success and is a good cultural fit in my organisation based on what I can deduce during the interview.
To create something cool and reach financial independence in X amount of years. But first I need to pay for food for the next couple of months until somebody better than Your Company starts begging for programmers and sending me emails. And to be honest, your project likely won't be able to hold my interest for more than a few months, it will become boring and routine, nothing like anything fun I'll be working on in my own time.
Most interviewers hate that answer. (which is why I freelance, it's perfect)
PS: I have yet to give the answer that directly, but I should try every time I go in to talk about a freelancing project and it turns into an interview.
Attacking each point:
You send me a stupidly long resume
Some recruiters/HR desks look for resumes with specific keywords, and we need to tailor our resumes to get past those (admittedly retarded) filters. As an interviewee, I understand that and have made my resume longer to get past them to the people that actually look at it. As an interviewer, I've rarely looked at the resume until the interview, and only scanned over it to look for things that I can ask about, in addition to our normal quetions.
You can’t tell me why you like your current job
You don't have to like your current job. Especially in this economy, some people are glad to have jobs. Of course, it'd be nice if you like your job, but then again, that's why he's interviewing. Whether or not a person likes a previous job has nothing to say about whether or not he'll like his next job, unless, of course, you're looking for a spineless twit who will go with the flow regardless of how they treat him.
It's more important to recognize a cultural fit and find someone that will get along with the employees, but again, this can vary wildly. I worked at a startup and we interviewed a manager from a large corporate company to be our BA. We went into the interview thinking there's no way we'll like this guy, but it turned out he was awesome, and a great cultural fit too.
No career plans or vision
Not everyone has a long-term. Not everyone knows what they'll be doing in five years, especially when they're younger. My first two jobs, I told them I'd be gone within a year and a half. I don't remember saying it, but when I quit a year a half later, they aid I told them that during the interview and they just didn't believe me. The better question is what will it take to keep me here for five years, and what is your firm going to do for it as well? Of course, people most likely can't answer this question until they've had a few jobs under their belt, so they realize what they like and don't like.
No skills
There's really the primary thing that matters.
Answer my skills with conjecture
I didn't read this far, but it sounds like 'Don't BS me'. I'll agree there as well.
I agree with csomar. I probably wouldn't work for you.
Well then, Don't expect me to even bother writing a cover letter or tailor my resume. In fact, if your only going to be scanning over my resume in 30 seconds why, on earth, should I even spend any time filling out your form to send you my resume? When I send people my resume, I at the very least expect them to read through it. If my skill set matches what you are looking for and you are thinking of an interview, I expect you to at the very least Google my name, or check out my website/github which I conveniently include as a QR code.
>The worst answers? “Well I like the challenge” or some other BS.
Well, Enjoy working with the worst developers possible. Most of the best guys I know will take a job with worse pay, less benefits, and further commute if the work sounds interesting (read: challenging). "I enjoy the challenge" is probably one of the best answers to why you want to work somewhere. Unless, of course the work you do involves mundane repetitive tasks every single day then you probably don't want developers that enjoy challenge, because they will leave very quickly.
You take this stance of "I have the elixir of life and you will bend over backwards to get it because you are desperate". So the only people that do end up bending over are the ones who are really desperate.
Wait till you're on the employing side, like, even, your boss asks you to look over /100+ resumes/ that are 95% irrelevant.
Signed,
A person that has viewed 1000s of resumes a week from time to time.
-He expects he won't hire me in the first five minutes? If in the first five minutes I get that vibe I no longer wish to have the job.
-Tailor-made resume for his job? As if people are supposed to create new resumes for every job that they apply for? Get serious. Plus different companies expect different style of resumes since there is no standard and what amounts to close to standard changes every couple of years. What he wants is people to magically read his mind to craft a resume just for him to meet his expectations.
- He won't hire if I can't say why I love my current job? If I love my current job then there's not much reason to leave it, now is there? Plus, he claims to have a BS detector but he seems to be asking for BS from the applicant.
- No career plans or vision? For most people laying out five year plans is BS, which means he won't hire you. What good does such a question do for anyone anyway? Looking back over my career I've only had one job that I actually planned for. The rest are from changes in things I can't control with changes in what interests me.
- I agree with the no skills part. As someone who's been on the hiring side of the table there's nothing more annoying when someone can't back up what's on their resume.
- "Don’t sit there and tell me what you would do in the future. I didn’t ask what you would do, I asked what you did." Um, yes you did, it was two bullet points ago.
- He apparently requires the perfect candidate. I wonder how many people he actually manages to hire and how many of them stay for their "career"?
- He talks of bad advice out there discussing the topic of his post and he seems to assume his will not get lumped into that list. I would say it's the same as any other post on the topic, some good and some bad.
He sounds a lot like the kind of guy that has a high turnover rate of first-year hires who leave for more money and he can't figure out why.
Not to worry. I will only work for someone who can manage to conquer problems of scale such as skimming a resume and finding pertinent points. If you are unable or unwilling to do so, we'll eventually have a problem and I'll be better off elsewhere.
If you can't narrow down resumes and phone interviews to candidates with better than a 1% chance of being accepted, then your interviewing pre-screening process is flawed. What other processes in our everyday work will also be flawed?
You send me a stupidly long resume
90% of all written correspondence (from customers, users, collaborators, vendors, etc.) is too long. Do you think they're all stupid, too?
You have annoyed me.
You're a manager. Your job is to properly deal with issues that would annoy others. Why would anyone want to work for someone so easily annoyed?
...do I really want to look forward to your rambling emails every day?
Do I really want to look forward to your sour attitude every day?
You can’t tell me why you like your current job
If I liked my current job, I wouldn't be here.
I don’t hire awesome people who don’t have the right skill mix.
Here's a clue: technologies change. By definition, anyone with the "right skill mix" won't have the "right skill mix" for long. Amesome people adapt. But how would you even know that if you don't hire them?
No career plans or vision
I've been programming for 33 years and still have no idea what I want to do when I grow up. This is an interview for an open job, not Dr. Phil.
If you don’t think well on your feet, spend some time reading through and practicing situational interview questions.
Are you serious? I'm a programmer, not an Americas Got Talent contestant. What you see is what you get.
If you are missing even one, I’m probably going to pass you up for someone who doesn’t.
Wait a minute. You want to hire perfect people, but you also want them to have "career plans or vision"?
I have a super BS detector
Obviously not, since so many of your questions can only be answered with BS.
The End
That's just about the only thing you've said that I agree with.
You sound like you have a serious attitude problem. I can't imagine working for someone like you. But thanks for writing this. You've solved many problems in advance. I won't be applying. And I don't imagine many people like me will be either.
This sums it up for me. The author sounds like a grumpy person who would be terrible to work for. I also suspect many of these rejections are self-fulfilling prophecies. When you're actively looking for a reason to reject candidates, you're probably going to find one.
> Do you have hiring war stories (interviewer or interviewee)? Share them in the comments!
looking for an employee is a WAR for this guy?!!
Here's a clue: technologies change. By definition, anyone with the "right skill mix" won't have the "right skill mix" for long. Amesome people adapt. But how would you even know that if you don't hire them?
gets to the heart why they cant. 10Xers are not a technology they are personality and a attitude. Hell some of them are not ever that great at some of the technologies they use, but they know how to use the parts they need to get them to the finish line. They know the principles of elegance in clean code, and simple systems that are only as complex as they need to be.
These people are not showing up to the door of people that interview like the author, and if they do they are not taking the position and probably recommending to other 10Xers to go ahead and avoid the interview.
I get the feeling from reading the article, that the author has not learned how to spot technical talent and is growing frustrated with it.
Interviews are a two way street. If I am applying for a job, my role during the interview is to convince you why I am a worthwhile hire, your role during the interview is to convince me that you are a worthwhile employer. If he was one of my clients I would disassociate myself from him very quickly.
As for his 5 points, I wonder if he realises that all 5 inversely apply to him just as much as they do to the candidate being interviewed.
1.Show me you can get things done. This means you can set realistic deadlines for projects and meet them consistently. You must be a good motivator.
2.Show me you are intelligent. I will ask you questions to discern how in touch you are with todays market. I don't care if you've interviewed a dozen people for this job, I want to know if you've actually read my resume.
3.Show me how I fit into your vision. Truthfully, we’ll work best together if you sincerely think I am the best person for this job in the long run. I want to know how you can help me succeed in my career, Tell me.
4.Be highly skilled. If your job advert says that you need a highly skilled Developer then don't have me sitting in a corner refactoring shitty code for the first 6 months.
5.Be Passionate. If I feel like the interview process is boring you, I will end the interview prematurely but politely.
/rant
I think the article would have been more constructive it was titled "Why I Will Hire You."
Then we get to his example of a "good" answer for career plans: yet another instance of "In this many years, I see myself that many steps up the corporate ladder. … communication … leadership … responsibility …"
Also this: "Let me know your passionate or don’t waste my time." (you're!)
This is why I love being a contractor / consultant. Clients don't ask for a little lap dance and a smile before we can do business, like this guy seems to expect.
They have a job to do that they think I can do, I give a quote, they say yes or no (usually yes, if we went this far). I do it, they pay me.
No resume-this, resume-that, what's your vision, are you passionate, what do you love or hate. I hate being in an office with a stranger in the middle of the afternoon, talking about my passions.
90% of all written correspondence (from customers, users, collaborators, vendors, etc.) is too long. Do you think they're all stupid, too? "
I agree with most of your post, but after doing a lot of interviews as the hiring manager, I have to agree that resumes should be short. I won't exclude a candidate just for sending a resume that is long, but as a general rule, don't expect me to go past page 2, especially for an entry-to-mid level position.
A programmer!
Yes, I've reached the end of my career. I'm where I want to be, and I don't want to change. I don't want to be a manager, team leader, or otherwise do anything other than programming. If there were any change I wanted, it would be 'do fewer non-programming things'.
An excellent example of the latter is the presence of spelling errors that could have been fixed with spell-check, completely random font changes due to copy-and-paste, etc. These typically are just the superficial signs that no thought was put into the content.
It's like showing up for an interview in a dirty t-shirt and sneakers. I'm not looking for excellent fashion sense; I'm looking for a basic awareness of the world around them.
So in his own special way that guy is telling the 1% to f*ck off. Well played.
I severely disagree with the attitude conveyed. People would do well to remember that a work arrangement is mutually beneficial, always. You take a job because it is in your interest to do so. You are offered a job because it is in their interest to do so. No one employs someone while taking a loss on them, yet companies treat interviewees as if they would be lucky to land such a wonderful job.
If this attitude came out in my interview, I'd immediately walk out. If you're treating me in this way before I even work for you, odds are it's not ever going to get better, only worse.
You might not like the tone of the author's writing, but having sat on the other side of the interview table, it is thoroughly depressing when a candidate tells you "Yeah, I just want a job - money, isn't it?", when you know that the role available is great, and someone who wants to care about will really enjoy it.
Don't get me wrong; we all have to pay the rent. There there are indisputably times when, guess what, one just needs a damned job that'll pay the bills.
But for a lot of smaller companies with cool little projects? Yeah, I think it's totally reasonable for them to discriminate on that level.
Be Passionate. If you are bored working in a similar job somewhere else, you’ll be bored with me.
Does the job involve rockets or something like that? No?
Well good luck finding exactly someone who is both highly skilled AND not bored by your job.
That you thought it appropriate to write a blog post with simply the title of "Why I won't hire you," is the reason "Why I will never interview with you." (And, for many others as well, I'm sure.) It has little to do with the content (although in fact, the content only gets worse with conceit and self-inflating statements) and everything to do with your attitude.
Who wants to work for someone who already thinks they're better than the majority of humanity? I'd want to work for a manager who knows how to communicate effectively without being abrasive, and who has excellent skills in resolving conflict and helping their team grow to their maximum potential. Everything about your blog post suggest the opposite combined with such a level of hubris, that I could only imagine working for you would be the worst job I've ever had.
Good luck with that hiring thing.
The best developers I've ever worked with tend to lack career plans. If you're sufficiently happy with your life that you don't need a change strategy, that's pretty cool.
That's the thing these interviews fail to take into account. They assume that everyone wants more, when that's not always the case. Happiness means knowing when you have what you want, and enjoying it.
The situation is very different however. In my experience, top talent either a) have their own company or b) are well-looked after by their current employer (at least one would hope so) so they need to actively lured away; how about you tell me why I SHOULD work for you rather than give all the reasons why I can't?
Oh yes - and the author is an arrogant dick.