Stupidest way to apply for a job
-
Giles wrote:
Also, throw away half the CV's as you don't want to employ anyone who is unlucky.
Is that supposed to mean that you disagree with what I am doing (as stated in my original post)?
Heh, no, its a joke :D If you randomly pick half the applicants and discard them, they MUST be the unlucky ones, otherwise they would not have been chosen. So who wants unlucky staff?! I want the lucky ones! :D
-
I can't believe it how so many candidates mail their resume with two dozen email addresses in the To: header [each of them a jobs@ or hr@ email ID for some company]. And the body of the mail is generic crap such as "really want to work in your great organization". That's pathetically stupid in my opinion - when I get such mails, I simply delete them. In fact I even delete mails where the To: is the same as From: and I am in BCC (since that's a sure indication that there must be several other IDs in BCC).
Well I do the same, and believe me it works, as I have not forwarded my resume to you. Who has the time to make custom resumes for each company. Just throw your resumes to all consultants, and its their business to find the suitable company. http://www.priyank.in/
-
Also, throw away half the CV's as you don't want to employ anyone who is unlucky.
"Je pense, donc je mange." - Rene Descartes 1689 - Just before his mother put his tea on the table. Shameless Plug - Distributed Database Transactions in .NET using COM+
-
Well, I meant any of them. :) I've learned a lot of different things because the job demanded it. I think that demonstrates the ability to solve problems which is what the brain teaser questions are for. So there you (not dave, but a rhetorical "you") sit, as an interviewer, interviewing a programmer who has a long list of self-taught languages, and types of jobs that required almost intimate knowledge of various business types, you've talked with him for several minutes probing his knowledge to make sure he sounds legitimate, and then you rattle of a problem-solving brain teaser. When I'm the programmer being interviewed, I offer that the brain-teaser is a waste of my time condsidering my level of experience, and thank the interviewer for his/her time. If they want to ask me programming questions, fine. Oh, by the way, can I use a book or MSDN to look it up so I can give a precise answer? I've long-since forgotten the specifics, but I still know how to look it up, and I'm not at all embarrassed to admit that I need to. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
Spot on. It is something that reall pees me off, being asked stupid questions about minute detail, when in reality, it is your ability to put together a working architecture that is the true value of a good engineer. Details are in reference books, and like any engineering discipline, they are at the disposal of the engineer. For example, here one of those silly questions: in a file you have ULONG val[]={1,2,3,4}; in another extern ULONG *val; is sizeof(val) the same in both files? Nunc est bibendum
-
It's an old joke... ;)
You must be careful in the forest Broken glass and rusty nails If you're to bring back something for us I have bullets for sale...
-
I only send one resume at at time, and only if I feel I'm qualified for the position. I have a smattering of VB, and I abhor the language itself, so I would never apply for a job that emphasized the use of VB, despite the fact that I know how to start up the IDE. I doubt I'd even apply for a C# position (unless the add stated a working knowledge of C++ was beneficial), despite having 15 years of C/C++ experience. Most companies want someone who can "hit the ground running", and I can't really do that with C#. For job applicants: I guess what I'm trying to say is don't waste people's time applying for work you know you're not qualified for. People don't generally want to hear "i'm a fast learner" - they want to hear about what you already know. For interviewers: Consider the applicant before sppouting off one of those cutsie little brain teaser questions. I taught myself Pascal, C/C++, CMS-2Y, MFC, development under proprietary WinCE devices, the finer points of estate planning (tax calculations), how to write DLLs, and the Windows API, and I've been coding for 25 years. I've walked out of plenty of interviews when they started asking stupid questions or wanted to give me a test. It's insulting to programmers who've been in the biz for as long as I have. Save that crap for college grads with no job history. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
John Simmons / outlaw programmer wrote:
I guess what I'm trying to say is don't waste people's time applying for work you know you're not qualified for.
What is so tough for the novice interviewer, though, is a frame of reference. For instance, I went to some job interviews where I was practically laughed out of the building, and other interviews where I was a God-Send and when can I start? All of this with the same resume, the same salary requirements, and through the same recruiter. The better you are, the more confident you are with your strengths and weaknesses. When you're a novice, you have no idea how good you are, or are not. I look on CodeProject, for example, and I feel like I'm 2 days old; I talk to others (who make more money than I), and they practically don't even know how to open up Visual Studio. One perfect example is what happened to me last night - at the VS 2005 launch, I ran into my boss from the last job I was at. He told me when I left, he lost his best asset. I was making $45 an hour there (contract of course), which I think is greatly inflated (for my skill-set and resume). So all I'm trying to say is, is that it's so hard for novices to know what to apply for.
