On 11-04-24 10:36 AM, Akhthar Parvez K wrote:
Well, what I actually meant was not diverting it baselessly. One could actually start with
"I don't think I actually know what you asked, but
if<now_divert_to_something_relevant_you_know>". It's just to let the interviewer
know that you know about something related eventhough you don't know the answer for the exact
question. It's anything but an attempt to fool.:-) After all, what the interviewer wants to
know is if the interviewee is knowledgable enough and it's not always necessary to have that
happened by an answer he expected.
I still think I have to disagree. Sometimes interviewers ask purposely
obscure questions not to see if you know the answer but to see what
you'd do if you came across a problem you couldn't immediately solve
when on the job. The best response is to state you don't know and then
tell what you'd do:
1. Inform your immediate supervisor about the problem.
2. Start searching the company's code base and asking the old hands
about it.
3. Search the web.
4. Ask the perlmonks <http://perlmonks.org/>
5. (Anything you can think of.)
--
Just my 0.00000002 million dollars worth,
Shawn
Confusion is the first step of understanding.
Programming is as much about organization and communication
as it is about coding.
The secret to great software: Fail early & often.
Eliminate software piracy: use only FLOSS.
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
