Show Menu

Dev Interview Cheat Sheet (DRAFT) by

This is a draft cheat sheet. It is a work in progress and is not finished yet.


What's your favourite language and why?
Do you have a preference for any particular framework?
What would you consider the strengths of $language to be?
Do you think there are any scenarios where $language would be an inappr­opriate choice?
What features would you like to see added to $language?
Do you find any langua­ges­/fr­ame­works intimi­dating?
What do you think makes good, mainta­inable code?
What do you understand by Test Driven Develo­pment (TDD)?
What do you understand by Continuous Integr­ation (CI)?
What is your experience of version control?
What are your thoughts on Design Patterns?
What is your general strategy towards docume­nting your code?
If you were faced with a project that had perfor­mance issues, what steps would you take to invest­igate them?
If you were faced with a legacy project with mainta­ina­bility problems, what things would you look to improve to get it on a stable footing?
How do you feel about code reviews?
What is your unders­tanding of Domain Driven Design (DDD)?
Swap $language for the language relevant for the role you are interv­iewing for.


Tell us about yourself?
What projects are you working on in your spare time?
How do you keep up with tech trends?
What was the last project you worked on?
What are you looking for in a new position?
What was the last big mistake you made and how did you recover from it?
If you're put on a partic­ularly busy project team with docume­ntation on how to set up a develo­pment enviro­nment but you run into an undocu­mented issue, how would you look to progress?


Do you have any experience of working in an Agile enviro­nment?
What is your unders­tanding of the SCRUM method­ology?
What are your thoughts on daily stand ups?
Would you be comfor­table demoing a feature you worked on to a client?