Sort of like the Joel Test I guess, except you don't need to limit it to checklists of yes/no questions.
|
closed as off topic by Walter, Jim G., Mason Wheeler, ElYusubov, gnat Dec 4 '12 at 7:24
Questions on Programmers Stack Exchange are expected to relate to software development within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.
|
Asking a company good questions is an important part of your interview. It will enable you to really show that you know what you're talking about. It also allows you to find out if the company is a good match for you. An interview should be about evaluating both the to be employee and the to be employer, not one sided. Here's a list of questions you can start with, and as you discuss their answers there will probably be other topics that come up that you can discuss. You can also make suggestions to the company if you find that their process can be improved. In addition to the Joel Test questions...
|
|||||||||||||||||||||
|
|
I have seen this somewhere. "What would you expect me to have accomplished in 6 months?", just to set expectations right. |
||||
|
|
|
||||
|
|
|
"Can I take a look at your coding standards document?" If there's something really silly in there, I will steer clear. Recent example: "Every private field must have a public getter and setter method" (Java) |
|||||
|
|
This isn't exactly something you can ask, but something to be aware of: Having gone through quite a few interviews and jobs, one thing that I think is crucial is to identify the potential personality clashes as much as possible among your potential co-workers. Over the years I've found that there are a couple of personality types common in our industry that can make things miserable and/or downright impossible. Team cohesion is extremely important in this line of work, and I've found that it's best to avoid getting involved with toxic personalities if at all possible. |
|||||||||||
|
|
Describe fully the complete build and release cycle including who is involved and how long it takes to get things moved from dev to test to ... to prod. It is surprising how many 'top' companies don't have this nailed, and how much pain a badly implemented process ultimately causes. |
||||
|
|
If the answer to any of these is "no", it is a big red flag. |
|||||||||||
|
|
@Brian R. Bondy coverned a lot of what I ask. I like to get a walk through the spaces. You can tell alot about a company from seeing how people interact with each other as you walk through. I ask about the corporate culture - I want a feel for how bureaucratic and structured the place is. I have found through the years that too unstructured is worse than too bureaucratic. Too often they aren't really serious about producing a product to make money with and will go down the tubes. I want to work with people who want to work, not play. I want to knwo if I will be working with people as part of a team or if I will mostly be working on projects by myself. I want to see how the position fits into the org structure and if there is room for growth. I want to know what interesting challenges the position will bring, not interested in doing rote work. If I can't learn something new and interesting in a job, it's not for me. Having been burned once, I ask about expected overtime, making it clear, I don't object to working overtime for a deadline, but am not interested in working overtime as a way of life. Better to know up front. |
||||
|
|
|
|||||||||||||||
|
|
I didn't see these mentioned. Apologies if I overlooked.
|
||||
|
|
|
I notice : "How much does it pay?" didn't make it on the list .. :P and I wonder why not! It's a key factor! |
||||
|
|
|
What I would want is to get a sense of the top management, because their attitude will trickle down to the entire company. Is everything just a "business decision", or do they take an interest in and care about people? It shows up in how they treat employees, vendors, contractors, and customers. Do they pay bills on time, or do they "age" them? Do their customers like working with them? Do they have a good reputation in the business community? You can't ask them these things directly, but you can do your homework and find out. |
||||
|
|
|
What I've found very interesting to ask is:
This has yielded a lot of very good insights into what people really think about their environments and how comfortable they feel speaking up about them. Usually starts a very good dialog and sometimes gives a glimpse into contended issues within the team. |
||||
|
|
|
Coffee? If the answer involves a vending machine - run. |
||||
|
|
