Slashdot Mirror
What Questions Should a Prospective Employee Ask?
Mortimer.CA writes "Even though things aren't great in the economy, it's prudent to plan ahead to when things (hopefully) pick up. In light of that, I'd like to update a previously asked question in case things have changed over the last four years: What do you ask every new (prospective) employer? When you're sitting in the interview room after they've finished grilling you, there's usually an opportunity to reciprocate. There will be some niche questions for specializations (sys admin, programming, PM, QA, etc.), but there are some generic ones that come to mind, such as: what is the (official) dress code?"
Similarly, what questions should you avoid? Read on for the rest of Mortimer.CA's thoughts.
He continues with these suggestions:
"What about my resume caught your eye? What hardware/software am I expected to use at my desktop (e-mail, OS, editor, source control, etc.)? Are there team lunches or get-togethers? What are your goals for the next six months, one year, three years? What ticket/issue tracking system do you use? Do you have separate build/stage/QA/etc. environments? How do you keep track of documentation? What are your full names (so I can Google them)? What are the typical hours of the team members? Those are some of the ones I've thought of after some digging around. Are there the generic ones that you ask? What are some question for various niches? (e.g., for sysadmins: what config mgmt software do you use?)"
"What about my resume caught your eye? What hardware/software am I expected to use at my desktop (e-mail, OS, editor, source control, etc.)? Are there team lunches or get-togethers? What are your goals for the next six months, one year, three years? What ticket/issue tracking system do you use? Do you have separate build/stage/QA/etc. environments? How do you keep track of documentation? What are your full names (so I can Google them)? What are the typical hours of the team members? Those are some of the ones I've thought of after some digging around. Are there the generic ones that you ask? What are some question for various niches? (e.g., for sysadmins: what config mgmt software do you use?)"
n/t
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Do you have manditory drug testing?
"I've worked in England and the policy on assault is pretty strict there. If you hit somone, immediate dismissal. What's your policy here? [cracks knuckles]"
Legendary question in by a candidate for a job in Sweden.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
Where do we eat?
If you want to know how much overtime you're going to work, and how family-friendly a workplace is, find out what the demographics of the company are. If you are single, you may find that an overly family-oriented workplace is going to put extra pressure on you to stay late due to parents needing to take time off to be with their family (doctor visits, holidays, etc). On the other hand, if you have a family, a family-friendly workplace may afford you more time to spend with your family.
Another good question is to ask your interviewer how many times a week he talks to customers. It will give you a good idea of how insulated you will be from customers, and that can give you an idea of whether you want the job or not. A non-customer centric position will probably be slower in promotion, but much lower pressure. A customer centric position will be higher pressure, but the opportunity for professional growth (even if all you want to be is a developer) is enormous.
Like bandwidth caps 'n stuff?
There are only two occasions when asking about average employee working hours is appropriate:
1) When you will be contracting with the company and will be charging them an hourly rate with the possibility of overtime
2) You don't really care about getting the job
If you ask in the first situation, you are simply being professional. You want to be able to accurately estimate the amount you will be charging them. It just makes sense, especially since it will end up costing them more to keep you later.
If you ask in the second situation, you are simply lazy and unwilling to be a "team player".
I often ask what are the actual (real) work hours. In my experience, a contract with an IT company at a programming job, states a basic outline of the work hours that are demanded of you (09:00-18:00, for example). Most of the time these work hours are just formal and not actual, since these types of jobs are very demanding (the needs of meeting goals and dead-lines). The kinds of hours that you'll be working may differ from the ones stated in contract. This information is quite important if you have some kind of routine - if you study part time, for example.
It is the universe that makes fun of us all.
I got a new job about 10 months ago.. during the interview, I asked about their benefits, and was told they were "pretty standard". Now, I learn how dishonest they were... health insurance is $850/month for family plan, and we only get 4 vacation days off a year (and only 5 paid holidays). No certification reimbursement, and they want to be able to call me on my personal cell phone after-hours. Lesson learned: get DETAILS.
Just how [in]competent is the management here?
Asking follow-up questions tied to the things the interviewer just spoke on (job responsibilities, organizational policies, challenges, etc.) will win you huge points because it shows you were listening, and you are interested in their organization. Asking questions about benefits, promotions, dress code, and other ephemera will signal to the interviewer that you may only be interested in drawing a paycheck, not being part of a group solving problems and working together. If you want generic questions to ask all employers, consider questions like "Who are your competitors?" or "What specifically in my CV/resume interested you?" The goal of the interview is to get the offer, and the best way to get the offer is to demonstrate an interest in the organization you are interviewing with, an understanding of the industry they are in, and at some level the challenges they face in the current market. As for the dress code question, you dress for your first day just like you dressed for your interview, unless told otherwise, and on the first day your new boss/HR/co-worker will tell you how to dress for the second day. Asking about dress code during the interview will send up a red flag that you may be someone that will challenge the dress code at some point down the line, that would be a strike against you.
Ken
The best questions are almost certainly those that are specific to the employer and the job which they might hire you for. These are excellent because they show that you've taken an actual interest in what they are doing and may have something to contribute to the overall team in the first 6 months or so. Which isn't to say that the other questions (e.g., generic "what are employment conditions like on the ground" checks) aren't good, but if the boss-to-be thinks you care, it's a big way to stand out for the better.
Or at least that technique has consistently worked for me so far, and people who ask such things do stand out when you're on the interview panel. Too many people just do generic applications for jobs and don't seem to care what they actually end up doing...
"Little does he know, but there is no 'I' in 'Idiot'!"
So that i don't dirty my lips when i kiss them!
I now have to ask, "Does the company have sufficient funds to meet payroll for the next year?"
No, that makes it sound like you already don't like the job you haven't even been offered yet. Instead, ask about career paths, ask where your co-workers came from (internal new-hires, transfers/promotions, etc.), and where former group members are now. Asking how often people get promoted makes you sound like a civil servant "wannabe", probably not your best interview tactic.
Ken
'Can I see an example of your code or documentation?'
If they don't keep documentation or their code tends to be messy and undocumented then you're going to spend half your time trying to figure stuff out rather than doing productive (and thus interesting) work. If a company's business is in a complex field (finance for instance) and the code/system has built up over many years there is a fair chance that both will be pretty incomprehensible to start with and if they haven't got reasonably documentation the your job is going to be harder and there is a chance that you'll never feel you full have a grasp on *everything* that is going on.
Apart from that, it will show that you give a damn about documentation and are organised.
One that I've always fallen back on when "do you have any questions for us?" time comes up is something along the lines of "Can you describe a typical day in the life of someone doing my job?". If they're honest, it generally gives me a feel for a typical day, how much time is spent in meetings, doing documentation, when people come in/leave, etc. I then lead them through things like "how much time do I spend doing change tickets/incident tickets? How much time is spent dealing with email/phone calls/walkups? How much time is spent on call?"
While these questions won't generally alter opinion of the job, it does tell me much more about the "how" as opposed to the general interview "what" and "why". Ultimately the quality of life part of the job is more important than the work, at least, as I grow older and move to more senior (ie: non-helpdesk/NOC) positions. Not hating being at work, being fufilled, challenged and treated with respect is more important at this point than simply advancing or resume building. To find out about the "quality of life" is generally the bent of my questions.
Good searching!
We emerge from our mother's womb an unformatted diskette; our culture formats us. - Douglas Coupland
Assuming I get through the first round or two, my questions are like these:
What is your culture like?
What do you like about working for (insert company name)?
(If it is a division of a large company) How heavy is the hand of Corporate on your day to day?
What keeps you up at night?
Usually by this point I am as much looking to be sold by the company. I am a product manager and usually seek similar roles. Things like culture, openness, empowerment, etc are usually covered in earlier interviews.
I should also add that I usually spend a fair amount of time researching a company before I even interview. Research their annual reports, investor page, read the SEC filings, look for analyst comments (on public companies), understand their market space, competition, etc. So usually much of this has come across already.
Oh yeah, one more: Do you use SAP? (god, how I have that frickin' program)
Geoff
Suppose you were an idiot and suppose you were a member of Congress
If asked like: "What is your education and training policy for employees?" and "Will additional education be reflected in job position, if my job performance is satisfying, or is promotion generally based on seniority?"
or something like that. And a critical one for me: "What is you policy on flexible hours" (or whatever you call in in the US - is it OK I get to work later (or earlier) and then leave later (or earlier)).
What hardware/software am I expected to use at my desktop (e-mail, OS, editor, source control, etc.)?
This (certainly the email and source-control bits) is an excellent question to ask -- not so much because of what the answer as such, but because of your interviewers' reaction to giving the answer. If the interviewers frown or are apologetic about the answers, then that's a big clue that the IT department is run for its own convenience rather than the users' convenience.
For instance, if the email system in use is Outlook, ask if they have IMAP or SIMAP turned on, to enable non-Exchange clients. If the answer is no, then you know that uniformity gets enforced over convenience. You also know that nobody in the company uses any external mailing lists (such as the GCC or Linux kernel lists), as there's no way of posting to those from Exchange without looking like a fool.
If your interviewers sound cross or apologetic when describing the source-control system -- in other words, if the source-control system was dictated by IT without engineering buy-in -- then decline the job. Even if it were theoretically possible to do work in such a company, the excess overhead due to dealing with bureaucracy would make it an inefficient use of your time.
The absolute best answer you could get here is the one a VP of engineering whom I once worked for gave to a compiler vendor whose products we didn't want. "Can't you enforce tooling?", they asked him. "No," he said, "we don't tell Babe Ruth how to hold his bat."
Peter
1. Health plan - even here in Canada, I consider this important. Even routine dental and prescriptions (not to mentioned uncovered specialists like chiropractors and podiatrists) can cost a fantastic amount of money. Everywhere I've worked for recently had copies of the policy documentation available for interviewees.
2. Overtime policy - This generally doesn't vary much due to have a legislated minimum here (1.5x pay past 8 hours a day (or 12 if that's your schedule) or 40 hours per week), but it's always good to know.
upon the advice of my lawyer, i have no sig at this time
Ask your interviewers how long they've been with the company, and why do they stay? The second one is more important if you're in a current "hot" field where people jump ship quite a bit. It tends to give a little more insight into the corporate culture and those you'll be working with, in my experiences.
... then ask them to call it, heads or tails?
Run and catch, run and catch, the lamb is caught in the blackberry patch.
You want your question to demonstrate your ability to do the job as well as allow you to assess your future bosses and coworkers. So technical questions like "What version control system do you use?" or "What kind of backup system would I be expected to maintain?" are good for talking to technically-oriented managers. For non-technical managers, some good questions might be "How does my work get tested before getting sent out to the users?" and "How are project schedules determined, and what approaches are typically used to keep projects on schedule?".
I am officially gone from
I'd like to show you how I would handle/think about the kinds of problems your team has to solve. Would you tell an issue you faced recently that would have been *my* problem if I'd already been working here? I'll talk out the way I'd try and fix it.
If you're smart, you will have done some research into the company before going to the interview so that you already know what kinds of things they do and the problems they face.
Come play free flash games on Kongregate!
I recently returned to school to complete my degree and was able to hear a very intresting presentation from one of the instructors last year. Being that I have applied for many jobs in the past year (and currently working full-time while going to school in the evening), a lot of these made sense. Here are some of the points I found most interesting to take into account during an interview.
- There are only two things that the employer wants to know during the interview: "Can you do the job?" and "Are you going to cause trouble?". The information on your resume will answer the first. Your answers and attitude during the interview will answer the second.
- During the interview, focus on proving you are able to do the job and that you will not cause trouble. Trouble would be absenteeism, incompatibility with co-workers, etc. Keep your personal life personal and your special interests and hobbies to yourself unless they directly pertain to the job. If you interests require you to take time off from work, that should come up during the negotiation period and not during the interview. Also, do not bring up money, pay, vacation, training, "team lunches or get-togethers", hours, or other trivial items. This should all be addressed after the job offer has been extended, while you negotiate, and before you start.
- Once the employer has gone through the process of interviewing all of the candidates and decided that you are the best candidate, you should have already prepared a list of priorities for what you want. If you need six weeks of paid vacation per year, if you need to make a certain salary, or if you need to work a certain schedule, that is all negotiable at this point before the job is accepted. For all of the effort they have put into posting a job opening, sorting through all of the applications, spending all that time interviewing, and somehow still decided that you are the best candidate, it is not in the employer's best interest to start the whole process over because you want six weeks of vacation time instead of the normal four. Everything is negotiable.
- If you are asked during the interview how much you are expecting to make at the new position, a correct answer is "I earn $XXXX at my current job and I am certain you will be fair, but I would like to lean more about the company". It does not ignore the question, but it does not put either party in a tight spot or make either party feel guilty. Again, pay is part of negotiation and not part of the interview.
- One item that should be addressed during the interview is asking about company culture: military (directives from management), team (groups work together to solve problems), competitive (individuals work "against" each other), artistic (try to create the best product), etc.
- Another item that should be asked is what the interviewer sees in the job. Each interview may give a different answer from HR, the department head, the department manager, and the team leader. Taking each of those into account will give a better impression of what is expected.
- I suspect that developers and other specialized positions would want to know what type of systems would be used and the development tools required. This, however, should already be answered to the employer by what is listed on the resume. If the tools required are not listed there and the candidate was still being considered, the tools must not matter very much to the employer and they may be willing to offer training on that system. I am not sure asking about what type of hardware, email, ticket tracking, system environment (Dev/QA/UAT/Prod), or documentation system would be used, since those are basically universal and two companies with the same system may use them in different ways and a new hire will need to become oriented with how the company wants to handle details. Also, if questions about dress code, hours worked, overtime availability, weekend catch-up time, or anything else not normally covered in an interview are important to you, s
"Mostly harmless."
Yeah euphemistic questions FTW.
I like: "What's the staff turnover rate like? How about in the dept I'd be joining?"
If the staff turnover is high, it's often not a good sign. Poor management or hiring practices, and often you'd be picking up the pieces. This doesn't necessarily mean you shouldn't join them, but if the turnover is high, the package better be better - haggle if necessary - esp if they know that now you know their environment "isn't better than industry average" based on the employee turnover rate.
In fact, the Bank Regulator in my country considers high staff turnover a significant negative when doing audits of banks.
The only question I can think of is,
"Are you hiring?"
www.eissq.com/BandP.html Ball and Plate System. Amuse your friends. Crush your enemies.
"Am I... am I supposed to type with my penis?"
Hunt and pecker?
I looked up this kind of stuff in Google, and the first link was to Career Builder. I copied down some of the catchall questions for an interview later that day. Granted the job turned out to be kind of tailored to my previous experience, but that experience is more jack of all trades than emphasized which they were okay with. I think it had to do in large part to the fact that I knocked that interview out of the park, and I think that is in part due to the questions I copied down.
I don't really think much of that kind of stuff, but if it works, it works.
When I talk to non-managers, I always ask them things like how do you like working here, and what don't you like about it? Most companies that I've interviewed with do tend to allow the people in the group you're interviewing with to talk to candidates and make sure they're a good fit personality-wise, so when I get a chance to talk to non-management types, I always like to get their perspective on the company, the environment, and the work, since it tends to be different from that of the managers. And when I'm on the other side of it (talking to candidates for my company), I try to give them both the good and bad aspects of the job.
About 10 years ago, I learned the hard way that the questions you ask can determine whether or not you get a job. I had received an offer at a large company, and when I learned that some amount of on-call time was going to be required, I asked whether this was a 24-7 thing, or whether there was some kind of rotating system of shifts. They rescinded the offer just because I asked the question; I was really glad they did, because I didn't want to work for a manager who would do such a thing. (I ended up taking a different job in the same company, for more money and with no on-call requirement.)
Which brings me to another point: if your questions are reasonable and a company declines to offer you the job just because of that, you probably don't want to work for them anyway.
Pull a stunt like that and you'd strike out if I was interviewing you. To each their own, but fer christ sakes it is an email client not your main development tool!
Once you start asking religious questions like the ones in your post, you start to look like a person who will be very difficult to work with. After all, if you have major demands for extremely minor things like your email client, what kinds of demands are you going to asking for when it comes to actually doing your job?
Every person I know who does job interviews says that the main thing they are looking for is whether you will fit in to the workplace. That's being a little simplistic maybe, but consider that the interviewer(s) are people too (and they're probably quite nervous as well). It's actually quite common to have an interview panel comprised of a higher level boss, the immediate manager of the position and a colleague (though maybe a senior or supervisor), and in these cases you need unanimous approval.
Some of the points I take from this are -
- whether they think you will get on with colleagues (so ask open-ended questions about potential co-workers that might leave you an opening to divulge some shared interests);
- whether they think they will be able to work with you (honesty, integrity, respect, professionalism, personable),
- what your personality can offer,
- long-term promise (ask about Continued Professional Development or whatever),
- the approach you take to your work - are you naturally someone who tries to provide value to the client? Do you "hug"? Or do you focus on being efficient? Consider say a bank - some banks the customer wants to get in and out as quickly, easily and cheaply as possible while other banks have customers that want to come in and be offered a cup of coffee before they have a lengthy discussion with their account manager that might include both their new loan, the way forward for their business and golf. The interviewer is not looking for someone who would be great at the other bank.
The trick is doing this in a way that is appropriate to the company and the profession. Be sure to read the website, their literature and figure out their market and their position in it. That not only provides you with ammo for discussion but indicates your interest in the company, that you think you're right for the company (and the company right for you!) and that you were smart enough to have thought of it.
I walked into my first interview for a "proper job" and within 30 seconds was asked what I thought about their new website, I confessed I hadn't had chance to read it and it was blatantly game over from there. The next interview I was asked something which was a clear opener for me to remark about the website, which she then asked me what I thought of and I responded that it was a little short on content, could perhaps do more to sell the company, but generally seemed appropriate and anyway in this field there is a danger of content going out of date. The interviewer actually then ticked something on her pad and scribbled a little comment, looked up and realised I'd caught her testing me and we shared a little smile which I'm pretty sure secured me the job.
Okay, I'm actually damn good at interviews. This is blowing my own trumpet, but it's true. I've beaten people vastly more qualified, more experienced and less demanding in salary because I can hold my own in an interview. In fact, I change jobs rather than mess about with the internal politics of pay-rises, even in credit crunches. It makes life more interesting.
I have *never* asked a question at the end of an interview. I've always said "No, I think you've covered everything I need to know" because, by then, they HAVE, or I've done my research already. Asking a smarty-pants question is likely to lose you respect too.
"What is the (official) dress code?"
You're looking at it. You're probably wearing it. You're talking to people who are wearing it. It's pretty irrelevant anyway, because if you're required to wear anything different (e.g. uniform, stricter dress because you're dealing with public etc.) then they will TELL you that or you will already know. And what are you going to do? Say "Oh, no... I couldn't wear that" and forgo the job? And 99.9% of places are the same anyway - smart or smart/casual unless you're public-facing.
"What about my resume caught your eye?"
A good question. For your first month of working. In the interview, it's just too long-winded to explain and they might well be reluctant to discuss details of their hiring process.
"What hardware/software am I expected to use at my desktop (e-mail, OS, editor, source control, etc.)?"
You'll have been told by the job description. You should also have been shown round the place by then, even if it's just "and this is our coding floor". Personally, I usually insist on pre-interview tours if it's at all possible but most places have done this for me automatically - why would you ever want to take a job at somewhere you've never even SEEN the inside of? I gain the most information by seeing where I'm supposed to work and walking through the building to get to it - H&S violations (Cramped working conditions, no fire extinguishers, etc.)? Spotted them. Employees slacking off/arguing? Spotted them. People wasting time in boring meetings? Spotted them. The person I'm replacing? Probably sitting at the same desk or be the one showing me around.
Plus, the people in interview might not want to get into those sort of details because it will take too long. They just want to get on through their candidates and start deciding. Also, by asking, it's like you're questioning their choice. You're being paid to do the job, you have to damn well learn whatever software they want anyway. All this question does is provoke a feeling that you won't be happy/productive if it's not your "favourite".
"Are there team lunches or get-togethers?"
AKA "I want to socialise, waste time, claim that I'm team-building". If you want a team lunch, you'll have one. If you don't then you won't. This is nothing to do with the job unless it's pushed "from above" but you can't tell people how to eat their lunch and you wouldn't want to work anywhere that did. It's probably the "best" of your questions, though.
"What are your goals for the next six months, one year, three years?"
Brilliant question. For THEM to ask YOU. You're basically questioning their dedication / long-term plans in a roundabout way. They will raise eyebrows at this question.
"What ticket/issue tracking system do you use?"
See above about software/hardware.
"Do you have separate build/stage/QA/etc. environments?"
You will know this by the end of the interview/tour or you haven't done your research properly. It probably tells you in the job description. If they say no, you're implying that you know or work better. If they say yes, you're making yourself look an idiot by not knowing that.
"How do you keep track of documentation?"
See hardware/software question and the above. If they say "we don't", you should already know that and will come across as superior. If they say, we use
The reason most companies ask isn't to stiff you, but to make sure you aren't expecting way more then what they are budgeted for. They don't want to get to negotiations and find out that you were expecting $150k a year when they only had a budget for $90k. If the company is worth its salt, they probably also want to know that you aren't asking for $45k and the market rate is $90k--after all, what is wrong with you at those low prices?
The trick to not pigeon holing yourself is to give them a ballpark. That is all they need--you to put them at ease that they aren't gonna get sticker shock when they hire you.
Give yourself a range of like $20k or so. Make sure that you span the range so that what you really want is somewhere in the lower end of the quote. For example, if you want $90k, make it $85->$100k. Just make sure that the low end is really and truly the absolute minimum you'd accept and the upper bound isn't a huge stretch for your skills and the market rate.
They ask "what is your salary requirements?" You reply "I was hoping for market rate, so ballpark about $80k -> 100k. Obviously that number might be more or less depending on things like my position, hours, benefits. Sound about right?". Now you still have a lot of negotiating power and they don't have to worry that when they want to hire you and need to negotiate salary you aren't gonna ask for $150k.
I once interviewed for a non-profit who asked what my salary requirements were and I said "about $70->$90k" and he immediately shot back "unfortunately we are budgeted for around $55k". With that, we both knew this wasn't gonna work so we didn't bother wasting more time.
That is my strategy. Your mileage may vary.
This is good to ask during a 1-on-1 interview, or when the interviewers are nearly peers. (i.e. bad to ask when the CEO and some flunky are in the room)
"What do you like least about working here?"
It's a good judge of character of the person interviewing you. I usually deflect answers that involve "commuting" or something external and re-ask the question. The answers tend to fall into three categories. 1. Bullshit/uninformed ("nothing! I love it here!") 2. What the boss/policy wants them to say ("we care about our customers *too much*!") or 3. Honesty.
People like talking about themselves, their opinions, and their likes and dislikes and will do it for hours. It's far easier to get them to open up about what's right (or wrong) with the company when you start with their gripes. Make the question about them and make them feel informed and important. At least it gives you some leverage in follow-up questions.
---
And for the record, at my current job I answer this as "That it feels slow to get software to market. Testing and management approval can seemingly take forever, but I realize it's a deliberate effort to maintain quality." It's honest and a personal gripe of mine.
Get off my lawn.
I like: "What's the staff turnover rate like? How about in the dept I'd be joining?"
Yes, though personally I tend to be more direct than euphemistic: "How many people have left the company/department in the past year? Why did they leave?"
The thing about "dangerous" questions like these, and asking about realistic working hours, and asking about IP clauses in the contract, is that good employers will usually be more than happy to have chance to explain why they're not like the bad employers. Most will enthusiastically tell you that they have low staff turnover. In terms of copyrights, particularly at the young companies looking for good people, I've had a senior interviewer tell me immediately that he himself had got the contract adjusted to clarify that, and it certainly wouldn't be a problem. For working hours, I've had a much wider range of answers, but usually pretty honest.
I have never, to my knowledge, missed out on an offer that I would have accepted because I asked such questions. I may have lost at least two offers, but in both cases I already knew I wouldn't accept anyway after evasive or outright damning answers to the working hours question, so the question served its purpose.
Clearly YMMV, particularly if you're desperate for a job or if you're happy working for corporate behemoths that tend to have less flexibility in their contracts (and whose HR people may black flag anyone who asks too many questions).
The other thing I always like to ask, though it's probably best to leave it until after the first interview, is to see a sample of their code and documentation. Just as they can tell a lot about me from my solution to a coding problem, so I can tell a lot about them by seeing what kind of code they actually write. I have never been refused this request, though most places ask you to wait until the next visit, so it might be worth mentioning it in advance if you're going back for a second interview and know it's likely to be the last one.
My experience is that once you're past any HR goons and you're dealing with techie folks you might actually be working with, good people will be quite enthusiastic to show you something they consider good code and happy to accommodate your request. It puts them on familiar territory, and makes for a more interesting (and memorable) interview for them than the other ten they've done this week. As a convenient side effect, as well as giving you chance to see their code, it also gives them a chance to show off and creates an atmosphere of fellowship and professional respect--a good discussion about their code can make them start to think of you as one of them before you've even left the interview.
Again, I'm not aware that I've ever missed out on an offer I would have accepted because of asking this question, though again there have been a couple of places whose offers I would probably have turned down if I'd received them after seeing the sort of code I'd be working with.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
MSN Careers has an article titled You Said What?! - 43 Things Actually Said in Job Interviews.
Yeah, everyone can be stupid in an interview. Learn and laugh from their mistakes so you don't make one.
"Giving money and power to governments is like giving whiskey and car keys to teenage boys." - P.J. O'Rourke
This is the worst advice I've seen on Slashdot. I'm a hiring manager. I conduct several interviews per week. It is a terrible red flag if someone does not have any questions. It demonstrates a lack of curiosity and empowerment. I need to hire curious people who will find and solve interesting problems for the business. The questions the candidate asks are a means to deciding if the he or she has what it takes.
That does indeed change things but you are still in dangerous water without clarifying yourself. If you asked those questions and didn't follow up with keywords like "productivity", "morale", and "TCO" then you are still a prima donna or worse, a religious zealot.
Letting people choose their own email client and develpoment platform might be okay, but it really depends on the organization. If you are hired to grow a development team, you better be well versed in the tradeoffs between "every gets outlook" and "lasse faire--anybody runs anything". At your level, you are hired to make the business more competitive. You better make it perfectly clear you aren't some zealot who will be hellbent on turning us into the next FSF regardless of the business justification. Once you've turned off my "zealot alert" radar, then you can ask these kinds of questions.
but definitely ask how long the position is intended to exist. Sometimes instead of going with a contractor like Tek Systems for a 1 year project, they just hire someone. But since everyone finds out that it's a temporary spot, they stop telling people so they can finally get one hired. Then to make sure you get the job, if they say it's only for the duration of a large project, say that's fine and they'll be shocked and lean towards hiring you. Then do such a good job that at the end of the project, they don't want to lose you and either increase their staff budget or fire someone else.
Google's Super Secret Search Algorithm: SELECT @search_results FROM internet WHERE @search_results = 'good'
A lot of these are questions I would never ask in an interview.
"What desktop hardware/software will I be using?" could be interpreted as "I'm a hardware bigot and will whine if I don't have a huge display and four white-hot cores." or "I don't touch Winders. I plan to reimage my PC with Mepis and I refuse to use any email client except Mulberry". Unless you want to show proficiency in a particular tool -- "Lotus notes? Yes, I've got several years' experience" -- I'd leave the topic alone. Your desktop is whatever it is. You'll get used to it.
"Are there team get-togethers?" == "I expect us to spend time screwing off under the guise of 'team building'. How close is the nearest bar?"
"What are the typical hours?" == "I am concerned about working too hard."
"What is your goal for the next etc" is a question directed at the interviewee, not the interviewer.
I would say "I expect to be on-call" as an opening for the interviewer to describe the on-call process.
I would know ahead of time what the company's stock has been doing, (if publicly traded) and be prepared to ask reasonable questions about the company business. My job doesn't end at my cube doorway -- it's important to understand the big picture.
I ask about education benefits, because I want to keep on top of my game, and I want prospective employers to know that.
Questions about the environment -- promotion process, product and documentation lifecycle, -- are fine, but don't get too militant about it if the boss doesn't think these things are important. There will be time for that battle after you're hired.
Find out if there are any tools or systems with which you are not familiar, and then express eagerness to learn them.
If there's a part of the process that's in disarray, (documentation, for instance) and you get signals that the boss would like to see improvement in this area, express eagerness to help straighten it out, and come up with a few suggestions.
I ask if it's ok if I eat at my desk. This isn't as arse-kissing as it sounds. I worked for one place that forbade eating at one's desk due to ant infestation.
In general, I try to avoid questions that might raise a red flag about how well I might fit in, or which might be considered concern on my part about how much effort I will be making. I am adaptable -- I've had ASCII terminals, X-terms, Windows, Sun and SGI workstations in front of me, and a variety of tools, some really obscure. It matters less what my work environment actually is than that it match the rest of the team.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
For IT, keep an eye out for some telltale warning signs. Lots of Dilberts hanging on a cube wall are a telltale clue that people there aren't entirely happy with their jobs, and the cartoons can be an important clue into what exactly is not functioning well within the company. Also ask just before you leave or prior to the start of the interview to use the bathroom. The state of the bathroom is another good sign of how the company treats its employees, and you're going to have to use that thing during the after-lunch rush hour and such. If it's like someone slaughtered a goat in there, you might want to consider giving them a miss.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
Instead of asking how often people are promoted, I ask what percentage of their management comes from people promoted within the company. I think it mitigates the idea that you're just using a position as a stepping stone while still getting you the answer you want.
Plus, I think it's important to know that there's a good possibility that your manager was at one point capable of doing the job you're applying for. Honestly, knowing my potential manager doesn't have unrealistic expectations is a lot more important to me than hypotheticals about whether I'm getting his job when he moves up or on.
If I'm set up for failure, I'm not going to get his job either way. Effective schmoozers might, but I'm not one of them.
-- It is no measure of health to be well adjusted to a profoundly sick society.
I once interviewed for a non-profit who asked what my salary requirements were and I said "about $70->$90k" and he immediately shot back "unfortunately we are budgeted for around $55k". With that, we both knew this wasn't gonna work so we didn't bother wasting more time.
That is an excellent example of a successful first interview, and one that a job hunter should be prepared for. A good follow-up would be
"Okay, then, I see we don't have a match on this position, but we do have a few minutes remaining for this interview. Are you aware of any positions that are available either with your institution or through your associations with colleagues in other institutions that match my resume and salary requirements?" That is, be prepared for the interview to terminate early because of an obvious bad fit, and be ready to try to turn it into a networking opportunity. The best outcome would be the interviewer saying that "You might try the Foo Foundation. John Smith-- a fellow in their HR Dept-- and I collaborated on designing this job announcement and a similar one that Foo is about publish. You can use my name in your cover letter and ask John to give me a call. If you give me permission to do so, I can tell him that we interviewed you and might have hired you if we had a larger budget to work with."
The chances of this kind of thing happening are pretty small. But they are zero-- nothing, nada, zip-- if you aren't prepared to shift a dead-ended interview into a networking opportunity.
Will
Ahhh,, the European vs US standards.. unfortunately there is no law on vacation days here in the US.. Legal holidays yes,.. We are a strange people, we work more hours, and get less benefits that we now have to pay extra for.. When a union tries to fight to keep their better medical coverage, that their workers are lucky enough not to have to contribute to (Like the way it used to be) The average person looks at it backwards and thinks "bad union worker, why should they not have to pay".. instead of "my employer is bad, why should I have to pay."... And many of these same people.. These people who get the crappy benefits that cost them.. well they just want to keep things the way they are.. Healthcare system reform.. what are you crazy ? .. it's just fine.. Many don't remember.. but back in the eighties it was the norm NOT to have to contribute to your health plan and I wish I could get that kind of coverage now, but even the most expensive plan that most places offer, don't touch what I had, and have high deductibles to boot.. our system is broken... and people will fight to keep getting screwed over.. go figure.
waiting for ad.doubleclick.net
in interviewing or being interviewed.
Your expression "the interview" reveals this.
Most non-entry level positions are filled by a process involving multiple interviews of multiple candidates over a period of days or weeks, often involving a pool or team of interviewers and a set of candidates that have made it past the initial filters. One of those filters being "the interview" that you have experienced.
Those candidates that pass the initial filters get further probing, meet more of the current staff, and eventually this results in offers for some and opportunities for them to counter.
There's no way a company making an offer is putting you "on the spot". When they do make an offer, the opportunity to ask the questions you so value becomes available. They say we offer $$$. They also offer XXX PTO, such and such working hours, etc. All of this is part of their offer package and subject to discussion and negotiation from the moment the offer is made until an agreement is reached, not before.
If such questions are so important to you that you must have the answers upfront, just send an email to the HR department before you send in your resume. Doing so will save both of us a lot of time and trouble.
Good judgement comes from experience, and experience comes from bad judgement.
- W. Wriston, former Citibank CEO
My main question is what is the structure of my team. How many people are doing the same job I do in my team. Is there a lead? Is there a manager? Who is the manager managing, just our group or others as well? I have enough experience that I don't want to be in a team which has a lead in it. When I have a manager who is not involved in day to day IT work that is ideal as he wants me to succeed. Leads always want to make sure you are not doing better than them as that is a threat to their position and job. On the other hand, doing a good job is something a manager wants you to do. If they say there is no lead I ask if anyone aside from my manager inside the team will be responsible for assigning me work and that sort of thing - digging out if there is some covert lead. I make sure this is straight with my manager.
I made another comment on here already, along these lines.... but I'll re-iterate anyway.
I've definitely had interviews where, by the end, I really had no useful questions that came to mind -- simply because after an hour of so of "back and forth" about the company and the job requirements, plus a tour that let me see things ranging from the dress code to the environment employees were working in, there wasn't much left to ask.
To me, saying "I think you've answered all of my questions right now, but I'll definitely follow up with you if I think of anything else." is a perfectly honest and legitimate answer. Certainly looks better than trying to make up some silly question you really wouldn't have asked otherwise, but are trying to throw out there just so the employer can check-off his list that "Yep, they asked me something."
Rather than "red flagging" a person for not having a question at the end of the interview, I think you'd be wise to ask them questions DURING said interview to determine their problem-solving capabilities. (EG. Ask them to tell you about 1 or 2 situations in previous jobs where they encountered a puzzling problem, and how they went about solving it.)
Better than where I work! Our policy is "no blood on the carpet".
OTOH, your contract allows the beating of customers. They've both got their pros and cons, I guess.
If I mod you up, it doesn't necessarily mean I agree with what you've said, sorry.
If you expect to be in and gone in one year, ask for salary on the high end of the scale. If not, try to pick a range that won't see you the first to go at the first round of layoffs.
Remember, some positions are hired on pure speculation - the BDM is "90% sure we're going to get this contract so we have to ramp up". This sort of position is a wee bit volatile, and far too common for comfort. You'll need a bit extra at the end to finance the next job hunt, so don't live too high in the meantime.
Other questions: "What happened to my predecessor?" - If you have no "predecessor" then the job is a new opening. Follow that bit of data with "How is the job funded?" These are the sort of questions that can be hugely useful, as well as make a decent impression. If you don't like the answers, back out with a smile - if the job isn't backed with a good business case, it's waste of everybody's time to proceed further.
Do not mock my vision of impractical footwear