Question for An Interview 1

[JohnMBoston]

Hello

I'm filling out an online job application, and they have two tech questions. One is "what's the most common and efficient approach to a DB2 call with multiple returns?" and the other is "what are the common tools for DB2 inquiry?". The second one is easy - SQL (are there other common tools for inquiry?). The first one I don't know - I've only set up databases (and actually, only once in DB2); I didn't work on any coding. Now just to be ethical, I'm going to state with my answer that I don't know that much about actual DB2 coding. But, it would be nice to give an answer anyway.

 

[screwloose]

So you are going to provide an answer you received from an online forum, from somebody who may not even know what they are talking about, in an attempt to obtain a job that clearly needs experience in the area that you don't have knowledge?

I would say you are not even qualified for the position based on your printed statements. So don't waste their time and money or your time.

 

[chiph]

I agree. Sure, someone will give you the answer to this question, but if you get the job they'll expect you to know these things cold.

When you don't, you end up burning your reputation "points", making it harder to get a job later. Remember, IT is a small community, and everyone knows each other. Word will get around.

So, be honest and either leave it blank or put "I don't know, but I could look it up for you". The latter shows that you're willing to admit the limits of your knowledge, and that you're willing to spend time learning about it.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[JohnMBoston]

...but finding out the answer demonstrates inititive and ingenuity. and, there's definitely other aspects of my qualifications that are above and beyond what they are asking for. I think your response is short-sighted and limited - definitely NOT what an employer would be looking for....! Standard "techie" - living in a limited world.

I'll just stop in a book store and look it up anyway.

 

[screwloose]

...and the other is "what are the common tools for DB2 inquiry?". The second one is easy - SQL (are there other common tools for inquiry?)..."

You are asking a question that you definitively state you know. Also, it isn't so much the "DB2 coding," but rather database experience in that area that you don't have. And, if that "Standard "techie" - living in a limited world" phrase was meant for me, then consider:

BS Business Administration
MSEd Business & Technology Education + 6 hours
A1C USAF Civil Engineering - PRIME BEEF (Primary Base Engineering Emergency Force), Fireman Specialist
Tech Specialist - my state's largest distributor
Unix Sys Admin - Fortune 400 company
Unix Sys Admin - Federal Govt Contractor
University Instructor - Adjunct Faculty
10 years in IT

For my research project in grad school, my paper was read by the superintendent of public schools in that particular city. His comment was, "it was a better written paper than most doctoral dissertations." The professor overseeing the study said it was the best written paper he ever had (in more than 20 years.) It used a multi-variate analysis of variance (MANOVA) because there were several dependent variables in the single experiment.

Plus, I intend to continue my education further because I don't intend to stay doing this job forever. An educated person has more opportunities.

Not everyone usually meets all criteria for a job, and you can let them know in an interview that you are capable and willing to do whatever to learn and do the job, however, in this case it seems it is a job that requires a more advanced knowledge of DB2 that you don't have. The application is to weed out those who don't meet INITIAL qualifications. Which you DON'T meet.

Next time, think twice before calling someone myopic.

 

[chiph]

JohnMBoston -

Best of luck in your job search.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[willir]

Well I guess we have to give kudos to JohnMBoston for being honest in his post.

But I agree with the rest -- a job application should be posted by the person requesting the job on their personal knowledger and experience.

but finding out the answer demonstrates inititive and ingenuity

TRUE, but consider the web as tool to find your answer, not to ask some one for the answer.

In a past life, I knew a person who was a very good "talker". Talked themselves into the head of a research position. I questioned the person on their lack of experience with statistics, research, etc. The comment -- "I could pick that up in a month or two". Hmmm... Well about 3 months into the job, they left on sick leave. The real reason was the person was sadly under qualified for the job. It did not take long for those who worked with the person in question to realize the lack of qualifications.

In the end, after a year, the company sued this person for false pretenses. The company was set back on time spent searching for a candidate, and lost a huge amount of time on the research project. The person who got and lost the job now has a huge hole to explain in their resumé, and actually did get sick from severe stress (ulcers). There were other casualtities as well...

Bottom line:
Get the best job you can that you are qualified to perform. If does benefit you if you obtain a job that you are not qualified to perform.

 

[Onyxpurr]

I'd have to agree with willir. While you may research it, you're only answering a small portion of the larger picture. Answer honestly with stating you don't know and what you would do to find out.

Sometimes the point of the interview is not only what they know, but what they're willing to admit they don't know as well and how flexible they are to finding out the needed information.

 

[rosieb]

It depends on what the interviewer is looking for.

My current boss recently told me that he'd hired me not because of what I knew, but because of how I handled the questions on what I didn't know. IT moves so quickly, he felt that if I hit a real problem, I'd know how to find the necessary information to sort it out.

In the past I once went for a job that looked as if it fitted my skills, after 10 mins it was clear that I had very little of the experience they were looking for. At that point I relaxed, I couldn't do any worse, so I was brutally honest about my knowledge and experience, but was clear on how I'd handle this, and got into a debate on one of the issues I was really confident on.

I didn't get the job, but I did get a letter saying I was reserve candidate, if their preferred candidate refused, they'd be happy to train me - oh and keep an eye on their web-site, as they'd like to employ me.

Some organisations/interviewers look more at potential than at existing skills. (I've never been qualified for a job I've got, but I've always done pretty well in them.)

Rosie
"Never express yourself more clearly than you think" (Niels Bohr)

 

[ESquared]

The purpose of interviewing isn't to test knowledge, anyway. That's just a sideline.

If they give you the questions ahead of time, and you don't have the answers in the interview, what possible excuse could you give? "And you didn't find out the answer to one of the pre-given interview questions before coming because you think that will make us (choose one) • more or • less likely to hire you?"

So, I don't have any problem with what JohnMBoston is doing. He was up front with us that it is an interview question, and didn't just go ask it in one of the forums. Perhaps he also has the integrity in the interview to say, "well, here's what I found when I researched this, because I knew the questions ahead of time. Although, don't you give those darn people on tek-tips the time of day! I mean, really!!!"

Then again, maybe he who will do anything dishonest to get a job and being told he's doing something wrong is just what he needs to begin the process of self-examination and correction.

It all depends on whether you want to give him the benefit of the doubt.

-------------------------------------
It is better to have honor than a good reputation.
(Reputation is what other people think about you. Honor is what you know about yourself.)

 

[celeron895]

Awesome credentials screwloose! You are an IT god. Way to be!

 

[Onyxpurr]

I hear ya Rosie.

Consider this...when I was desperate, I interviewed for a help desk position in the company I was temping for. The IT director called me up personally and said that I didn't fit the bill for the help desk position (something I knew already), but that I shouldn't sell myself short, that I was way above this position. Outcome? A few months later they CREATED a position for me as business programming analyst with much more flexibility and better pay.

Glad I didn't try to BS my way through that help desk interview! ;-)