Web developer interview questions, with a scoring guide
Builds and looks after the website so it's fast, secure, accessible and connected to business tools. Here are 19 questions for a web developer interview. Each comes with a follow-up and a 1 to 5 scoring guide so you can compare candidates fairly.
Use these as a free interview guide
Writing the job ad too? Start from our web developer job description template.
Questions specific to the web developer role
Role-specific
Walk me through how you update plugins or the CMS on a live business website.
Follow-up: What would you do if the update broke something?
1 WeakClicks update on the live site.
3 SolidTakes a backup, then updates the live site.
5 StrongBacks up, tests on staging, checks key pages and forms, deploys at a quiet time, and has a rollback plan ready.
Role-specific
The owner says the contact form 'stopped working' and leads have dried up. How do you track down the problem?
1 WeakRebuilds the form from scratch.
3 SolidTests the form and checks the spam folder.
5 StrongReproduces it, checks form logs, email delivery and recent changes, fixes the cause, and recovers any lost submissions.
Role-specific
How do you make sure a page you build works for someone using a screen reader or only a keyboard?
1 WeakNot sure.
3 SolidAdds alt text to images.
5 StrongUses proper HTML structure, form labels, a logical focus order and good contrast, and tests with a keyboard and a checker against WCAG 2.1 AA.
Role-specific
The owner wants to add a tracking pixel and a pop-up that collects email addresses. What do you check or raise before you build it?
1 WeakJust adds them.
3 SolidMentions it might slow the site down.
5 StrongRaises consent and privacy (PIPEDA, CASL consent for email), the cookie notice, page speed and pop-up accessibility, and suggests a clean way to do it.
Behavioural questions by skill
Behavioural questions ask about something the person actually did. Past behaviour is a better guide than "what would you do" answers alone.
Problem solving
Works out the cause and fixes it properly.
Tell me about a problem at work that you solved without being told how.
Follow-up: How did you work out what was wrong?
1 WeakWaited to be told what to do.
3 SolidSolved it with a common fix.
5 StrongFound the cause and fixed it so it stayed fixed.
Describe a time something went wrong in the middle of a busy day. What did you do first?
Follow-up: Who did you tell, and when?
1 WeakPanicked or froze.
3 SolidCalled for help right away without trying anything.
5 StrongMade it safe, tried the obvious fixes, and escalated with clear information.
Tell me about a time you noticed a better way to do a routine task.
Follow-up: What happened when you raised it?
1 WeakNever looked for one.
3 SolidNoticed it but didn't act.
5 StrongSuggested or tested it and can describe the result.
Attention to detail
Gets the small things right.
Tell me about a time you caught a mistake before it caused a problem.
Follow-up: How did you spot it?
1 WeakNo example.
3 SolidCaught one by chance.
5 StrongCaught it because of a habit or check they always do.
Walk me through how you check your own work before calling it done.
Follow-up: Has that check ever caught something?
1 WeakThey don't.
3 SolidA quick look over.
5 StrongA clear routine that fits the task.
Describe a task where getting the small details right really mattered.
Follow-up: What would have happened if they were wrong?
1 WeakCan't name one.
3 SolidNames one, but light on how.
5 StrongExplains the details, why they mattered, and how they got them right.
Communication
Explains clearly and keeps people in the loop.
Tell me about a time you had to explain something complicated to someone who was new to it.
Follow-up: How did you know they understood?
1 WeakCan't explain clearly, even in the interview.
3 SolidExplained it but didn't check understanding.
5 StrongUsed plain words or examples and checked they got it.
Describe a time you had to give bad news to a customer, coworker or manager.
Follow-up: What did you say first?
1 WeakAvoided it or left it to someone else.
3 SolidDelivered it, but bluntly or late.
5 StrongDelivered it early and clearly, with a next step.
Tell me about a time a misunderstanding caused a problem at work. What did you learn?
Follow-up: What do you do differently now?
1 WeakBlames the other person entirely.
3 SolidFixed the issue with little reflection.
5 StrongFixed it and changed how they communicate, such as confirming in writing.
Organizing and time management
Plans the work and meets deadlines.
Walk me through how you plan a typical work day.
Follow-up: What do you do when the plan falls apart?
1 WeakNo plan.
3 SolidA loose plan.
5 StrongA clear system, such as a list or calendar, and how they adjust it.
Tell me about a time you had several deadlines at once.
Follow-up: How did you decide the order?
1 WeakMissed some without warning.
3 SolidMet them by working late.
5 StrongPrioritized, planned, and met them or flagged early.
Describe a system you use to keep track of tasks, orders or paperwork.
Follow-up: Show me how you'd use it on your first day here.
1 WeakNone.
3 SolidMostly memory.
5 StrongA reliable system with an example.
Learning and coachability
Takes feedback and gets better.
Tell me about a time a manager gave you feedback on how to do something better.
Follow-up: What changed after that?
1 WeakCan't recall any, or dismisses it.
3 SolidAccepted it.
5 StrongApplied it and can say what changed.
What's something you're working on getting better at right now?
Follow-up: How are you going about it?
1 WeakNothing.
3 SolidA generic answer.
5 StrongA specific skill and a plan for it.
Describe how you learned the ropes at your last job.
Follow-up: What would you do the same way here?
1 WeakWaited to be shown.
3 SolidLearned from the training given.
5 StrongAsked questions, took notes, and got up to speed quickly.
Prescreen questions for web developer candidates
Ask these on a five-minute phone call or send them as a form before you book interviews.
- Are you legally entitled to work in Canada? (Yes / No)
- Which days and times are you available to work?
- When could you start?
- What pay are you looking for?
- What interests you about this job?
- Can you share links to live websites or code you have built or maintained? (Yes / No)
- Have you used Git for version control on a real project? (Yes / No)
How to score the answers
- Ask every candidate the same questions in the same order. That's what makes scores comparable.
- Write down what they did, not your impression. "Closed alone on a Saturday and restocked for the morning" beats "seems reliable".
- Score each answer from 1 to 5 against the guide under the question. A 3 is a solid, acceptable answer.
- Average the scores and read the notes behind any big gap between interviewers.
- Check references on the areas where you're least sure.
Questions to avoid
In Canada, hiring questions should be about the job. Human rights laws protect people from being treated differently because of things like their age, family status, disability, religion, race, place of origin, sex, sexual orientation or gender identity. Stay away from questions like these:
- "How old are you?" or "When did you finish high school?"
- "Do you have kids?" or "Are you planning a family?"
- "Where are you from originally?" (You can ask: "Are you legally entitled to work in Canada?")
- "Do you have any health problems?" (You can ask: "This job involves [a real duty]. Can you do that, with or without accommodation?")
This is general information, not legal advice. Rules vary by province.
Questions
What should I ask in a web developer interview?
Ask about the parts of the job that matter most: problem solving, attention to detail, communication, organizing and time management, plus role-specific questions such as "Walk me through how you update plugins or the CMS on a live business website." Ask every candidate the same questions so you can compare them fairly.
How do I score a web developer interview?
Score each answer from 1 to 5 against a short guide that describes a weak, solid and strong answer. Score what the person actually did in their example, not how confident they sounded. Then average the scores and read the notes behind any big differences.
What should I ask before interviewing a web developer?
Use a short prescreen: work eligibility, availability, start date, pay expectations and the must-haves for the role, such as "Can you share links to live websites or code you have built or maintained?"
Turn this page into a ready-to-use interview guide
Staffkin builds a web developer prescreen and interview guide in one click, gives you a fillable PDF, and lets you score candidates side by side. Free for your first job.
Start freeRelated roles