arialdomartini /Back-End-Developer-Interview-Questions

A list of back-end related questions you can be inspired from to interview potential candidates, test yourself or completely ignore

★ 16,987⑂ 2,060
Created 2014-06-06
16,987
stars
+0+1+7
2,060
forks
–
watchers
–
prs
–
issues
–
releases
–
discussions

README

Back-End Developer Interview Questions
======================================

This page has been translated to Chinese by monklof.

I started writing down this list as my personal notes of topics I discussed with colleagues and friends, and that I wanted to deepen...

I'm not a big fan of asking technical questions in job interviews: I rather prefer to sit together with candidates in front of some real code, hands on the keyboard, facing a real problem, and to have a full day of pair programming, hopefully rotating with all the other team members. It is one of the best opportunities to know each others' style and to let candidates know some details about their future job.

Yet, I feel some categories of technical questions could be a good starting point to begin an engaging conversation. 

This repo collects a number of back-end related questions that can be used when vetting potential candidates. It is by no means recommended to use every single question on the same candidate: that would take hours, and would have no sense at all, as they cover a too broad set of topics for a single developer's to possibly know. Browse the section you find more relevant for your context, and pick the questions that give you more ideas on the conversation to have.

This project is admittedly inspired by Front-end Job Interview Questions by @darcyclarke

 Where are the answers?
I didn't include any.
Most of the questions are open-ended, and some of them just don't have a right or a wrong answer. On the contrary, they are intended to be used as the starting point for a conversation that hopefully tells you more about the person's capabilities than a straight answer would. Personally, I would even choose the questions whose answers are not yet clear to me.

Feel free to open a Discussion.





 Table of Contents

 Questions about Design Patterns
   Globals Are Evil
   Inversion of Control
   Law of Demeter
   Active-Record
   Data-Mapper
   Billion-Dollar Mistake
   Inheritance vs Composition
   Anti-Corruption Layer
   Singleton
   Data Abstraction
   Don't Repeat Yourself
   Dependency Hell
   Goto Is Evil
   Robustness Principle
   Separation of Concerns

 Questions about Code Design
   High Cohesion, Loose Coupling
   Index 0
   TDD
   DRY Violation
   Cohesion vs Coupling
   Refactoring
   Code Comments
   Design vs Architecture
   Early Testing
   Multiple Inheritance
   Domain Logic in Stored Procedures
   OOP Took Over the World
   Bad Design

 Questions about languages
   3 Worst Defects
   Functional Programming
   Closures
   Generics
   High-Order Functions
   Loops and Recursion
   Functions as First-Class Citizens
   Anonymous Functions
   Static and Dynamic Typing
   Namespaces
   Language Interoperability
   Hate of Java
   Good and Bad Languages
   Referential Transparency
   Stack and Heap
   Pattern Matching
   Exceptions
   Variant and Contravariant Inheritance
   Constructors and Interfaces
   Node.js
   Java and Time Traveling
   Eliminate Nul

Snapshot: 2026-11-10T09:35:25Z · Data license Apache-2.0 · JSON