|
|
|
|
|
by petesalty
5887 days ago
|
|
Interviewing is a two way street, or at least it should be. If the interviewers don't want to be interviewed it's a bad company.
To that end here are some points I'd like to add (I'm currently hiring some programmers and would love to have any of them ask me for the following. None have so far): 1. Ask questions about how a manager would handle a situation. If you're not being interviewed by your direct manager (why not?), ask what the company would do. Start off simple, "I want to use a new technology that we don't already support but I believe will make a project easier/quicker/more profitable. What's your response?" and work up to harder things "We're pushing to a rapidly approaching hard release date and someone vital quits. The team is already at breaking point. There's no way we'll deliver. What do you do?" 2. Ask to see the working environment and sit down and talk with other employees of all kinds (programmers, designers, secretaries) without management present. Not for long, just 15 minutes. If they say no, it's a problem. 3. If you're expected to maintain and existing code base, ask for code examples. They often do it of you, it's only fair. Nothing in particular, just something so get an idea of the quality. Just a few of the things I'd be more than willing to do as a manager. |
|