You can ask anything that the government allows you to ask, which is not
much really.
So I would ask the process of debugging, ask them about the toughest bug
they found and the process they used to fix it.
Ask them about the biggest mistake they made while on customer location and
how they dealt with it. The process is what's important not the details.
Most importantly, relax it's just a conversation.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Michael Schutte
Sent: Friday, August 26, 2016 5:54 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Conducting interviews
I'm a bit nervous. Today was supposed to be me attending an interview not
leading it.
But here we are. Time for me to break out of my shell.
Does anyone have any tips or things I should be asking? We are interviewing
a consultant for RPGLE position.
Would it be appropriate to ask them to find a bug in a 20 line procedure?
We haven't had much success lately with people that can debug issues. This
to me is a biggie. This particular issue I expect someone to be able to
find just looking at the code. I discovered it yesterday going to have fixed
today. I just thought this would give me some insight on the person problem
solving ability.
Sent from my iPhone
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
