|
|

Welcome to Rick Huby's Website

Web Designer Interview Questions

30 Jul 2007 - For a recent hire I had to put together some questions for the candidates; I found these quite useful so thought I would share them.

The web developer job at eConnected compromised of two core components; XHTML/CSS development and PHP work. Other aspects of the job included JavaScript, MySQL and support of existing website, however I felt that these were secondary requirements.

I split the interview into two sections; general interview questions and a test of the candidates technical ability in the core aspects of the job.

Warm Up

I wanted to start off the technical questions with just some easy questions to get them relaxed (developers seem to be a nervous bunch on the whole!). These questions also served to identify the candidates who really didn't have enough starting knowledge or impetus to be suitable for the job.

  1. Can you explain the difference between server-side scripting and client-side scripting.
  2. Can you explain what XHTML is and how it differs from HTML. What about Tranisitional and Strict Doctypes?
  3. How do you keep your web design knowledge up to date?

PHP, XHTML & CSS Tests

CSS Test

I was looking for a decent understanding of CSS syntax in this test (application of CSS is tested separately). I wanted to make sure the candidate knew enough CSS to get by.

Answers:

  1. No closing ; for each property/value pair
  2. Using ; as a separator instead of , 3 font-face doesn't exist in CSS (looking for font-family)
  3. Tiny is not a valid font size

XHTML Test

XHTML is fairly straight forward and anyone who could deal with the CSS test should be able to breeze through this; however just to be thorough I wanted to go through this exercise.

Answers

  1. There is no document type declaration.
  2. The title should appear between head elements.
  3. The closing heading tag is incorrect. It should be an h1.
  4. The paragraph containing the non-breaking space entity,  , should be removed as we should not be using HTML elements for layout purposes.
  5. The & should be written as & or &
  6. Bonus points for mentioning that a more descriptive page title or the use of meta data would increase the chances of the page being usefully indexed by search engines.

PHP Test

For the PHP test I put together 6 pieces of simple code and asked the candidates to explain what was happening or to tell me what the outcome was.

Whilst these were written in PHP they are very general questions and should be answerable by anyone with decent development knowledge.

Answers

  1. 10 - Trick questions relating to the scope of the the variable $num;
  2. abc - String concatenation
  3. $b - $a is a boolean and $c is an array
  4. 0 - Simple logic test
  5. Foreach loop builds an unordered list if there are any elements in the array $arr. It prints out the key and value of each item in the array.
  6. A class called person with "name" and "email" variables with getter and setter methods. set_email uses regular expressions to check if the email passed is valid and returns a boolean notification.

XHTML/CSS Coding Approach

We had previously tested to see if the candidate had a basic knowledge of the syntax of XHTML and CSS but this is a distinct skill from the approach to the coding of a web page.

In the final step I gave the candidate a screengrab from one of our websites and asked them to discuss how they would approach the coding of the page.

Screenshot from www.dynoadd.com

Whilst not an exhaustive list, I was looking for them to discuss these sort of things:

  • Use of floats and/or absolute positioning to create columns
  • Use of CSS/Javascript for the drop down menu
  • Overlapping image of the bottles and the issues that may arise (for example the use of a PNG in Internet Explorer 6)
  • The fixed height section with overflow: scroll
  • Their approach to the main image on the page that fades behind the fixed height section
  • Approaches to the curved corners and fades used in the design
  • Cross browser considerations

The crux of this test was to see that the candidate had a sound approach to the development of a web page from an initial graphic.

In Closing...

Overall I'm very happy with the process as I feel that it broadly tests the candidate in the areas that are relevant to the job. I would tweak the questions slightly for a more senior role, but I am convinced that the method is a sound one.

For anyone looking to incorporate this sort of test I'd just like to mention the non-technical aspects of the interview. In the end these were pivotal in my choices for the second round of interviewing. The critical instance technique worked well for me ("can you give me an example of...") and finding ones suitable to the role may help understand a bit more about the suitability of the candidate.

I won't claim to be an authority on this subject however and I'd love to hear any feedback you hae, so please feel free to add a comment.

Comments

Hoobs, Hiring staff is a total nightmare - as you'll know - it never works in the favour of the employer once you've employed a staff member so to be cautious before hand is the only way to do it and this test you have devisied seems to be one of the better ways of checking for general knowledge of the role - which is really important in your game. My advice also would be to hire for attitude ( a good one obviously)
www.freyasykes.com

Freya Sykes | 04 Jul 2008 at 11:18:25

Add Comment

Unfortunately I have had to disable comments temporarily as I am getting too much comment spam. By all means drop me an email (hello at rickhuby dot com) if you want to get in touch about anything. Hopefully I'll magically discover oodles of time laying around and get this sorted quickly.