By: TomLiotta

TomLiotta — Sat, 24 Nov 2012 05:35:50 +0000

Third try for this comment…

More info is needed. There are no correct answers yet. Besides, we shouldn’t post direct answers to questions used in interviews. That wouldn’t make us popular with our employers.
For #1, what’s available to work with? Is the SQL Dev Kit installed, or should it be done natively? What system elements are allowed to be changed? Database? Work management? Authorities? And what has previously been done, i.e., how is the program currently structured? (Is it currently RPGIII?)
For #2, the question is incorrect. Programs don’t have LDAs; jobs have LDAs. Is the intent of the question that a program should access the LDA of a different job? What is the OS version? (Best methods changed at V5R4.) Are the jobs concurrent? Does ‘access’ mean read or write?
Don’t hesitate to ask clarifying questions. No project has everything answered at the start.
One big problem with interview questions is that you need to grasp quickly what the interviewer is looking for in ‘this’ specific interview. Is direct technical knowledge a higher priority than the methodology used in approaching and resolving a problem? Responding appropriately can be critical. That requires noting details of the interviewer. Is the interview conducted by an HR person simply following a script? Or is it done by a potential technical manager and/or coworkers?
A few seconds spent at the beginning demonstrating personal interest in the interviewer can go a long way towards setting the tone. Never give up the right to interview the company just as much as you are being interviewed.
Tom

By: TomLiotta

TomLiotta — Thu, 22 Nov 2012 22:23:15 +0000

I’ve posted twice before against this question, but nothing has shown up for a couple hours or so. Sometimes it just takes a while. — Tom

Comments on: Interview Question

By: TomLiotta

By: TomLiotta