Defining a Web front-end developer (integrator) role

Each organisation would have a different set of requirements for an integrator or a front-end developer role. In this article I will outline the technical aspects only. Here is a sample job description which I think reflects this role: Technical qualifications Able to write semantic markup using HTML 4.01 Strict Doctype Knowledge of DOM Scripting Knowledge of CSS and cross-browser issues Responsibilities Implement Web user interface and interaction elements based on screen designs, wireframes, flowcharts and other documentation Integrate front and backend components Extract applicable screen design components from mockups Create proof of concepts Nice to haves Experience with image editing software Understanding knowledge of HTTP Familiarity with a LAMP environment Knowledge of OOP concepts Experience in XML/XSL Knowledge of microformats Familiarity with templating engines and CMS Familiarity with Wiki software Familiarity with revision control Good understanding of content Knowledge of accessibility Sample (easy) interview questions What's the difference between HTML and XHTML? What's UTF-8? What's the address element for? What's the difference between PNG8 and GIF format? What's HTTP 301? How do you calculate a selector's specificity? What's JSON? What's progressive enhancement? Can you think of any useful questions that are not overly technical — on the code level — but would be able to let you assess an applicant's knowledge?

• Article
• CreativeWork
• Document
• Entity
• Post

Gulam M

• Person

Gulam M

• Person

Gulam M replied on 2008-08-25 00:28:29

<div typeof='oa:TextualBody' resource='#note-20080825002829' property='rdf:value' datatype='rdf:HTML'> <p>Can you give examples of "hard" questions?</p></div>

• Annotation
• Note

Gulam M replied on 2008-08-31 03:52:29

<div typeof='oa:TextualBody' resource='#note-20080831035229' property='rdf:value' datatype='rdf:HTML'> <p>@Sarven - I like your definitions of 'easy' and 'hard' questions! Inspired by the 'complexity theory' in Computer Science ?</p> <p>@Ludo - Based on Sarven's definition, yes my question was hard! :P</p></div>

• Annotation
• Note

Jean-Michel Feurprier

• Person

Jean-Michel Feurprier replied on 2010-11-11 16:19:34

<div typeof='oa:TextualBody' resource='#note-20101111161934' property='rdf:value' datatype='rdf:HTML'> <p>Cool article, but now, why wouldn't you write a more 2010-ish post, about back-end developer and integrator roles?</p></div>

• Annotation
• Note

Ludovic

• Person

Ludovic replied on 2008-08-26 02:16:07

<div typeof='oa:TextualBody' resource='#note-20080826021607' property='rdf:value' datatype='rdf:HTML'> <p>I don't understand your question Gulam... too hard !</p></div>

• Annotation
• Note

note-20080825002829

• TextualBody

note-20080826021607

• TextualBody

note-20080828233031

• TextualBody

note-20080831035229

• TextualBody

note-20101111161934

• TextualBody

Sarven Capadisli

• Person

Sarven Capadisli replied on 2008-08-28 23:30:31

<div typeof='oa:TextualBody' resource='#note-20080828233031' property='rdf:value' datatype='rdf:HTML'> <p>@Gulam M, questions are relatively easy in a sense that they are some of the key topics in front-end dev and answers to those questions can be verified.</p> <p>Open ended questions, on the other hand, are harder to answer because the purpose of the question may not be easily verifiable e.g., </p> <ul><li>How long would you normally spend on solving a problem?</li><li>Do you subscribe to Web Feeds? Which ones?</li></ul></div>

• Annotation
• Note