25 web developer interview questions

Walk me through how you'd fix a bug a customer reported on our site.

A good answer: Reproduce it first, find the cause, fix it with a test or a check, and explain what happened in plain words.

How do you keep us updated when a task is taking longer than planned?

A good answer: They say so early, explain why, and offer a new estimate or a smaller version that could ship first.

How do you handle access to our code, hosting and passwords?

A good answer: Their own accounts with only the access they need, two-step sign-in, and no secrets in code or chat.

What's your main stack, and what have you built with it recently?

A good answer: A specific stack and recent projects they can explain in detail.

How do you estimate a task?

A good answer: They break it into parts, include testing and unknowns, and say how confident they are.

How do you test your code before it goes live?

A good answer: Automated tests where they help, manual checks, and a staging site.

How do you use Git when you work with others?

A good answer: Branches, clear commits, pull requests and code reviews.

How would you make our website faster?

A good answer: They measure first, then fix the biggest problems, like images, scripts and caching.

How do you document your work?

A good answer: A short readme, comments where the logic isn't obvious, and notes on how to deploy.

How do you keep a site secure?

A good answer: Updates, only the access each person needs, no secrets in code, backups, and watching for errors.

The site goes down on a Friday night. What do you do?

A good answer: They check the status and logs, roll back if needed, and update you as they go.

I ask for a feature you think is a bad idea. What do you say?

A good answer: They explain the trade-off in plain words, suggest an alternative, and build what you decide.

You inherit messy code from the last developer. What do you do?

A good answer: They don't rewrite everything: they fix what's needed and improve it bit by bit.

A task is going to take twice as long as you said. What do you do?

A good answer: They tell you early, explain why, and offer a smaller first version.

You find a security hole. What do you do?

A good answer: They tell you straight away, fix it, and check whether anyone used it.

A library you rely on is no longer supported. What do you do?

A good answer: They assess the risk, find a replacement, and plan the switch.

We can't afford a rebuild. How would you improve the site?

A good answer: They pick the changes with the biggest effect for the least work.

How would you plan your working day around our hours, and how would you tell us if something came up?

A good answer: The hours they can reliably cover, how they'd warn you early about a sick day or an internet cut, and what backup they have.

Tell me about a time you got stuck with no one around to ask. What did you do?

A good answer: They tried to solve it first, noted what they tried, then asked one clear question with the details instead of waiting or guessing.

How do you like to get feedback, and how should we tell you when something needs to change?

A good answer: A straight answer about what works for them, and an example of feedback they took and how they changed their work.

What would you want from us in your first week to do this job well?

A good answer: Specific questions about tools, logins, priorities and who to ask. It shows they think ahead.

Which part of this kind of work do you enjoy most, and which part do you find hardest?

A good answer: An honest answer with a real example for each, and what they do to handle the hard part.

What does your workspace look like, and what's your backup if the power or internet goes out?

A good answer: A quiet space, a reliable connection, and a real plan B: a second connection, a nearby place to work, or a phone hotspot.

How do you show your work when nobody can see you working?

A good answer: Updates without being asked, a shared task list they keep current, and a short note at the end of the day.

Tell me about a time you disagreed with a manager or client. How did you handle it?

A good answer: They raised it respectfully with reasons, listened, and went with the decision once it was made.