Re: Conducting interviews

Geez, I really need to proof read better.

On Fri, Aug 26, 2016 at 4:57 PM, Michael Schutte <mschutte369@xxxxxxxxx>
wrote:

I will take note of all these suggestions. They seem they can be very
beneficial. I made it through them :-). It was a little nerve racking,
especially since I've only been on the other end twice in my life, well for
jobs that really mattered.

I was aware of an interview at 9 and was caught off guard of the interview
at 8. I was made aware that the original interview wouldn't be in at 7 AM.
I made it to the interview just in time... my daughter recently broke her
leg (same daughter that has beat cancer). So I was waiting for the baby
sitters to make it. Luckily they did. So I didn't have time to prep
myself or read over this consultants resume. But to me most resumes read
the same. I knew what he was there for.

I think did pretty good. Maybe made some mistakes. Since I didn't have
time to prepare that sample code with an error, I started off asking their
method to finding issues. Such as a record having the wrong value in a
field. They both gave answers that I expected about pulling journals. They
told me about their experience with warehouse management, I shared my
background and experience. Since we've moved to coding more procedures,
I've asked their ability. One was more versed than the other. One was
more familiar with RPGIII but a quick learner while the other worked with
III, IV and free.

In all I think I received enough information to make the right decision.

At point, I had to stop myself from laughing. I've been watching Friends
reruns. The episode where Chandler interviews for a new job... the joke
about "duties" and what you "do do". I started explaining what we do and
said "what we do do.". Stopped and reworded it. I just couldn't help it.
Juvenile language. HAHA.

In case you were curious as to the program error.

D InvalidUOM S n inz(*off)

/Free
Exec SQL Open C5;
Exec SQL Fetch C5 Into :LineNbr, :ItemCode, :QtyToShip,
:Storer, :Suffix;
DoW SQLCODE >= 0 And SQLCODE <> 100;
MessageId = *Blanks;
SCR_ERRMSG = *Blanks;

If ValidateDivisibility(Storer:Suffix:ItemCode:QtyToShip:

OrderType:MessageId:MessageData);

If InvalidUOM = *Off;
If OrderLineInductsToConveyor(p_OrderNbr:LineNbr:MessageId:

MessageData:QtyToShip:p_ConveyorId)

Or MessageId = Uom1PickFrontRequired
Or MessageId = Uom2PickFrontRequired
Or MessageId = Uom3PickFrontRequired;
-- omitted due to not important
EndIf;
EndIf;
Else;
InvalidUOM = *On;
SCR_ERRMSG = 'Qty not divisible by UOM';
ReturnMsgId = QuantityNotDivisibleByUom;
EndIf;
Exec SQL Fetch C5 Into :LineNbr, :ItemCode, :QtyToShip,
:Storer, :Suffix;
EndDo;
Exec SQL Close C5;
/End-Free




On Fri, Aug 26, 2016 at 1:58 PM, Tommy Holden <Tommy.Holden@xxxxxxxxx>
wrote:

The company being willing to invest in their IT personnel is one of the
reasons I came to my current job and it has been a great benefit to me as
well as the company!



Thanks,
Tommy Holden

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Duane Scott
Sent: Friday, August 26, 2016 12:51 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Conducting interviews

I'll have to remember these questions and retro-fit them to the
organization I'm applying. If their answers are that they don't believe in
assisting their employees in obtaining these, then I'm not sure the
organization is one to aspire to.

duane

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Friday, August 26, 2016 1:10 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Conducting interviews

I love these questions. They certainly aren't going to do ALL of that
but the better not do NONE of that. It really is telling if they invest in
themselves or not. If they do not why would you invest in them??


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 8/26/2016 9:02 AM, Glenn Gundermann wrote:

Hi Michael,

I haven't read anyone else's replies so this may be repetitive.

I feel it is important for a developer to keep current. I ask them:
- What user group(s) they belong to.
- What speakers/topics they have attended to in the last year.
- Can they list all the great conferences, e.g. COMMON, IBM
conferences, RPG DB2 Summit, TUG, etc.
- When and what was the last conference they attended.
- What user forums do they follow/participate in.
- What technical subscriptions do they read.
- Can they name some of the popular technical authors.
- What technical authors do they like to follow.
- What courses have they taken.

Once I get the feel of this, I can go into the technical evaluation:
ILE, DB2, SQL, RPG. etc. I've had interviewees tell me they have
learned something by the time they leave the interview.



Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Cell: (416) 317-3144


On 26 August 2016 at 06:54, Michael Schutte <mschutte369@xxxxxxxxx>

wrote:

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.

--
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.

________________________________
________________________________
CONFIDENTIALITY NOTICE: This electronic message transmission is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. If you have received this transmission, but are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution or use of the contents of this information is strictly
prohibited. If you have received this e-mail in error, please contact NALC
Health Benefit Plan at 703-729-4677 and delete and destroy the original
message and all copies.




--
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.
--
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.