|
Oh I don't mean they shouldn't. Just that, in a buyers market, their reputation in the community means precisely squat.
Programmers are a dime a dozen nowadays and the status quo has always been to just not respond. So, in practice, there's really no reputation hit at all.
|
|
|
|
|
Manners, dear boy, but I'm a Brit.  but it's a pain, I spent a long time looking, only to be told by recruiters that my skills were out of date. Finally get a job find my skills are exactly what is needed
|
|
|
|
|
Not sure how big your community (developers to companies) is in your area but I know of some companies that have pulled the multiple interviews and never respond. eventually word gets out about them doing this and developers start turning down interview requests.
|
|
|
|
|
It's a buyers market at the moment (from the employee's point of view) so with an attitude like that all those companies are going to end up with is sup-bar employees.
Start contracting, nobody ever got rich working for somebody else 
|
|
|
|
|
Man, that is true in more than one country....
It seems like people either don't care or are to timid to even say "sorry, but not this time".
There are no secrets to success. It is the result of preparation, hard work, and learning from failure. Colin Powell
|
|
|
|
|
On a bright note if they are to callous to respond would you really want to work for the heartless bastards?
If first you don't succeed, hide all evidence you ever tried!
|
|
|
|
|
I've thought exactly that. They may "forget" to pay me when that time comes.
(Actually, I actually did have a company forget to pay me for my first week. I worked for another that had a mistake on almost every pay check for the first six months. At another company, a person in accounting decided she had too much work and threw away everything on her desk, including my new hire paperwork and some very important bills.)
|
|
|
|
|
A mate of mine got a job, then the day before he was supposed to start he got a much better job so phoned the first up to say he wasn't going to start.
A month later the company he wasn't working for paid him.
He phoned up, they said thanks for letting us know, send the money back.
A month later they paid him again.
This carried on for six months.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
I'm a devoted lurker at Ask a Manager and the lack of reply from even a good amount of investment of time and effort on both partys seems quite common. There are all sorts of reasons - but none seem to be in *your* favour.
The essential advice: This sucks. Get over it. Assume you've don't have anything until you have a written offer. Stressing about it just makes you feel bad, and doesn't harm the rude people.
Iain.
I am one of "those foreigners coming over here and stealing our jobs". Yay me!
|
|
|
|
|
Joe Woodbury wrote: If you take the time to interview someone, take the time to follow up.
One should at least take the time to call, if only to say, "Douchebag!" 
I actually had an interview once and got a call that evening to inform me that they were sending me an offer. That was in July. I got the offer the following January. 
Will Rogers never met me.
|
|
|
|
|
Yep, this happens often... as an engineer, I don't understand at all why not just say something rather than nothing at all. I guess HR is a job consisting of being nice to whomever happens to be in front of you at the time and nobody else.
|
|
|
|
|
Albert Holguin wrote: I guess HR is a job consisting of being nice to whomever happens to be in front of you at the time and nobody else.
Hmm, I always wondered how that department was supposed to work. That statement clears up a few things ... thanks!
|
|
|
|
|
I hate to call them two-faced but it does seem that way on occasion.
|
|
|
|
|
|
I've also had interviews before. What's annoying is that after the interview and they didn't want you to be part of them, they always say, "We'll call you."
Don't mind those people who say you're not HOT. At least you know you're COOL.
I'm not afraid of falling, I'm afraid of the sudden stop at the end of the fall! - Richard Andrew x64
|
|
|
|
|
Agreed, but in these days of everything being done by email, there really is no excuse for not at least acknowledging the receipt of an application, even if they don't bother to tell you that you were unsuccessful.
I applied for a senior position once at a public utility who's motto included the phrase "Investing in people...", and - despite my sending the application by post and by email (and incidentally having to repair their PDF form in order to complete the application in the first place) they didn't even acknowledge receipt with an auto-response, so I had no idea whether it had been received.
The HR person was very annoyed (and rude) when I rang up on the day after the closing date to find out whether or not the application had arrived, saying that they had lots of applicants and didn't have time to respond to every one! At that point I decided I didn't want to work at a public service organisation with that kind of internal culture anyway...
Needless to say, I didn't even get an interview. Now maybe I wasn't a good candidate, but that doesn't excuse rudeness and lack of care.
Mike
|
|
|
|
|
Most companies can commit with a letter/call/e-mail within 24 hours, even if contract paperwork takes longer. Bigger the company, more professional they should be so rudeness really is unacceptable.
My experience has been the longer they take to reply, the less likely you are to get the job. After a week it's pretty much a write-off. If they wanted you they'd come running, it being a developer's job market.
And after a refusal (whether to invite me for interview or after interview), they'll never have a chance to employ me again, no matter what the offer. Hell hath no fury like a female dev scorned 
|
|
|
|
|
Having done tons of interviews.
1) It is too time consuming. We interviewed 10+ people for each position
2) It is an awkward converstation: "Hey John, remember me... Yeah, you didn't get the job"
[I only make that call when it ends with: "You were MY #1 choice, but I got trumped by H.R. and the manager
you will report to. Is it okay if I keep your info, in case something opens up?"]
3) The person getting the offer gets a call.
Finally, a different perspective.
You would not even think about it, if you just landed a new job you enjoyed!
Would you call back all those companies you interviewed with and say "remove me from consideration"?
I wish you the best on your journey.
In the meantime, Write a CodeProject article. Give yourself an edge at the next interview
|
|
|
|
|
Member 10389821 wrote: Would you call back all those companies you interviewed with and say "remove me from consideration"?
Good point. I think not!
Once you lose your pride the rest is easy.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
Member 10389821 wrote: Would you call back all those companies you interviewed with and say "remove me from consideration"?
If I haven't heard from them, I do.
|
|
|
|
|
In my experience there are companies out there where not calling you back is part of the hiring process. It is not intended to be rude, rather they want to find out a few things about the candidates.
1) Does the candidate really want this job? Do they want to work here, or they just want a paycheck? (this matters to many employers)
2) Is the candidate the sort of individual who will take initiative and follow up on their own?
Many companies want to see these traits in potential hires. I understand that some companies also just want worker bee type developers as well, meaning the above traits would not be valued.
Once I interviewed with a place 4 times, having to follow up with them after a couple weeks each time. They ended up offering me a job, but I took a different job anyway; not because of hard feelings the other place just offered more money.
For the record I did end up having a conversation with the company I turned down letting them know I was not taking their offer.
|
|
|
|
|
Rowdy Raider wrote: 1) Does the candidate really want this job? Do they want to work here, or they just want a paycheck? (this matters to many employers)
2) Is the candidate the sort of individual who will take initiative and follow up on their own?
I have heard that before also. I always call back and if I really want the job call back even after being rejected. Sometimes their first choice turns them down and you show more interest than others. It has worked for me. 
Once you lose your pride the rest is easy.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
It is better not to work for companies who can't be bothered to reply - if they don't care about people and common decency then it's probably best to avoid them.
|
|
|
|
|
I always ask about last date of the interview answer. If the answer was not received up-to the date, then the answer is... 
|
|
|
|
|
Hello all,
I've decided to go the IMAP way at our company... (phone change and multiple devices without Exchange)...
Now that we are here, it looks like Outlook 2013 doesn't like IMAP at all... and I'm having lots of problems: non synchronizing folders, Sent items go there only after applying a rule... Today I've received a really old message as unread into the Junk folder. 
In case I'm trying to get something to work which won't (there are several places around that show complaints regarding that)... which would be your recommendation on a mail client? I've tried Mozilla Thunderbird and it just worked... (It is uglier than Outlook and makes less things, but it works...) I'm about to propose every single user in the company to switch to Thunderbird, but before doing that (which will be difficult for everyone)...
Can Outlook 2013 work well with IMAP? should I do something to get it working as expected?
Thank you in advance!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
