Thursday, August 24, 2006
It’s been an interesting last few days.
My email address seems to have gotten listed as being that of a spammer. Again. On a good day, I might send out about 24 emails. A spammer I am not.
Thankfully, that’s been cleared up now.
I got contacted by two companies this week that I actually responded to (read that they were for full time positions and weren’t looking for things that were blatantly not me. Though I have to admit that more places seem to actually be looking at my website before they contact me).
One’s a company about an hour or so from here, and the other one is Amazon.
I’m interested in interviewing with both of them, but I’m also a bit nervous about the Amazon interview since the position includes, among other things, something I haven’t really done in two years (and that’s explicitly stated on the profile they used to find me, so I’m hoping that it won’t be that much of an issue).
The phone interview with Amazon is supposed to be a technical one, so I’m basically expecting to get hammered to the wall with it. The other one I don’t know much about yet.
I find it amusing that I get so nervous before some interviews. I know that if it goes well, it goes well and if it doesn’t then it doesn’t, but there’s just something nerve wracking about them for me. I think it’s the fact that so many of them try to grill you on things you did ages ago, trip you up just to see if they can, or ask you impossible questions (yes, some people like to ask impossible questions to “see how you will react. I consider this to be BS) so I end up sitting there trying not only to give the correct answers but to feel out the people who are interviewing me and their intentions.
I have largely become of the opinion that interviews aren’t much fun for the people on either side of the table, and there is something wrong with the people who actually enjoy them. =]
It’s funny. Interviews make me nervous, but being thrown into the sparing ring with someone doesn’t at all. I also don’t tend to get nervous when working on actual problems unless I’m running up against a hard time limit or someone is badgering me. It’s the whole “put him in a maze like a lab rat while we act smug, superior, and all knowing” thing that gets me.
Unfortunately, I’m not kidding about the acting smug, superior, and all-knowing part. I once interviewed with a company that gave me a test they had supposedly just re-written, labeled it as a C++ test and it was really just a straight C test. I got it and noticed printf statements (among other things) everywhere. I later asked the dev manager about it and basically got yelled at, stonewalled, and then told that it didn’t really matter anyway because they were porting everything to C#.
If it didn’t matter, why re-write the test? If you’re migrating from one language to another, would it not be a bit important to know the difference between the language that you say you are migrating from and the language you use as a test for prospective employees? Furthermore, why jump down a candidate’s throat who asked a rather pertinent question?
I wasn’t smug or snotty when I asked. I genuinely wanted to know. But the whole interview ended up being pretty bad, so I doubt that I would have accepted their offer if they had made one.
Hopefully neither of those interviews end up being like that one or worse. Please let me meet an at least somewhat sane company that wants to hire me. =]
Current mood: tired
Current music: Deadsy – Brand New Love