Skip to content

Instantly share code, notes, and snippets.

@josephmcasey
Last active November 16, 2017 18:47
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save josephmcasey/b73990c6322191c43698d6c1ac809e7e to your computer and use it in GitHub Desktop.
Save josephmcasey/b73990c6322191c43698d6c1ac809e7e to your computer and use it in GitHub Desktop.
Coding Interview
## My standbys:
What languages/frameworks to you usually work with?
What development tools- IDEs, Bug Trackers, Version Control, etc do you use?
What's your development methodology like (Agile, Waterfall, Scrum, Crystal, etc)?
Do you have dedicated QA personel? Even if so, do developers do some amount of their own unit testing?
## The Joel Test:
Do you use source control?
Can you make a build in one step?
Do you make daily builds?
Do you have a bug database?
Do you fix bugs before writing new code?
Do you have an up-to-date schedule?
Do you have a spec?
Do programmers have quiet working conditions?
Do you use the best tools money can buy?
Do you have testers?
Do new candidates write code during their interview?
Do you do hallway usability testing?
## Some things to help you decide if you really want the job:
What's the best part of your job? And the worst or most frustrating part?
Why do people tend to leave the company?
If I took this job, what would you most hope I could take care of for you? (Especially to your would-be manager, but also to peers, other managers; it's curiosity not sycophancy.)
What are the goals for this project over the next year or two? What changes would you like to see in the way the project runs?
How do the short and longer-term project goals get set and how is work distributed?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment