By that I suppose you mean your job creating the Daleks, and that the other evil scientists "love" you, by which you really mean fear you!
Mr Awe
Just tanked a job interview.
- Thread starter sojourner
- Start date
By that I suppose you mean your job creating the Daleks, and that the other evil scientists "love" you, by which you really mean fear you!
Mr Awe
I had a interview where the person doing the interview could not think of anything to say.
I had to ask her about pay,hours and what the Job entailed etc
I had to ask her about pay,hours and what the Job entailed etc
when i went to the interview for the job i'm in now i remember the boss all high and mighty telling me how good the company was and the like and i admit i was getting bored. any way he stopped and said
"so why do you feel i should hire you?"
without thinking i said
"well the main thing would be that i actually turned up and stayed to the end instead of walking out twenty minutes ago"
he looked me straight faced and i thought i had blown it but he said
"cant be more honest then that you start tomorrow"
"so why do you feel i should hire you?"
without thinking i said
"well the main thing would be that i actually turned up and stayed to the end instead of walking out twenty minutes ago"
he looked me straight faced and i thought i had blown it but he said
"cant be more honest then that you start tomorrow"
I've tanked just about every interview I've ever had. In fact, I think the one good interview I had was completely sabotaged when unbeknownst to me my former boss who volunteered to serve as a reference decided to make shit up because I didn't take my old job back when it was offered to me a few weeks after I was originally downsized!
Yeah, that probably cost me about 8 months of work, but on the bright side I didn't end up testing Sony HDTVs for a living, which is incredibly boring.
As for coding questions in interviews. They're usually pretty ridiculous. Write an extension method? Give me a break. That's exactly the sort of thing you would Google when you need it. Luckily I interviewed with someone who wanted someone with broad programming skills instead of being able to recite MSDN documentation by heart.
I mean, I guess I understand that you want to be confident that a candidate has the skills they claim... but I got way too many questions in various interviews where anybody who isn't an OCD mouth-breather would just figure out the right answer with 2 seconds of googling or intellisense spamming. No, I can't write a fucking event handler for random mouse/keyboard input without looking up what event arguments I get sent. So the fuck what?!? I've seriously gone on interviews where the fucker was mad that I didn't know some of the stuff by heart and just wrote something like "mousePos.X" rather then exactly how the fucking API exposes it to you on a sheet of paper. As if it actually matters if something I write on a sheet of paper compiles, as if it won't be working two seconds after I step in front of an actual computer.
What kept my spirits up during my last bout of unemployment was to be combative when faced with stuff I found stupid. I just think to myself "this company actually values this person's opinions. Why on earth would I want to work here?" When they ask you for your salary requirements, and you don't actually want to work there, just double or triple your actual requirements. "What salary would I require to work here? At least 300k..." It's good fun, a lot of HR monkeys get off on thinking the people they interview would suck them off for a job, they're not necessarily ready for you to have a spine.
Yeah, that probably cost me about 8 months of work, but on the bright side I didn't end up testing Sony HDTVs for a living, which is incredibly boring.
As for coding questions in interviews. They're usually pretty ridiculous. Write an extension method? Give me a break. That's exactly the sort of thing you would Google when you need it. Luckily I interviewed with someone who wanted someone with broad programming skills instead of being able to recite MSDN documentation by heart.
I mean, I guess I understand that you want to be confident that a candidate has the skills they claim... but I got way too many questions in various interviews where anybody who isn't an OCD mouth-breather would just figure out the right answer with 2 seconds of googling or intellisense spamming. No, I can't write a fucking event handler for random mouse/keyboard input without looking up what event arguments I get sent. So the fuck what?!? I've seriously gone on interviews where the fucker was mad that I didn't know some of the stuff by heart and just wrote something like "mousePos.X" rather then exactly how the fucking API exposes it to you on a sheet of paper. As if it actually matters if something I write on a sheet of paper compiles, as if it won't be working two seconds after I step in front of an actual computer.
What kept my spirits up during my last bout of unemployment was to be combative when faced with stuff I found stupid. I just think to myself "this company actually values this person's opinions. Why on earth would I want to work here?" When they ask you for your salary requirements, and you don't actually want to work there, just double or triple your actual requirements. "What salary would I require to work here? At least 300k..." It's good fun, a lot of HR monkeys get off on thinking the people they interview would suck them off for a job, they're not necessarily ready for you to have a spine.
^"Candidate is prone to hypochondria, may abuse PTO policies."
So you're saying it was a bad idea to ask about any support for prescription drug dependency in the first meeting?
I remember how when I did an interview for a job with a bank when I first moved to Cincinnati. The interviewers were ice cold (never smiled the whole time, not even to say "nice to meet you" like I got in most other interviews in my ENTIRE life. They ended up got me to talk about working for a zoo......
There was one job I didn't get because they were asking me absurdly technical questions about SQL minutiae (which, in real life, I would've just googled if it ever came up). Ah well. I got a good job anyway.
Yea, that's the type of questions I got. The stuff from experience I know doesn't come up in day to day work, and if it did, I could google in 2 minutes.
You could always go to a technicial school to further your knowledge. Most of the time those schools have job placement. The tech school I am going to for Networking and programming has that. I don't think it would be impossible to get a grant, depending on your states economic situation. But don't give up, you only fail when you say I can't.
