last night: funny; today: job interview
May. 4th, 2006 09:13 amso, last night I ended up hanging out at the big time for a while and then heading up to the hill to meet up with a friend. we ended up playing crazy wander around the hill games for a couple of hours, and then I crashed and went to bed. I was fairly stressed out last night, largely because today is going to be my first 'real' job interview in like 10 years.
The last real job interview I had was about three years ago at a local software monopoly, and one of the interviewers got angry at me because I described our software getting better performance than what it turned out their the version of more or less the same software did. (Like, got angry, engaged in masculine imperatives, more or less terminated the interview, stuff like that) Really lucky I saw that behavior before starting the job. So, not many interviews. How did this happen?
I worked for one company for 9 years, and the other side projects I've worked on have largely been either self-directed, or there's been no interview involved at all (like Static Factory.) I didn't even have a relatively current resume until I talked to some folks from google a couple of weeks ago, and I'm still not sure that I have a good resume. (I had it looked at by some career services folks locally yesterday.)
I'm interviewing today at a company (called Echo Whiskey Sierra) for a contracting gig. It seems to be the sort of place where I could do both Info Org and Engineering stuff, and is a pretty good work environment. The contract would probably span the remainder of my time at the iSchool, and then some. In general, it seems like it would be a good fit for me for a full time position on a variety of levels, and that's what i'm trying to find out. I've got a plan to move around a lot of my early summer plans to fit better with the contract that I've worked out over the last couple of days.
Because it involves dev and info org stuff, I've been scanning through The Art of Computer Programming by Knuth to look at the things that I can never remember the name of. One of the perils of not having taken any computer science courses in school (aside from 'Programming Languages,' which was a lot like getting kicked in the head repeatedly and 'Processor Design (or whatever),' which was about how to built a RISC processor from the ground up using common household appliances) is that I'm better at remembering how/why to use something than what to call something.
The last real job interview I had was about three years ago at a local software monopoly, and one of the interviewers got angry at me because I described our software getting better performance than what it turned out their the version of more or less the same software did. (Like, got angry, engaged in masculine imperatives, more or less terminated the interview, stuff like that) Really lucky I saw that behavior before starting the job. So, not many interviews. How did this happen?
I worked for one company for 9 years, and the other side projects I've worked on have largely been either self-directed, or there's been no interview involved at all (like Static Factory.) I didn't even have a relatively current resume until I talked to some folks from google a couple of weeks ago, and I'm still not sure that I have a good resume. (I had it looked at by some career services folks locally yesterday.)
I'm interviewing today at a company (called Echo Whiskey Sierra) for a contracting gig. It seems to be the sort of place where I could do both Info Org and Engineering stuff, and is a pretty good work environment. The contract would probably span the remainder of my time at the iSchool, and then some. In general, it seems like it would be a good fit for me for a full time position on a variety of levels, and that's what i'm trying to find out. I've got a plan to move around a lot of my early summer plans to fit better with the contract that I've worked out over the last couple of days.
Because it involves dev and info org stuff, I've been scanning through The Art of Computer Programming by Knuth to look at the things that I can never remember the name of. One of the perils of not having taken any computer science courses in school (aside from 'Programming Languages,' which was a lot like getting kicked in the head repeatedly and 'Processor Design (or whatever),' which was about how to built a RISC processor from the ground up using common household appliances) is that I'm better at remembering how/why to use something than what to call something.
no subject
Date: 2006-05-04 05:09 pm (UTC)no subject
Date: 2006-05-04 05:12 pm (UTC)