All Play and No Work
Woah! I had 30 visitors to my blog today and not one of them was me.
A couple of posts back I told you that I had a job interview with the company that I would choose to work for, as if I had any choice in the matter. I never told you how it went. The interview went great for the first 20 minutes. The interviewer asked typical questions such as, "Why did you pick computer science?", "What was your favorite class?", and "What do you know about [Company X]?" I represented myself really well, and I was confident and relaxed. However, right after the 10 minute disruption from the three car pile-up 50 feet from his office window, the interview turned ugly. He asked me... technical questions! The next 30 minutes of the interview went something like this:
Interviewer: "Can you define inheritance as it relates to object-oriented programming?"
Suzie: "Ok. Inheritance is when one object... inherits... data and attributes from another object. An object has all of the attributes of its parent as well as having attributes of its own."
Interviewer: "Can you be more specific? How would you utilize inheritance in Java?"
This is when I would ramble on some more, and then the interviewer would circle 2. I was being graded on a scale of 0 to 5 (5 is best).
Interviewer: "How would you write an SQL query to count the number of entries in a database?"
Suzie: "Well, this is something that I don't know off the top of my head but I have studied it in the past. I could look up the answer in a book within two minutes. I mean, come on! I had my database class more than two years ago! Do you expect me to remember every single detail that I learned in class? I didn't even know there were going to be technical questions for this interview. You should have warned me beforehand! I would have studied! I've been tricked! No, don't circle zero! Nooo!"
This is when the interviewer would circle zero. And retrace the circle two or three times.
After the two full pages of technical questions were over, I asked, "When will I find out something?"
Interviewer: "Well, not as soon as you'd like. If it was a stand out interview we would try and hire that person as soon as possible. But for most interviewees, it will be at least a month because we're waiting for a job fair at the end of February." Apparently, I didn't stand out.
I say all of this because today at my school there was a job fair and [Company X] was there along with [Company Y] who I would also like to work for. The representatives from [Company Y] said I was stand out. Maybe that's because I was the only Caucasian female they had seen all day but I'd like to think it was because of my skills. My computer hacking skills, that is.

3 Comments:
You have the opposite problem from what I have. You see you have the qualification and I have the experience. Somehow companies expect people to magically have both. You have experience and you don't have the qualification they don't think you are stand out. You have the qualification and you don't have the experience they think you don't stand out. So it's hard to get both because you need both to get a job. Catch 22.
Well I've recently found out that a Sun or a Microsoft certification can add lots off value even to a Masters degree because it basically says you have both knowledge and experience because it's a very practical approach to learning.
I once did some computer programming in high school. I used DOS to developed a Road kill menu that would tally all the prices and selections. It was kind of boring but in the end it was cool. I really don't think that I am qualified to do anything on computers other than make comments on this blog. I have other professional qualities but I rather not expose those to the wide and growing wider range of people check this blog.
and them some...
-~-
I agree Johan, it is tough to get experience when you don't have any to begin with.
Road kill menu? That's something I haven't thought about doing before. Hope it was never used it real life! Suzie
Post a Comment
<< Home