Subj : Re: Software Job Market Myths
To   : comp.programming,comp.software-eng
From : CBFalconer
Date : Mon Aug 15 2005 06:04 pm

Chris Sonnack wrote:
> 
> Peter K. writes:
> 
> > I agree; I've seen fradulent resumes during the post-mortem after
> > people were fired (or quit).  It's a bit of an eye-opener.
> 
> We've been interviewing here for a several open positions recently,
> and I'm astounded at what people put on their resume.  I designed
> a few simple questions designed to test folks' understanding of
> certain areas, and--despite claiming "expertise" in an area--I've
> been getting a lot of blank looks and faked answers.
> 
> I have a feeling someone will ask what those questions are, and I'd
> be interested in feedback anyway, so here some are (we're seeking
> folks strong in Java, VB, HTML, JavaScript, XML and related areas):
> 
> * What is J2EE?  What does it mean?
> 
> * What is a Java Bean?
> 
> * Visual BASIC: What are the two possible starting points in a
>   VB program (i.e. where are the first lines of code that run)?
> 
> * Is it possible to create a "class" (user-defined object) in
>   JavaScript?  And if so, how?
> 
> * Name some HTML FORM controls.
> 
> * What are three possible sources of style sheet info for an HTML
>   element?
> 
> * What is the difference between an http GET and http POST?
> 
> * Describe XML, XSD and XSLT.
> 
> I'm less interested in their exact answers than how they field the
> question and respond, but obviously the content of the answer does
> matter.
> 
> And the technical part is on a piece of the whole.  Ability to
> work with others, seek out their own answers, network with others,
> etc. are equally--if not in some ways more--important than their
> technical ability.

My interests don't run that way.  I have heard of most of those
terms, but I couldn't answer any of those questions.  I _could_
find out in fairly short order.  Yet I suspect I would be a
worthwhile hire even for your application.

-- 
"If you want to post a followup via groups.google.com, don't use
 the broken "Reply" link at the bottom of the article.  Click on 
 "show options" at the top of the article, then click on the 
 "Reply" at the bottom of the article headers." - Keith Thompson

.