Web Developer Interview Questions and Tips

Web developer interviews can be complex. The diversity of the work creates many additional elements that should be considered during a job interview. Even if you're an experienced developer, you may find yourself dealing with exotic technical subjects. You can also find yourself answering very basic questions, actually describing font size issues and how to make different fields work the same way.

Because of the wide range of possible subjects, it is advisable to structure your interview preparation according to the job criteria. Pinpoint essential job functions and technical requirements.

Preparation for interview questions

You will usually get two basic types of questions: Informational, and practical. Practical questions will ask that you give practical examples to solve problems. The most common subjects for web are:

  • Informational: Currency of skills, types of systems used, functionality, specific experience in development, web standards.
  • Practical:  Expect to be asked about core subjects like JavaScript, HTML, XHTML and CSS as essential practical questions.

Other practical questions include:

  • Elements
  • Codes
  • Development languages
  • Using class definitions
  • Script
  • Response codes
  • Memory issues
  • Accessibility policies and practices
  • Control systems
  • Configurations of processes
  • Debugging
  • Client-specific subjects.

Questions you Should Ask

During your preparation you should also:

  • Ask about any area of the job where you're unsure of your subject matter or technical aspects.
  • Check out the employer's product, analyze the standards being applied, because they're an indicator of what's expected.
  • Investigate any unfamiliar features or functions related to the job.
  • Make sure your portfolio is a good match for the job, and contains the right technical elements to prove competence in the essentials.

Practice questions

These are common forms of informational and practical questions. They are also very important issues to employers. Each of these questions relates to your style, preferences for tasks and competencies in some way:


  • Which developmental languages do you least like to work with?
  • Do you do ongoing training, or do you remain current through your work?
  • Do you have a preferred browser you like to work with?
  • Can we have a look at your portfolio, showing how you use CSS?
  • What are your specific areas of interest in this job?
  • Show us some websites you've developed.

Practical questions:

  • What's wrong with this piece of code, if anything?
  • This code doesn't run. How would you rewrite it, to make it run?
  • How would you make a class definition, with this set of elements?
  • What is response code 404? When does it occur?
  • How do you make this material compliant with Web Content Accessibility Guidelines?

The range of questions is structured logically to take you through the issues of working with the employer's materials. Just stay focused, and give straight, clear answers.