This morning a recruiter called to ask me if I was available for a contract. I of course said "yes."
"Do you have Oracle database experience?"
"I think so." (I worked at Oracle for three years.)
"Do you know what 'SQL' [pronounced "see-quel") is?"
"Of course! Structured Query Language."
"Are you sure?"
"Yes."
"I ask because we sent two candidates to the client, and neither of them knew what it was. When the interviewer asked what 'SQL' stands for, the candidate asked, 'Can you spell that?'"
"Do you have Oracle database experience?"
"I think so." (I worked at Oracle for three years.)
"Do you know what 'SQL' [pronounced "see-quel") is?"
"Of course! Structured Query Language."
"Are you sure?"
"Yes."
"I ask because we sent two candidates to the client, and neither of them knew what it was. When the interviewer asked what 'SQL' stands for, the candidate asked, 'Can you spell that?'"
no subject
Date: 2010-06-03 06:14 pm (UTC)I tend to do the opposite, I state that I don't know much about the subject (if I don't) and then in the interview find that I know more than the interviewer and get the job. (There are some subjects on which I can reasonably claim to be expert, and do, but in many more areas I'm more aware of my lack of knowledge than of any ability.)
no subject
Date: 2010-06-03 06:21 pm (UTC)except
Date: 2010-06-04 12:44 am (UTC)no subject
Date: 2010-06-03 07:45 pm (UTC)In Kevin's initial example, I would have told my boss "we don't want to hire somebody with lies on their resume".
no subject
Date: 2010-06-03 11:28 pm (UTC)no subject
Date: 2010-06-04 12:09 am (UTC)