Two Front End Development Interview Questions No One Has Been Getting Recently + One I’m Afraid to Even Ask

by Rob Larsen

Yes, I’m still helping out with screening candidates. I haven’t yet interviewed someone to replace me, but there’s still a week to go.

Anyway, we’ve had a couple of technical questions that candidates universally failed to answer. Why share them here? For starters I just want to know if we’re crazy to expect people to know these. I also like the idea of a kind of “easter egg” for candidates. If someone does enough research to find my blog and read this post, they’ve shown me something, even if it’s not the answer to one of the questions posed below.

The two that have surprisingly turned into stumpers (at least for the last five or six folks I’ve interviewed)

  1. What is hasLayout?
  2. What’s the significance of setting the body text to .625em?

And the bonus question that I want to ask, but don’t, because it’s kind of goofy to say out loud

  1. What’s “The Mark of the Web?”

Answers after the jump.

What is hasLayout?
hasLayout is a proprietary, read-only Microsoft property that has occasionally serious effect on the way that elements render, flow and react to events. Read more about it here.

I ask about it because it’s one of the first things I look at to when I’ve got a particularly strange IE6 bug.

At this point I don’t even need a really good answer for this one. I’d settle for vague recognition.

If they do answer it correctly, the natural follow-up is “name a way force an element to gain layout”

What’s the significance of setting the body text to .625em?
Simple answer- it sets the default font-size to 10px, which makes all kinds of calculations easier to make.

This very site uses the technique coupled with em-based measurements to make a site that scales nicely. I ask this one because the technique itself is pretty cool and simple knowledge of it (even without the experience of having used it) shows that the person has at least done some reading.
What’s “The Mark of the Web?”
<!– saved from url=(0014)about:internet –>
That’s “The Mark of the Web.” :)

Why is important? Setting the MOTW allows you to debug pages on your local machine in Internet Explorer without dealing with the dreaded “To help protect your security, Internet Explorer has restricted this webpage from showing active content” security bar.

Clearly very handy.

Read more about the MOTW here.


Personally, I’m surprised these have been as tough as they’ve been. Anyone else got any surprising stumpers?

4 Responses to “Two Front End Development Interview Questions No One Has Been Getting Recently + One I’m Afraid to Even Ask”

  1. Lance Jonn Romanoff Says:

    The first two seem reasonable enough. Obviously you didn’t interview me to replace you. The third one is actually new to me though as I don’t do a lot of debugging of local files. Even knowing about it now I doubt it would get used very much.

  2. Rob Larsen Says:

    I just sent you an email.

    As for the MOTW, I use it when I’m doing JavaScript proof of concept stuff, mostly. It comes in really handy there.

  3. really? Says:

    Let’s pick 2 completely random, farthest left corner, obscure tagging questions to ask our next FED candidates. That’s spending your time wisely showing off what YOU know (only by choice selection) and what 99 out of a 100 FED’s won’t know off the top of their head.

    Good use of everybody’s time.

  4. Rob Larsen Says:

    Those are random? The concept of layout in IE is a huge help when debugging cross browser CSS issues and, at the time this was written, that em measurement trick was quite popular. It’s since fallen out of favor, but it was useful at the time.

    Also, I WANT to hire the 1/100 and not the 99/100, so this line of questioning was obviously on the right track.

Leave a Reply