4 ms·

I can't speak for the particular interviewer at hand, but when I was interviewing people with whiteboard questions, I was interested not in the result, but in t

I can't speak for the particular interviewer at hand, but when I was interviewing people with whiteboard questions, I was interested not in the result, but in the way they think and approach the solution. So, if I were you in that particular situation, I'd start with simply laying out how do I think CSS rules will work out for the problem at hand, maybe used a marker to draw a simple style inheritance diagram for the particular DOM tree, etc., and would just turn the whole thing into a conversation. If the interviewer would demand exact solution for the problem on the whiteboard, then probably it's time to part your ways and go to the interview with another company.

reeses 13y ago
Thisity this. You're not going to find out in six hours if you're willing to marry someone, but you may find out that they leave their dirty underwear on the floor, never wash dishes, have sex with goats, and don't think fart jokes are funny. When they're standing there apparently thinking, I want them talking. "What's going on?" "Well, I can't remember the exact method name for this..." "Eh, make one up that sounds close enough." Then, if we have time, we talk about implementing MagicBeanFactory#dwim, but that's usually after my anti-pep speech of,"These are the things that may or may not piss you off about working here..."