[thelist] Re: interview questions

Erika Meyer emeyer at lclark.edu
Tue Aug 21 18:56:48 CDT 2001

It's good if an interview becomes a dialogue more than a Q&A session 
with them doing all the asking and you doing all the answering.

In response to this question, I'd ask first how they would present 
the design to me... on paper? As a Photoshop mockup?  And I'd ask any 
other background questions I have about their development process.

Then I'd answer the questions by examining these issues, off the top 
of my head, and in no particular order...

Part One (assuming all the IA and mockups have already been done by 
other parties):

1.  How diverse is the audience, their resolution, their browsers, 
their monitor size, their bandwidth?

2.  Keeping the answers to number 1 in mind, should the design be 
solid or liquid?  How well does the mockup work as a liquid design?

3. What choices will we make re: accessibility?

4. Related to #3: How important is visual design consistency across browsers?

5.  Which parts of the site incorporate dynamic content?  Which parts 
of the site change regularly and how do they change?  Who does the 
maintenance and how?

6.  Which parts of the site are consistent across several pages and 
could benefit from being put into includes?

7. Which parts of the site should be text, which should be graphics?

Part Two:

Regarding teamwork, I would like to see the team get together to 
assess the various design issues, and come up with a plan for 
implementing the design including milestone dates for 
completion/coordination of various steps.

Each team member would be responsible for a particular area of the 
site, & hopefully each would be responsible for an area within 
his/her area of interest and expertise.

We would let each other know ASAP if we are unable to meet milestone 
dates for any reason.

Communication would be consistent and regular, enabling us to 
troubleshoot problems together as needed, and to modify goals or 
process structure as necessary.

  One of us would record progress and act as a liaison with the supervisor.

--- I don't know if these are "good" answers... but they are mine.

I think sometimes the interviewer is looking for something specific, 
and the best we can do is give our own educated, thoughtful ideas. 
If it's what they like to hear, great.  If not, you probably are 
better off working somewhere else.


>And also
>"Talk me through the methodology and key issues you'd
>when coding designs into HTML"
>"How would you work with other team members to achieve
>high quality result while aiming to complete the work
>quickly as possible"
>What *are* the good answers to these questions? How
>would *you* answer them?


More information about the thelist mailing list