On Thu, 2007-10-18 at 22:04 -0700, Vitaliy wrote:
> What do you think of those? In your opinion, what skills are essential for 
> embedded developers? What sets them apart from desktop app programmers?

I can't comment too well on what questions to ask, the embedded world is
something completely different to almost anyone you ask. Some think
knowing ASM is paramount, others think you shouldn't need to read the
device datasheet...

However, I just want to mention that relying only on "correct answers"
is not a good idea IMHO. Don't get me wrong, I think it's VERY
worthwhile to "test" people during interviews, it's what I had to do to
get my current job.

That said, be aware that there are LOTS of people that are just great at
tests, but when you get them into real situations they don't work out.
Also, there are lots of people who AREN'T good at the fake world of a
"test", yet excel in the real world.

Also, I wouldn't concentrate on what exactly the applicant knows. Who
cares if they get a brain freeze and get one of the questions wrong.
What I'd be more focused on is how the applicant DEALS with not knowing,
or getting a question wrong. 

I've heard of applicants getting ANGRY (i.e. yelling and fists pounding
on tables) with the interviewer, claiming the test "wasn't fair". I've
heard of applicants who, even when presented clearly WHY their answer is
wrong, will refuse to accept they might be wrong and state that their
answer is correct and it's the interviewer that's wrong.

In fact, a technique I've seen which I feel is very constructive is to
put progressively tougher questions to the applicant, incrementing until
you ARRIVE at a question they just don't get right. Anybody can learn
what you need them to know, the willingness TO learn is what's important
IMHO.

TTYL

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist