jsync | Java Staffing Specialist

  • home
  • about us
  • why jsync?
  • hot jobs
  • resources
  • contact us
the watercooler

sign up for our monthly newsletter here:





jsync » watercooler » "What Every Manager DOESN'T Want"

"What Every Manager DOESN'T Want"

05/11/2008

by Dave Fecak

In preparing candidates for interviews and talking to Java professionals that are thinking about a move, we often discuss what hiring managers want both in interviews and in employees. For this month’s article, I decided to take that conversation and explore it from another angle. Here is a list of things that managers do not want, from the time you are applying for the job until the time you are gainfully employed.

...before you’re hired

  • 10 page resumes – Not only is a 10 page resume a complete waste of time in writing, it will actually HURT your chances of getting the job. Trust me on this one. Recently, one of our clients mandated that they would not consider any resumes longer than three pages. Their theory is simple – if you can not describe on paper what you have done in your career in an efficient manner, you are not going to be an efficient communicator (perhaps not an efficient coder either). Trim it down to the minimum amount to get the interview so you still have something to talk about when you get there.
  • Aloof interviews – Hiring managers want to hire candidates with two main qualities: the ability to do the task at hand, and an interest in performing that task. The technical interview is designed to take care of the ability part, and everything else that happens during your interview are indicators of your interest. Show zero energy and ask zero (good) questions in interviews, and receive no offers. In a metaphor I’ve used before, think of the interview as an exercise similar to ‘speed dating’. Be careful on how long you play ‘hard to get’.
  • Employer/co-worker bashing – Save your complaints about the guy in the cube next to you for the dinner table. Interviewers are aware you aren’t 100% thrilled with your current employment situation simply by the fact that you are there in the interview.
  • Overzealous follow-up – If you have ever walked out of an interview and sent an email from your iPhone to the manager saying ‘Thanks for the interview, did I get the job?’, you might be a redneck bit overzealous. Give them time to digest the interview and gather their thoughts. Most of our clients will give feedback on an interview within two business days, and asking for their decision before that time has passed may be a sign of desperation.
after you’re hired…
  • Forgetting why you’re there – The technology business is a bit tricky, since the work of programmers isn’t always transparent to the business users and vice versa. Managers tend to want employees who show interest in learning how the business actually works, so to better be able to create systems for your users.
  • Unwillingness to code – At a certain level in your career, you probably expect that you will not be coding at all. That is a fairly reasonable expectation, but these days I tend to see Java pros that tend to think their days of coding will be over long before they probably should be. I think many of you would be surprised to find out how many companies will not consider candidates that are not willing to code at least 50% of the time. Being willing to roll your sleeves up if necessary is something that managers will find very attractive. Even though you may be much more valuable as an architect or technical leader, showing that you are not ‘above’ coding shows solidarity with your team and is the sign of a true team player.
  • “I don’t gather reqs!” – No matter what your title or role, in this business you need to be able and willing to talk to the business and get a requirement. Being unwilling or unable to take a req will limit your potential to get hired and/or advance in your career.
  • VP/Chief/Director/Architect… – If your job title is more important to you than what your role is in the company, take a long look in the mirror. In some companies the CTO will be writing code, and in some companies a Technical Lead will not. Smaller shops may even let you create your own title! (DISCLAIMER: This article was written by the ‘Director of Talent’ here at jsync!!)
  • “I want to hold your hand” – The ability to work independently and show initiative in your work goes a long way towards career success. Begging managers and co-workers incessantly for their input and feedback on a proposed solution will get you a reputation as someone who needs lots of support. At the senior level, the expectation is that you know your job.

Newer >

< Older

archives

06/11/08: "Four Years of Columns, Condensed"

05/11/08: "What Every Manager DOESN'T Want"

05/10/08: Tech Tips from May 2008 Newsletter

04/09/08: "Bookmarks of the Java Pros"

04/09/08: Tech Tips from April 2008 Newsletter

03/12/08: "Suggestions to Make Your Java Career Recession-Proof"

03/12/08: Tech Tips from March 2008 mailer

02/06/08: JSync Client Survey Results

01/09/08: "New Year's Resolutions for Java Pros"

01/09/08: Tech Tips from January 2008 Mailer

Watercooler Archives >


Take our $ and run!
  • home
  • about us
  • why jsync?
  • hot jobs
  • resources
  • contact us

© 2008 JSync, Inc. All Rights Reserved.