digg

Facebook Connect Join Digg About

Top 7 questions to ask in an Interview

artima.com — The questions you forget to ask when you are interviewing for a job, but wish you'd asked after taking the job. - by Bruce Eckel (Author of 'Thinking in Java').

Who dugg this? Made popular Oct 7, 2006

Digg DudeWhat is Digg?

Digg is a place for people to discover and share content from anywhere on the web. Digg surfaces the best stuff as submitted and voted on by the community. Take the Tour to learn more.

62 Comments

show profanity settings
expand all
  • mshade, on 10/12/2007, -4/+63Ask the questions outlined in this article, and you won't be getting a job offer.
  • JavertHolmes, on 10/12/2007, -2/+46Here are the questions to ask for those of you who aspire to a higher calling in life and hope to make $100k+ a year.

    1. Is there an internal competition within the company where the people who stay the longest are seen as working the hardest, despite actual work output?
    2. Is the ass-kissing hierarchy currently full at the moment or will there be new openings for me to join?
    3. Can you send me a list of whose jokes need to be laughed at the most often?
    4. With which people higher up in the hierarchy can I be seen slacking off with, yet not get penalized for slacking off?
    5. What are the cool local places to eat at during lunch?
    6. I know there's no dress code, but what's the dress code?
    7. Which hot women am I not allowed to interact with since they're already "taken" by someone who can fire me?
  • HebrewHammer, on 10/12/2007, -3/+43Please note:
    The blogger is an accomplished author, written several programming books. When was the last time he held a job?

    Change title of story to read, "Some questions to ask during the interview if you do not want an offer."
  • macewan, on 10/12/2007, -2/+27What is the average length of time others have kept the job I'll applying.
  • shakin, on 10/12/2007, -16/+41Those are all terrible questions.

    1. Any company large enough to have a "management chain" that you don't see every day is also large enough to have official procedures. If you're buying an expensive tool then you would go through your company's requisitions agent.

    2. If you're in the building for an interview you should have a pretty good idea what the noise in the building is like.

    3. Meetings are completely project-dependent. Don't make yourself look like an ass who doesn't like talking to other people.

    4. What is the interviewer wearing? And why are you so concerned? If you like wearing shorts, t-shirt and sandles to work then you should consider appearing on What Not To Wear. I hate geeks who can't dress properly,

    5. This is a fair question, but it makes you sound eager to avoid coming in to work. Bring it up gently.

    6. Great, another one that makes you sound like you dislike people and are not a team player. Nobody wants to hire some jerk programmer in sandles who likes to work 4:00 pm - 12:00 am. If you're a good programmer then you'll want to work with other people, such as the end users of your program, who can help you with design decisions. If you're the type of programmer who likes to work in a shell then you should have lost your job after the .com bust and not got another one.

    7. Now you're sounding like you're making excuses for failing before you've even landed the job. You're better off asking if you'll be able to manage a few projects, that way you'll actually be responsible for its success or failure. From the sounds of these questions this guy isn't too interested in taking responsibility.
  • berwiki, on 10/12/2007, -4/+27 1. If I want to buy something like a book or a tool, how does the process work (how hard is it?). What's the cost limit before the approval must go up the management chain?
    2. What's the noise level like during the day?
    3. How many meetings am I expected to attend, and how long do they
    usually last?
    4. Is there a dress code?
    5. Can I work from home sometimes?
    6. Does it matter when I work, as long as I come to meetings?
    7. How many projects have succeeded/failed in the last five years? To what
    do you attribute the failures?
  • Chompy, on 10/12/2007, -3/+23"4. What is the interviewer wearing? And why are you so concerned? If you like wearing shorts, t-shirt and sandles to work then you should consider appearing on What Not To Wear. I hate geeks who can't dress properly,"

    To hell with that; that's exactly the dress code we have in place where I work, and I love it. If a shop that doesn't have clients coming through the office insists on that kind of nonsense, that's the first sign that something is wrong. Comfortable people work better; shirts and ties are for the shops still run by clueless middle managers who are focusing on the wrong things instead of what matters: getting the work done.

    What you're wearing at work is absolutely meaningless, so why be uncomfortable? And if you're judging someone based on what they wear, that makes you an idiot.
  • nazsco, on 10/12/2007, -2/+23> I concur.

    hey, can you see that little thumbs up icon over there?
  • The5thHorseman, on 10/12/2007, -2/+21Agreed - a few of these questions during an interview would likely have you tossed out of consideration. Now, post-offer, yes, it would be appropriate to clarify some such things.
  • schwack, on 10/12/2007, -0/+11Buried as lame. Self-centered questions are NOT the questions you ask for ANY job.

    If you're going to be that into yourself in an interview with a prospective employer, why not ask these questions?

    "How many breaks do I get in a day and for how long?". "How much exactly are you going to pay me?" "My healthcare starts immediately.. right?" "You guys don't have a proxy server do you?"

    You get the idea. If you're asking questions about you in an interview, and not about the company you are applying for or the position. The only question you should ask is "if based on this interview, am I still a candidate in the selection process?". The answer will sometimes surprise you.

    What is really ridiculous is false information making the front page of Digg.
  • WorldGroove, on 10/12/2007, -1/+118. How difficult is it to implement new technology or ideas; in terms of the approval process?
    -----
    *WorldGroove: "Hey boss, I wrote this WebApp that connects to the different SAP systems we have using SAPjCO to gather data in a database and use it to run batch-maintaince during the night. I know we normally license Oracle, so I installed open source Thunderbird on Ubuntu and I'm using apache to manage the system and some python to help parse through the data and decide what needs to be done and when."

    *Boss:"Uh, yeah... well we only use Windows Servers with IIS and Oracle. We have to issue a work-ticket and allocate a new server and check with our legal department about licensing."

    *WorldGroove:"But boss, everything I wrote is free and it works just fine on a modern PC running Linux. Actually a couple of the guys have already been using it for a week and so far it's been..."

    *Boss: "WHAT?! You need to get things like that approved before implementing them."

    *WorldGroove:"That would of taken months; I just wanted to try it out. Everyone in the office loves the shiny icons with AJAX interface. I think if we just get some more feedback, we could really turn this into..."

    *Boss:"As far as I know, that 'python' thing you mentioned isn't on our software-approved list. Neither is this "ThunderBird" Database you spoke of. Or that AJAX thing."

    *WorldGroove:"Well, these are well-known softwares and they're free and work very well. I just need to do some more cleaning up of the code and document everything, then.."

    *Boss:"You need to see me tomorrow morning to discuss your conduct. You can't just go off making whatever you feel like. It can take up to a year to get those softwares approved before connecting them to our systems."

    *WorldGroove:"But boss, I discussed the risks with my group and it's just doing small tasks without tampering with any critical systems. Just a few little things that cause us to be called up at night or take hours to do manually each week. It's already saving us hours a week and with alittle more work & feedback from others, it could be...."

    *Boss:"Turn that application off. We've been doing it manually years before you were hired. I don't need you telling me how to run this shop."

    *WorldGroove:"Umm... I was just trying to help. Everyone else seems very happy with it."

    *Boss:"Well, that's because they don't understand their job. Now what are they suppose to do with the free time?"

    *WorldGroove:"Perhaps work on some other projects or go for training?"

    *Boss:"No, I want them working on assignments I gave them. The assignments that your WebApp just stole from them. Turn it off."

    *WorldGroove:"Um, okay. Sorry."
  • Rikkochet, on 10/12/2007, -2/+11Agreed. Or: "Questions to ask on your second week at a new job"
  • MrL0Lz, on 10/12/2007, -1/+8These are the dumbest questions I've ever seen, buried as lame
  • nstrupp2, on 10/12/2007, -0/+7In retrospect some of these questions may have been good to ask, but I can't remember a time when I wish I would have asked "What's the noise level like during the day?"

    Some questions should definitely be answered before accepting a job. Such as "Is there a dress code?" or rather, more appropriate "What is the dress code?" It could be a real problem if you took a $20k/year job but are expected to wear a suit every day and don't already own any.
  • Crucifix, on 10/12/2007, -0/+5These questions really depend on the job and who is interviewing you... some interviewers might get the impression that you're disorganized or downright lazy if you ask a bunch of questions about how many meetings you must attend, when you must be at the office, and whether you can work from home. Not to mention that you could sound a bit anal asking about noise level (if they'll complain about the noise level, they'll complain about anything), and companies hate whiners.

    Now that's not to downplay the article at all; in fact, in my opinion, these 7 points are important aspects of enjoying a balanced home/work life. But let's face facts - there aren't *that* many companies out there that play to the employee this much. If you want to find a company that works for you, go ahead and ask these questions, but you might do well to ask the questions differently, so as not to ruin your chances at compromising a few contemporary perks for a job you would really enjoy.
  • Grassmunk, on 10/12/2007, -0/+5A MUCH better way to ask some of these questions:

    1. What is your training policy?
    2 and 4: May I have a tour of the facilities?
    5. Do you have flexible work hours?

    Do no ask 3 or 6 they will make you look lazy and make it look like
    3. How many meetings am I expected to attend, and how long do they
    usually last?
    6. Does it matter when I work, as long as I come to meetings?

    Maybe ask this if you've written a few books on Java and are getting hired as an emergency and you can make:
    7. How many projects have succeeded/failed in the last five years? To what
    do you attribute the failures?


    REAL questions to ask:
    What is your bonus structure?
    How many projects has your team complete this past year?
  • G33k0ft3chz, on 10/12/2007, -0/+5My only question I would ask, "Are you a Virgin?"
  • bugdog, on 10/12/2007, -0/+3JavertHolmes, sounds like you work in my office.

    I should have asked about the noise level and then asked what would be done if it became intolerable (which it has).

    I've asked a number of times for a better headset, only to get told that it costs too much and wouldn't get approved (not that they've even tried). My next thing will be to get a letter from my doctor (yay). I can't decide if he needs to state that the real reason I require noise cancelling headphones is because I am going to kill two of my coworkers if I don't get them, or if I should go with a lesser "gets migraines" story.
  • freff, on 10/12/2007, -0/+3Not true. There are a lot of questions that should be asked during an interview. An interviewer likes applicant that ask well thought out and researched questions. Some of these may involve you personally, and how well you fit with the position they are looking to fill. There's nothing wrong with showing some curiosity about the job and the company, but I agree that some of these are...not so good.

    "You guys don't have a proxy server do you?" Classic. I'm so stealing that....
  • blitzman, on 10/12/2007, -0/+3What you should ask, at some point after it's clear they want to hire you:

    "What is the company policy on work I do on my own time with my own equipment?"

    If it isn't to your liking, the time to negotiate that is when you negotiate your salary and other compensation.
  • Markie1006, on 10/12/2007, -2/+5@shakin

    "2. If you're in the building for an interview you should have a pretty good idea what the noise in the building is like."

    Wrong.

    Pretty much every interview I've had in the last 10 years have been held in meeting rooms, normally away from the general office hubbub. This gives you absolutely no clue to what the sound level is like in the area where you'll be working.
    You may be unlucky and end up sitting next to a Milton who insists that it is their right to be able to use their phone on speakerphone (at all times), because otherwise the phone wouldn't have that feature!
    Yes - I sit far too near to an assclown like that.
  • mithras, on 10/12/2007, -0/+2@WorldGroove: Sounds like you should submit a story to TheDailyWTF.com!
  • TheSpook, on 10/12/2007, -2/+4@shakin - Let's be honest here... Nobody likes working with end users.
  • matrixneo, on 10/12/2007, -3/+5A serious look at asking questions during Interview:
    http://www.informationweek.com/news/showArticle.jhtml;jsessionid=4CVFLMNGD2U2YQSNDBOCKICCJUMEKJVN?articleID=187200561

    Google Interview questions:( This one is already dugg, but if you haven't read it - try it)
    http://www.gamedev.net/community/forums/topic.asp?topic_id=299692
  • Mokey, on 10/12/2007, -0/+2Who's digging this stuff? This list's a surefire way to *not* get any job you're applying for.
  • G-RaZoR, on 10/12/2007, -0/+2The greatest question I have ever been asked in an interview... "Why should we NOT hire you?"

    --never saw that one coming....
  • 4NDr01D, on 10/12/2007, -0/+2it's so sad the innovation is routinely squashed by procedure and middle management.
  • HickJew, on 10/12/2007, -0/+2"Is there mandatory drug testing?"
    "No?"
    Exclaim "Great!" while jotting down on notepad.
  • Fratz, on 10/12/2007, -0/+2Questions I have asked:

    1) (if applying for a position that was vacated) What was the reason for the previous person leaving?
    2) Why do you like working here?
    3) Can I see a demo of your software?

    Questions I wish I had asked:

    4) Can I get a copy of your coding standards? (Ostensibly to practice using them, but also to make sure monkeys didn't write them.)
    5) What are the last three innovations adopted by your group?
    6) What criteria do you apply to new ideas to determine if they will work?

    At my previous company (a worldwide shipping company with a hidden arrow in their logo), the answers to #4-6 would have been:

    4: "We don't have any written down, but basically you should write your program as a single function with no subroutines."
    5: "We have non-human-readable filenames, so rather than simply make them human-readable, we created an innovative table that maps the non-human-readable names into a description. Plus, we just started using sockets for network communication instead of our proprietary home-brew implementation that we made because we couldn't understand sockets. Third, we started doing our own QA because the company's QA group doesn't understand how to test software."
    6: "We run them by Larry, and then Larry dismisses them as infeasible, then resurrects them as his own ideas six months later."

    It would have been enough to scare me away.
  • inactive, on 10/12/2007, -0/+1It seems like a lot of companies want someone with the skills of a good programmer for jobs that involve very little programming ( or interesting programming ).

    You have to use tact and know when to quit, but I think asking as many details of what you will be working on and when, while watching their faces, listening to the tone of their voice would help. Details.

    If they hesitate on details you should take that as a clue that they aren't offering what they say they are offering.

  • TechCoder, on 10/12/2007, -0/+1In regards to #4, you should just ask where you would be working. Is it an office, cubicle land or a trading floor.

    Where you work for 8+ hours a day will determine how productive you will be.
  • oogee, on 10/12/2007, -1/+2I thought of some more questions to bring the total to ten:

    8: how long will it be before I can apply for your job?

    9: Is your son actually as gay as he looks in that photo on your desk?

    10: do you smell *****?

    there! now the list is complete.
  • ChrisLowder, on 10/12/2007, -0/+1You may as well ask them to show you the door after you finishing asking those asinine questions, because you sure as hell wouldnt be getting the job...
  • serra, on 10/12/2007, -3/+4I love it, those are so true!
  • freff, on 10/12/2007, -0/+1Wow. Most of these are questions for after you've been offered the job, or thereabouts. A couple of these are straight up disasters for an interview though. Imagine giving someone a job interview, and that person actually asked you during the interview, "How many meetings am I expected to attend, and how long do they usually last?" Talk about giving the wrong impression to the interviewer. Personally, I would forward that person's resume to the waste basket as soon as the door closed behind them.

    Perhaps a better way to that question would be to ask, "How much time would I be expected to devote to meeting with management/team members? Would I be expected to meet on weekends/after work hours? Do employees ever feel that meetings sometimes interfere with productivity?"

    Numbers 5 and 7 are keepers though.
  • Mambo, on 10/12/2007, -0/+1I think the question about meetings is a valid one. I am only out of highschool, but I interned at a business where many of the people doing the actual work, ended up wasting weeks at a time in pointless meetings. They didn't need to be there, they had nothing to give to the metting, but yet they were required to attend.
  • inactive, on 10/12/2007, -0/+1Wow. That seems like some things that happen in my company!
  • SniperSlap, on 10/12/2007, -0/+1I don't see myself asking these questions ever. These are more "details to glean once you have established yourself in the company".
  • inactive, on 10/12/2007, -0/+1More importantly, why did they leave?

    If they left screaming at the stupidities in their daily life, this is not good.
    If they left because they got headhunted for triple the salary as a result of the profile of the job, sign me up.

    Much of the time its less about what the job is immediately, more about where it is leading to.
  • ptrcd003, on 10/12/2007, -1/+2Wow..and right after I saw office space. Does he have his radio on at a reasonable volume between 9 and 11?
  • grumpyrain, on 10/12/2007, -0/+1Do we ask this before or after "How long do you have to work before we qualify for sick leave?".

  • Johnbinarystar, on 10/12/2007, -0/+1Two questions I wish I would have asked in my present job:

    Describe process and outcome for filling the last three vacancies in positions the next step up from the one being interviewed for. (If they don't give a good account of an open and fair competitive interview/selection process, look elsewhere).

    Describe the organizations budget, and the levels of management budget responsibility. (You may not believe it but in the 900+ person place where I now work, there are 10's of managers, but only 2 managers have access and control of the budget.

    Never take it for granted that any potential employment place is run by adults in a fair and practical manner.
  • yahoofrom, on 10/12/2007, -0/+1Brilliant
  • leperkuhn, on 10/12/2007, -1/+2I gotta ask, are you in high school? If you don't care about your own work conditions, you're an idiot. Of course you should be asking questions about how things will be for you, and if you aren't, you will never get any respect, because it's obvious you're just a nobody that's desperate for a job doing ANYTHING.
  • jayc, on 10/12/2007, -0/+1Sounds like just a rephrase of "tell me about your greatest weakness" which is equally as pointness. Here's how it goes:

    Interviewer: So, Bob, tell me what your greatest weakness is.
    Bob: Well, I just get so gosh darn involved in my work that I end up working way more than I shoud, I really need to work on that! *cue fake laugh*

    The interviewer is happy and nothing about the interviewee has actually been learned in the process. Behavioral interviews are pointless and many times demeaning.
  • chadpyle, on 10/12/2007, -0/+0What a rediculous list of questions.
  • MicrowavedH2o, on 10/12/2007, -1/+1They seem decent at first, but definitely the _top 7_ to ask....

    just some stuff to consider, and as other comments have pointed out, some of them are stupid.
  • rightclick, on 10/12/2007, -0/+0Where's the best place to sneak a quick smoke? I am too lazy to walk to the stairway.
  • payrolldude, on 10/12/2007, -0/+0Funny, I just interviewed a prospective employee. She asked me if our dress code required High-Heels, as her present job does. (and she does not like it!) I replied: "No, but we do have a height requirement..." She did laugh. I offered her the job.
  • dtt1167, on 10/12/2007, -2/+2going a lil Pirates of Silicon Valley eh?
  • Fetching more discussions...
    Show 51 - 62 of 62 discussions

  • Add a Comment

    Login or register to comment!
    Or, sign-in super fast with your Facebook account ...


© Digg Inc. 2009 — Content created and posted by Digg users is dedicated to the public domain | Terms of Use Updated | Privacy Policy
DIGG, DIGG IT, DUGG, DIGG THIS, Digg graphics, logos, designs, page headers, button icons, scripts, and other service names are the trademarks of Digg Inc.