Click here to Skip to main content
15,907,183 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
SeattleC++12-Aug-15 10:16
SeattleC++12-Aug-15 10:16 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Gary Wheeler11-Aug-15 6:47
Gary Wheeler11-Aug-15 6:47 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Slacker00711-Aug-15 7:05
professionalSlacker00711-Aug-15 7:05 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Gary Wheeler11-Aug-15 7:08
Gary Wheeler11-Aug-15 7:08 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
VC Sekhar Parepalli11-Aug-15 7:19
VC Sekhar Parepalli11-Aug-15 7:19 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
jschell11-Aug-15 9:32
jschell11-Aug-15 9:32 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
enhzflep12-Aug-15 5:26
enhzflep12-Aug-15 5:26 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Kirk 1038982112-Aug-15 5:56
Kirk 1038982112-Aug-15 5:56 
Gary Wheeler wrote:
If any interviewer were to ask me a question like that I would walk.


I interview people all of the time.
I ask questions like these at every interview.
The purpose is NOT EVER one true answer. It is about analyzing the person for their response.
Can they solve HUGE problems with lots of unknowns.
How do they approach it, how do they process it, and break it down.
Finally, how do they respond when they hear the problem.

There is no one right answer. In fact, I had a PhD once who belted out the approach to my top 3 questions. Completely nailing them. So I asked a question which is nearly impossible to know the answer to (what happens to a brownie, when pushed out a port of the space shuttle, into space. So that it is going from an atmosphere condition of inside the space shuttle, to outside into space. Describe everything you can think of. Does it explode, implode, etc.)

This is where it is interesting. He completely wigged out. He became physically agitated, he did not know the answer, and it really bothered him. But his response showed me that he may have some social issues. He is used to always being right, and is usually the smartest guy in the room.

The point is, that it was a fun game when he knew the answer, and it was stressful when he did not.

I want the guy who thinks it is a fun game when he does not know the answer, and plays with the question. Turns it around. Asks it differently. States a bunch of assumptions, and then starts developing insights as to what will/should happen and what to look for, what you could test.

I don't really want the answer. There is no ONE right answer. There is no ONE right approach.

There is simply the concept that MOST software is about building the unknown. And if you don't have the skills, to quickly start mapping that unknown to known, and what questions to ask, and to ENJOY the process. You are going to fail. Very rarely do my clients come to me and say "I need you to add 2 integers together and output the result". They ask for things like "We need to automate the filling in of these various forms with data from up to X different sources, and we need it to be correct. I have PEOPLE who do this today, but the computer would be so much faster." (Except that people can think, and programs have a tough time doing what people do). (BTW, in this case, we used 2 monitors and wrote a drag-n-drop interface that updated the other program. The problem was way too "humanistic". But a well-intentioned PhD could have spent years trying to write the system, which would have had to been reviewed by a human anyways).

BTW, if you have a better way to find people who are comfortable with complexity, and have the ability to express how they approach it, given problems that they have never heard of, and you know that your process works in general (nothing is perfect). I AM ALL EARS? (or eyes, since I will be reading it).

As hiring managers, we are trying to find skills. Not what people tell us, but what they truly have.
We need to know our confidence in those skill levels. And we cannot just trust what they tell us. Sometimes 10 years of C++ is really the same 1 year of C++ simply 10 years in row!

HTH
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
SeattleC++12-Aug-15 10:24
SeattleC++12-Aug-15 10:24 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Gary Wheeler13-Aug-15 1:27
Gary Wheeler13-Aug-15 1:27 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
R. Giskard Reventlov11-Aug-15 5:54
R. Giskard Reventlov11-Aug-15 5:54 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
OriginalGriff11-Aug-15 6:09
mveOriginalGriff11-Aug-15 6:09 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Munchies_Matt11-Aug-15 6:40
Munchies_Matt11-Aug-15 6:40 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
R. Giskard Reventlov11-Aug-15 6:46
R. Giskard Reventlov11-Aug-15 6:46 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Munchies_Matt11-Aug-15 6:47
Munchies_Matt11-Aug-15 6:47 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Member 1070767711-Aug-15 22:22
Member 1070767711-Aug-15 22:22 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
jschell11-Aug-15 9:40
jschell11-Aug-15 9:40 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Roger Wright12-Aug-15 17:07
professionalRoger Wright12-Aug-15 17:07 
GeneralRe: Testing a Potential New Hire's Troubleshooting Skills During The Interview Process Pin
Slacker00712-Aug-15 22:05
professionalSlacker00712-Aug-15 22:05 
GeneralBoomeranging Telescopic and Kaleidoscopic Phrase Maze of the Day ("Dumb") Pin
B. Clay Shannon11-Aug-15 4:32
professionalB. Clay Shannon11-Aug-15 4:32 
GeneralRe: Boomeranging Telescopic and Kaleidoscopic Phrase Maze of the Day ("Dumb") Pin
Cornelius Henning11-Aug-15 5:14
professionalCornelius Henning11-Aug-15 5:14 
GeneralJolly Sailor Bold Pin
Afzaal Ahmad Zeeshan11-Aug-15 4:24
professionalAfzaal Ahmad Zeeshan11-Aug-15 4:24 
GeneralRe: Jolly Sailor Bold Pin
Jalapeno Bob11-Aug-15 4:43
professionalJalapeno Bob11-Aug-15 4:43 
GeneralRe: Jolly Sailor Bold Pin
Richard MacCutchan11-Aug-15 5:47
mveRichard MacCutchan11-Aug-15 5:47 
GeneralRe: Jolly Sailor Bold Pin
Afzaal Ahmad Zeeshan11-Aug-15 7:38
professionalAfzaal Ahmad Zeeshan11-Aug-15 7:38 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.