Interview Questions

[Broken_Arrow]

---

USar wrote:
Broken Arrow, The list of questions you mentioned are definitely useful for the initial screening over the phone.

---

Glad to help!  I feel your pain. You have to walk a line between not alienating a perfectly good candidate with questions that are too specific, and not hiring a poser.

[pachook]

Also a nice "technique" would be to ask the questions from CLAD exam (a sample exam available on ni.com).

In my company it happend once - that a candidate claimed to know and work with LV, but when he had to explained one of the examples with for loop he failed - ( I belive he even had difficulties with naming that structure). 

Of course another situation is when you are looking someone, who doesnt have LV experiance, but then I think some "algorithmic" question would do.

[James_W]

The one I got in my interview a few years ago, was "This is the problem... how would you start to solve it using labview" I was given a whiteboard to draw on and a pen, if you can't work in LabVIEW away from the desk and describe which functions/structures you would use to solve a simple problem, you won't pass the CLAD either.

Giving them no code can be just as interesting as giving them code if you ask them to draw the BD on the board. Especially if you ask for the architecture, FP and reasons for chosing it.

- I've never seen "code" in an Interview yet, but I have a full time programming job.

James

[RobCole]

Interesting that all the questions focus on LabVIEW itself.

I got the job I have now because I asked the interviewers what was being used for source control (it's a team environment) and how they maintained documentation and code separation for team work.

Methodology for working with code is important. I would always add questions around these areas (I've been bitten too many times with lost code or hard to understand un-documented code).

     Rob