Comments

Answers

0

I'd go with more generalised questions to gauge the candicate's problem-solving skills. Technical stuff questions should however include basic Windows stuff like 8.3 versus long filenames, permissions, users and groups. Find out if they know what a domain is and so on.

I like to know what research they have done about the job they're going for, so you'd want to know which section of MSDN they'd been looking at, whether they knew about this site, maybe Symantec Connect, InstallSite and so on.

On a forum-usage note, I wasn't sure if opening a new 'Interview Questions' thread is a good thing or not. On balance, though, I think it's valid, as the other thread got a bit unwieldy.

Basically I'd say something like MCDST or the newer certifications for Windows 7 are a good start. If you can get your hands on Testkings of them, they might give you some good ideas. The questions in there might be a bit too specific and Microsoft minded, but it's all about basic problem solving on an end user OS.

I think it might be a good idea for you to think back when *you* first started packaging and what you skills were at that point. That might be a good starting point for determining questions.

I think that it would be a good idea to see what they know about the equipment and software that is in your environment. Like how familiar are they with the OS(s) that you have in place? Not that it's a big deal but what do they know about security settings and issues? Have they been part of an effort to create a standardized core image? What do they know about Active Directory if anything? Do they have any scripting or programming experience?