Summary
The questions you forget to ask when you are interviewing for a job, but wish you'd asked after taking the job.

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?

What questions do you wish you had asked?

Talk Back!

Have an opinion? Readers have already posted 42 comments about this weblog entry. Why not add yours?

RSS Feed

If you'd like to be notified whenever Bruce Eckel adds a new entry to his weblog, subscribe to his RSS feed.

Digg | del.icio.us | Reddit

About the Blogger

Bruce Eckel (www.BruceEckel.com) provides development assistance in Python with user interfaces in Flex. He is the author of Thinking in Java (Prentice-Hall, 1998, 2nd Edition, 2000, 3rd Edition, 2003, 4th Edition, 2005), the Hands-On Java Seminar CD ROM (available on the Web site), Thinking in C++ (PH 1995; 2nd edition 2000, Volume 2 with Chuck Allison, 2003), C++ Inside & Out (Osborne/McGraw-Hill 1993), among others. He's given hundreds of presentations throughout the world, published over 150 articles in numerous magazines, was a founding member of the ANSI/ISO C++ committee and speaks regularly at conferences.