Professional Documents
Culture Documents
1) Why are you hiring for this position? or Why is this job open?
Many programmers don't dare to ask this question, but in my opinion, it's a good
question, but you better ask this on the face to face interview, not in telephonic
one. Just the response to this one question there, and the way that the Interviewer
answers it (if they're being circumspect, direct, shifting their eyes, etc.) will
answer a substantial amount of the questions you will have in your mind. Even if
the answer is just "we need more help" you should hopefully get a better idea of
what you're signing up for and your responsibilities.
4) How are decisions made? Is architecture dictated top down? Are ideas from anyone
welcomed? If so, in what scope/context?
This will give you some idea about their technical setup and beaurocracy.
6) "Are there any projects or big picture goals the company is focusing on at the
moment that if I hired, could keep in mind as I'm learning the ropes? And if so, is
there something that I could do I'm my position that would help further the
company's progress toward that goal?
14) What don't you like about working here and what would you change?
17) What are some challenges that will face the person filling this position?
19) What is the organization's strategy/plan for the next five years, and how does
this department fit in?
This will give you some idea about your job security. If the company has well
defined planned or, at least, thinking some years down the line then it's the good
time to join them. This usually happens when a new leadership has taken place.