Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save jondruse/405178 to your computer and use it in GitHub Desktop.
Save jondruse/405178 to your computer and use it in GitHub Desktop.
The last few jobs I've had have proved to be somewhat disappointing. What I realized
after a few months was that it was mostly my fault for not asking the right questions
In a way a job interview is really for both parties. Not only do they have to think
that you fit in, but you have to think that you'll enjoy working there. Here's a
pretty long list of questions to pull from. Or you could ask them all, up to you.
General Questions:
1. What is the dress code?
2. What are the normal business hours?
3. What are my immediate supervisor's hours?
4. Do you offer benefits?
5. What is the waiting period for benefits?
6. What is your policy on working from home?
7. How much vacation/sick time would I get?
8. What is the average employment length?
9. What is a typical day/week like?
10. What is an atypical day/week like?
11. Would I be working in a cubicle?
12. How many people are in the department?
Technical Questions:
1. What version of ruby/rails are you currently running on?
2. Do you plan to upgrade?
3. How closely do you follow ruby/rails conventions? (MVC, db schema, etc.)
4. Do you work as a team?
5. Does code get reviewed before it can be committed? By who?
6. How much test coverage do you have?
7. What is your deployment strategy? ie.. shell script, capistrano, CI
8. Do you use git? svn? other?
9. Do you have a development strategy? What is it?
10. Do you have a regular release cycle?
11. What platform would I be developing on? Mac? Linux? ... Windows? (shutter)
12. Would I be able to bring my own computer?
13. In what state do you see the application in 6 months, 1 year, 5 years?
You probably get my point. Make sure you know what you're getting yourself into. And
remember, just as you are putting your best foot forward, so are they. Not that they are
intentionally deceiving you, but they probably won't naturally offer this information. So
it's up to you to find out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment