Re: perl interview questions

[Doug]

2011/4/21 Jyoti :
> Hello All,
>
> Please give me any link or any tutorial which will be helpful for
> preparation of PERL interview.
>

There are lots. But, doesn't google give you any info you want?

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Alan Haggai Alavi]

Hello Jyoti,


Please give me any link or any tutorial which will be helpful for
preparation of PERL interview.


Please read `perldoc perlfaq` (http://perldoc.perl.org/perlfaq.html). It
is a collection of frequently asked questions which will certainly help
you at an interview.

Regards,
Alan Haggai Alavi.
--
The difference makes the difference

--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Shlomi Fish]

Hi Jyoti,

On Thursday 21 Apr 2011 07:49:00 Jyoti wrote:
> Hello All,
> 
> Please give me any link or any tutorial which will be helpful for
> preparation of PERL interview.
> 

First of all, see:

* http://perl-begin.org/learn/Perl-perl-but-not-PERL/

(It's either "Perl" or "perl", but never "PERL". It is a ).

Then see the other resources at http://perl-begin.org/ . There are some 
tutorials at http://perl-begin.org/tutorials/ and some books (some of them 
online) here: http://perl-begin.org/books/ . The most recommended book, if you 
already know a different programming language is probably "Modern Perl" ( 
http://perl-begin.org/books/#modern-perl ) - otherwise, you should look at 
Beginning Perl ( http://perl-begin.org/books/#beginning-perl ) first. Both are 
available online for free download.

Regards,

Shlomi Fish

-- 
-
Shlomi Fish   http://www.shlomifish.org/
List of Portability Libraries - http://shlom.in/port-libs

Chuck Norris does not code; when he sits at a computer, it just does whatever
he wants. (By: Kattana.)

Please reply to list if it's a mailing list post - http://shlom.in/reply .

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Luis Roca]

On Apr 21, 12:49 am, jyoti.bans...@gmail.com (Jyoti) wrote:
> Hello All,
>
> Please give me any link or any tutorial which will be helpful for
> preparation of PERL interview.

Do you have a job description of the position you're interviewing for?
Is this a web development position? Is this a systems administrative
job? It's difficult to give you prep questions for an interview
without even knowing what the job title is you are interviewing for or
what kind of work this company/companies do. ;-)

However for some general topics chromatic wrote a list of expertise
managers -should- be asking candidates to have. It's worth a look:

http://www.modernperlbooks.com/mt/2011/01/how-to-identify-a-good-perl-programmer.html

Again, if you provided some more information about the position (the
company's job description) I'm sure people can give you more specific
help – good luck!

Luis


--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Brandon McCaig]

On Thu, Apr 21, 2011 at 9:07 AM, Luis Roca 
wrote:
> Again, if you provided some more information about the position
> (the company's job description) I'm sure people can give you
> more specific help – good luck!

Wouldn't it be nice though if the people conducting interviews
already knew enough about what they should ask and how to
interpret it...? :-X

Pass the responsibility on to the people that will have to live
with the hire. :P


-- 
Brandon McCaig  
V zrna gur orfg jvgu jung V fnl. Vg qbrfa'g nyjnlf fbhaq gung jnl.
Castopulence Software  

--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Owen]

> On Thu, Apr 21, 2011 at 9:07 AM, Luis Roca 
> wrote:
>> Again, if you provided some more information about the position
>> (the company's job description) I'm sure people can give you
>> more specific help – good luck!
>
> Wouldn't it be nice though if the people conducting interviews
> already knew enough about what they should ask and how to
> interpret it...? :-X
>
> Pass the responsibility on to the people that will have to live
> with the hire. :P




Did not this thread start with a problem about 20 cows?

It seemed to be a general "IQ" type of question and any answer would
do as long as you could explain it.

In my mind the simplest answer would have been to randomly split the
herd in two. The probability of each group of ten meeting the criteria
would be almost the same?


Owen





-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Akhthar Parvez K]

Hi Jyoti,

On Thursday 21 Apr 2011, Jyoti wrote:
> Please give me any link or any tutorial which will be helpful for
> preparation of PERL interview.
> 

I don't honestly think someone would write an article or tutorial about 
"preparing for a Perl interview". That should actually split into two: Learning 
Perl and Preparing for an interview.

And here's some free advice and feel free to take it if you like :-D

#1 - Never learn for an interview; but learn for the job.
#2 - Apply for an interview only if you're fit enough. - If you don't think 
your skill set don't match with the requirements of the company, just don't 
apply. You're thus doing a favor to yourself and everyone else.
#3 - Once you apply, just be ready to face an interview any time.
#4 - Trust your abilities and be confident - This is the most important part 
and would let you handle the interview in the best possible way.
#5 - Never give a wrong answer - If at all you receive a question that you 
don't know, do not panic, just be smart and divert the question so you can 
answer what you know. 
#6 - Please your interviewer with well explained responses. 

Hope that helps!

-- 
Regards,
Akhthar Parvez K
http://www.sysadminguide.com/
UNIX is basically a simple operating system, but you have to be a genius to 
understand the simplicity - Dennis Ritchie

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Shawn H Corey]

On 11-04-24 09:48 AM, Akhthar Parvez K wrote:

#5 - Never give a wrong answer - If at all you receive a question that you 
don't know, do not panic, just be smart and divert the question so you can 
answer what you know.


If you don't know the answer, say so.  Then state how you would go about 
finding the answer.  Do not reply on clever tricks in an attempt to fool 
your interviewer.



--
Just my 0.0002 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/

Re: perl interview questions

[Akhthar Parvez K]

On Sunday 24 Apr 2011, Shawn H Corey wrote:
> On 11-04-24 09:48 AM, Akhthar Parvez K wrote:
> > #5 - Never give a wrong answer - If at all you receive a question that you 
> > don't know, do not panic, just be smart and divert the question so you can 
> > answer what you know.
> 
> If you don't know the answer, say so.  Then state how you would go about 
> finding the answer.  Do not reply on clever tricks in an attempt to fool 
> your interviewer.
> 

I'm sure that I wouldn't have received such a response had I explained it a bit 
more, but then that's my fault as I made tips so short that it didn't convey 
the message clearly.

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

-- 
Regards,
Akhthar Parvez K
http://www.sysadminguide.com/
UNIX is basically a simple operating system, but you have to be a genius to 
understand the simplicity - Dennis Ritchie

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Shlomi Fish]

On Sunday 24 Apr 2011 17:13:18 Shawn H Corey wrote:
> On 11-04-24 09:48 AM, Akhthar Parvez K wrote:
> > #5 - Never give a wrong answer - If at all you receive a question that
> > you don't know, do not panic, just be smart and divert the question so
> > you can answer what you know.
> 
> If you don't know the answer, say so.  Then state how you would go about
> finding the answer.  Do not reply on clever tricks in an attempt to fool
> your interviewer.

Very good advice! 

I recall an interview I did for the IBM Haifa R&D lab, where I was asked a 
question, which I didn't immediately know the answer to, but instead of saying 
"let me think about it" I "brainstormed" a little with the interviewers until 
I reached the right answer. Maybe they sensed it, and I didn't get the job 
even though I did well on the other tests. (Though who knows - back then there 
was still a lot of recession and they had many candidates.). 

I'll reply directly to what Akhthar said with more advice from my experience.

Regards,

Shlomi Fish

-- 
-
Shlomi Fish   http://www.shlomifish.org/
Escape from GNU Autohell - http://www.shlomifish.org/open-
source/anti/autohell/

 sub id { my $self = shift; $json_parser_for{ $self }
->decode($json_for{ $self })->{id} } # Inside-out JSON-notated objects

Please reply to list if it's a mailing list post - http://shlom.in/reply .

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Shlomi Fish]

On Sunday 24 Apr 2011 16:48:10 Akhthar Parvez K wrote:
> Hi Jyoti,
> 
> On Thursday 21 Apr 2011, Jyoti wrote:
> > Please give me any link or any tutorial which will be helpful for
> > preparation of PERL interview.
> 
> I don't honestly think someone would write an article or tutorial about
> "preparing for a Perl interview". That should actually split into two:
> Learning Perl and Preparing for an interview.
> 
> And here's some free advice and feel free to take it if you like :-D
> 
> #1 - Never learn for an interview; but learn for the job.
> #2 - Apply for an interview only if you're fit enough. - If you don't think
> your skill set don't match with the requirements of the company, just
> don't apply. You're thus doing a favor to yourself and everyone else. #3 -
> Once you apply, just be ready to face an interview any time.
> #4 - Trust your abilities and be confident - This is the most important
> part and would let you handle the interview in the best possible way. #5 -
> Never give a wrong answer - If at all you receive a question that you
> don't know, do not panic, just be smart and divert the question so you can
> answer what you know. #6 - Please your interviewer with well explained
> responses.
> 

Some more advice from my experience:

1. Be yourself. Be honest. If you don't like 
Java/Perl/Python/COBOL/Lisp/C/C++/whatever, say so. Google hires many Python 
programmers to write Java, and even many Perl programmers to write Python or 
Java or whatever (yes, some people code even Python against their 
preferences). If you lie, you will eventually get caught, possibly after being 
hired and then fired immediately.

2. Seek good workplaces. A lot of workplaces there are crap. It's hard to know 
how many, but see http://blog.red-bean.com/sussman/?p=79 (= Version Control 
and "the 80%"). To paraphrase on what Tolstoy said "All good workplaces are 
the same. Every bad workplace is bad in its own way.". Often times, I realised 
I knew things much better in most respects than my superiors based on what I 
read in various software management and software development in general on the 
Web. It's hard the way a workplace is managed as an underling (at least if 
you're not being very assertive.) and it is a good idea to make sure that your 
boss (your CTO/etc.) have heard of http://www.joelonsoftware.com/ , knows what 
Extreme Programming is about mostly, understands test-driven development, has 
read "The Cathedral and the Bazaar", does not require more than 40 hours/week 
weekday (otherwise you *will* be burned out), etc. He does not have to agree 
to everything every software management "guru" out there says (which is often 
contradictory), but he has to be able to explain why he deviates from it.

Whether he prefers to use Perl or Python or Java or C or whatever (some of 
which are only useful in completely different contexts) is less critical.

3. Don't give up. Finding a job is hard now in the post-bubble world. 
Employers are very picky and careful, and 
http://www.joelonsoftware.com/articles/GuerrillaInterviewing3.html says that 
if you have a little doubt, it means no hire, which some employers may 
practise deliberately or subconsciously.

It can sometimes take a lot of time to find a good job after you left the 
original one (for whatever reason), but you should be able to find one, 
because it seems that in IT centres, all fields nowadays are desperately 
looking for clueful programmers. If you're good, you will likely find a job 
soon enough.

4. Whether working or not, always try to improve your existing skills (which 
you consider important enough and not passé), become experienced in more 
technologies (what I call "horizontal learning" because it's impossible to 
100% master a complete fields such as RoR/CPAN/Python/etc. and you should not 
wait to know everything to know about it to learn more stuff), and also 
improve your spoken and written English (and your native languages), because 
it is one of the most important skills that any person can possess, and 
naturally, every programmer.

---

OK, these are the things off the top of my head. 

Regards,

Shlomi Fish

-- 
-
Shlomi Fish   http://www.shlomifish.org/
Stop Using MSIE - http://www.shlomifish.org/no-ie/

Ran Eilam To Shlomi Fish: so what are you working on? Working on a new wiki
about unit testing fortunes in freecell?

Please reply to list if it's a mailing list post - http://shlom.in/reply .

--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Shawn H Corey]

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

5.  (Anything you can think of.)


--
Just my 0.0002 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/

Re: perl interview questions

[Shlomi Fish]

On Sunday 24 Apr 2011 21:01:57 Shawn H Corey wrote:
> 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". 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  
> 
> 5.  (Anything you can think of.)

I recall a job for a security company that developed an Intrusion detection 
system (IDS) or Intrusion Prevention System (IPS) - don't remember which one - 
as a small embedded box running vxWorks [vxWorks] and they asked me "How would 
you design an IDS?" I told them that I didn't know and they told me "We'll 
help you. Do you have any ideas?" I had some leads, but I ended up saying I 
don't know, and couldn't really get anywhere. Maybe they were looking for 
brighter or more experienced people then me, but I naturally didn't get the 
job, nor was I very impressed of their hiring and interviewing philosophy.

Most good workplaces I've been to asked me to write a piece of code (a bit 
tricky, but not very time consuming) in their language of choice or less often 
"my favourite language", and I do better there because I'm a capable coder, 
and I think it's a good idea to actually instruct the candidate to write some 
code.

--

On a different note, another good idea is to not be too prepared. One of my 
online friends was offered to interview for Google, and he got prepared with 
studying a lot of deep and formal data structures and algortihms theory ("you 
need to know how to implement a QuickSort off-hand.") and when he came there, 
his technical questions were much less sophisticated than he thought they 
would. Some employers may view such a thing as a red flag, because a person is 
trying to seem to be more than he is by "cramming" for an interview. They 
usually don't expect you to be a software development 
superstar/virtuoso/rocket-scientist , and you should know better to assume 
they do (and if they do, you probably won't get the job by cramming.).

Regards,

-- Shlomi Fish

[vxWorks] - http://en.wikipedia.org/wiki/VxWorks - an embedded operating 
system by a company that was often referred to as "The Microsoft of the 
Embedded market", mostly POSIX compatible, but very different from most 
mainstream UNIX, a bit quirky, using a very old version of the GNU tools for 
development. Lost some popularity and hype in the embedded space due to 
competition from Linux, Embedded MS-Windows, the BSDs and similar solutions, 
but is still popular. I was told it's not really comparable to Linux, and they 
both have different use-cases.

-- 
-
Shlomi Fish   http://www.shlomifish.org/
http://www.shlomifish.org/humour/ways_to_do_it.html

Chuck Norris doesn't make mistakes. (Su-Shee) He corrects God. (Shlomi Fish)

Please reply to list if it's a mailing list post - http://shlom.in/reply .

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Akhthar Parvez K]

On Monday 25 Apr 2011, Shlomi Fish wrote:
> On Sunday 24 Apr 2011 21:01:57 Shawn H Corey wrote:
> > On 11-04-24 10:36 AM, Akhthar Parvez K wrote:
[ snip ]
> > 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  
> > 
> > 5.  (Anything you can think of.)
> 
> I recall a job for a security company that developed an Intrusion detection 
> system (IDS) or Intrusion Prevention System (IPS) - don't remember which one 
> - 
> as a small embedded box running vxWorks [vxWorks] and they asked me "How 
> would 
> you design an IDS?" I told them that I didn't know and they told me "We'll 
> help you. Do you have any ideas?" I had some leads, but I ended up saying I 
> don't know, and couldn't really get anywhere. Maybe they were looking for 
> brighter or more experienced people then me, but I naturally didn't get the 
> job, nor was I very impressed of their hiring and interviewing philosophy.

Actually I was talking about a situation like this, not the context Shawn 
mentioned. What Shawn mentioned was more of a "what would you do if you're 
faced with an issue that you couldn't fix on time" case. Let me demonstrate the 
one I mentioned with the following conversation:

Interviewer: How would you design an IDS?

Interviewee: I have never worked on IDS so far, hence don't have a clear idea 
about the designing of the same. However, I was part of a team that developed 
an Exploit Scanner/Detection tool for Linux machines. It was written in Perl 
and we used a couple of mechanisms such as signatures, regular expressions etc. 
to detect the exploits and setup a Hash design to store the scan results in the 
most appropriate manner. 

Interviewer: Ok, that's good. So as you said you don't have much idea about 
designing IDS, how would you proceed if you're assigned for that job?

Interviewee: First and foremost, I would talk to the experienced members in my 
team to get some valuable inputs and then read some books as well as search 
through the web for more details. In fact, I'll try wherever I think would help 
me to learn more about the same. I'm pretty sure I would be able to get it done 
as that has been case whenever I worked on something interesting.

Here, the interviewee is not fooling the interviewer and the latter would be 
generally happy to know the former has got some experience in something 
related. For the interviewee, he can still use the opportunity to impress the 
interviewer even if he doesn't know the particular answer.

> Most good workplaces I've been to asked me to write a piece of code (a bit 
> tricky, but not very time consuming) in their language of choice or less 
> often 
> "my favourite language", and I do better there because I'm a capable coder, 
> and I think it's a good idea to actually instruct the candidate to write some 
> code.

Yes, this is good if you're being interviewed for the post of a developer. But 
in some cases, it's not really necessary. Suppose if they understood your 
coding credibility already, they wouldn't really want to dig deep into 
programming. They would rather want to know something else, mostly related to 
planning, managerial or other non-technical aspects etc.

-- 
Regards,
Akhthar Parvez K
http://www.sysadminguide.com/
UNIX is basically a simple operating system, but you have to be a genius to 
understand the simplicity - Dennis Ritchie

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: perl interview questions

[Shlomi Fish]

On Monday 25 Apr 2011 18:07:51 Akhthar Parvez K wrote:
> On Monday 25 Apr 2011, Shlomi Fish wrote:
> > On Sunday 24 Apr 2011 21:01:57 Shawn H Corey wrote:
> > > On 11-04-24 10:36 AM, Akhthar Parvez K wrote:
> [ snip ]
> 
> > > 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  
> > > 
> > > 5.  (Anything you can think of.)
> > 
> > I recall a job for a security company that developed an Intrusion
> > detection system (IDS) or Intrusion Prevention System (IPS) - don't
> > remember which one - as a small embedded box running vxWorks [vxWorks]
> > and they asked me "How would you design an IDS?" I told them that I
> > didn't know and they told me "We'll help you. Do you have any ideas?" I
> > had some leads, but I ended up saying I don't know, and couldn't really
> > get anywhere. Maybe they were looking for brighter or more experienced
> > people then me, but I naturally didn't get the job, nor was I very
> > impressed of their hiring and interviewing philosophy.
> 
> Actually I was talking about a situation like this, not the context Shawn
> mentioned. What Shawn mentioned was more of a "what would you do if you're
> faced with an issue that you couldn't fix on time" case. Let me
> demonstrate the one I mentioned with the following conversation:
> 
> Interviewer: How would you design an IDS?
> 
> Interviewee: I have never worked on IDS so far, hence don't have a clear
> idea about the designing of the same. However, I was part of a team that
> developed an Exploit Scanner/Detection tool for Linux machines. It was
> written in Perl and we used a couple of mechanisms such as signatures,
> regular expressions etc. to detect the exploits and setup a Hash design to
> store the scan results in the most appropriate manner.
> 
> Interviewer: Ok, that's good. So as you said you don't have much idea about
> designing IDS, how would you proceed if you're assigned for that job?
> 
> Interviewee: First and foremost, I would talk to the experienced members in
> my team to get some valuable inputs and then read some books as well as
> search through the web for more details. In fact, I'll try wherever I
> think would help me to learn more about the same. I'm pretty sure I would
> be able to get it done as that has been case whenever I worked on
> something interesting.
> 
> Here, the interviewee is not fooling the interviewer and the latter would
> be generally happy to know the former has got some experience in something
> related. For the interviewee, he can still use the opportunity to impress
> the interviewer even if he doesn't know the particular answer.
> 

Good advice. I'll keep that in mind for next time, instead of saying "I don't 
know". Applied psychology at its best. (Though I think they were still not a 
good place to work for me.).

> > Most good workplaces I've been to asked me to write a piece of code (a
> > bit tricky, but not very time consuming) in their language of choice or
> > less often "my favourite language", and I do better there because I'm a
> > capable coder, and I think it's a good idea to actually instruct the
> > candidate to write some code.
> 
> Yes, this is good if you're being interviewed for the post of a developer.
> But in some cases, it's not really necessary. Suppose if they understood
> your coding credibility already, they wouldn't really want to dig deep
> into programming. They would rather want to know something else, mostly
> related to planning, managerial or other non-technical aspects etc.

Well, I think you should always ask a person to write some code, even if 
you're sure based on their open-source code (CPAN/etc.), their posts to 
technical mailing lists (such as beginners@perl.org, etc.) that they are very 
good programmers. This is because you can still see how he handles a task. I 
recall an interview for a company where the CTO there, who was and still is a 
very good friend, told me "In your favourite language, write a function that 
replaces the string '%FOO%' in a given string with the second argument." I 
asked if I could use Perl for that, and he said "Only if it's your favourite 
programming language!" and so I went to write that. He then said that the 
Python routine was a bit shorter and that many C and Java programmers he 
interviewed had natural problems with this due to their languages' 
limitations.

Naturally, he knew I knew Perl, but it still was a good mention of trust. And 
naturally, even if you're a Perl shop (or Ruby or Py

Re: Perl Interview Questions

[Chris Devers]

On Thu, 25 Aug 2005, praba har wrote:

>   I am working as perl-cgi programmer in a small company.  I got a 
> call from the big company for Perl developer post.  So I need perl 
> related interview point of view questions. Kindly help me for this 
> interview.

"Explain what a closure is and why you would use one."


 

-- 
Chris Devers

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

Re: Perl Interview Questions

[Ken Perl]

What the name of the big company?

On 8/25/05, Chris Devers <[EMAIL PROTECTED]> wrote:
> On Thu, 25 Aug 2005, praba har wrote:
> 
> >   I am working as perl-cgi programmer in a small company.  I got a
> > call from the big company for Perl developer post.  So I need perl
> > related interview point of view questions. Kindly help me for this
> > interview.
> 
> "Explain what a closure is and why you would use one."
> 
> 
> 
> 
> --
> Chris Devers
> 
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>  
> 
> 
>

--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

RE: Perl Interview Questions

[Dhanashri Bhate]

Hello,

pls don't mis-understand.

There are perl gurus in this list as well as pther beginners like me , and they 
will surely help, but first at least show that you have taken some effort to 
learn Perl!

If you say that you want a new job and someone should help you with the 
interview questions, nobody from the list will answer favorably! even if 
someone asks that i want to do this , how to i do it in Perl?  the answers 
would be, try something urself, show us some code and then we'll help you.

So, if you have internet access try reading first about perl, get perl 
installed on your machine try out some programs and then if you face 
difficulties post them here.

Best regards
Dhanashri

-> -Original Message-
-> From: praba har [mailto:[EMAIL PROTECTED]
-> Sent: Thursday, August 25, 2005 10:45 AM
-> To: beginners@perl.org
-> Subject: Perl Interview Questions
-> 
-> 
-> Dear All,
-> 
->   I am working as perl-cgi programmer in a small
-> company.  I got a call from the big company for
-> Perl developer post.  So I need perl related 
-> interview point of view questions. Kindly help me
-> for this interview.
-> 
-> regards
-> Prabahar
-> 
-> 
-> 
->  
-> 
->  
->  
-> 
-> Send a rakhi to your brother, buy gifts and win attractive 
-> prizes. Log on to http://in.promos.yahoo.com/rakhi/index.html
-> 
-> -- 
-> To unsubscribe, e-mail: [EMAIL PROTECTED]
-> For additional commands, e-mail: [EMAIL PROTECTED]
->  
-> 
-> 
-> 

--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]