Job different than posting--OUCH!

Submitted by Anonymous (not verified)
in
BLUF: I went to an interview yesterday for a particular job, and discovered that the job posting was misleading enough it might as well have been a totally different position. Here's the posting I responded to: [url]http://sacramento.craigslist.org/sof/699967152.html[/url] Now, I was quite excited, because management is the direction my career is going in, and the position is a stretch but within my capabilities. I got called to interview just the day after I sent my resume and I thought "cool"! I went in, did my intros as per the Interview series, handled the "tell me about yourself" question as best as possible considering I wasn't as prepared as I'd have liked (there's a lot of work to do in the interview series, and I had just started listening to earlier this week) and we were off into the interview. I'm doing OK even through a question I didn't really anticipate along the lines of "what do you want to do (professionally)". Then he hits me with the salary expectation question. I had done my research, and though I couldn't find the exact job description, I extrapolated that similar jobs were in the $110k - $150k range. I told him $125k. Well, that was the _wrong_ answer! Come and find out that what they're really expecting is not a manager, but they want a System Integrator who will go out to client sites (70% travel) and handle integration problems of their product with the clients equipment. For the $70k range. Eventually (when the product takes off, and since it won't ship for over 6 months, not anytime soon), this person might take the lead and build a team of system integrators. The 70% travel was a surprise, but then the details of the job was a bigger surprise. The job I was interviewing for was way different than they posted (and no, they weren't offering me a lesser job and keeping the bigger job open, there was no job with the description as posted). It was very difficult not showing my disappointment, this position is not one I could take even if I was still interested as I can't travel that much (I've got a 2 year old at home, and frequent multi-week trips isn't going to work for my family). He figured out I couldn't do the travel part, and so asked if I'd be interested in a QA position. Unfortunately, it pays similarly, so I'd be taking a big pay cut, and going back to doing work I left behind 8 years ago. I was willing to be interviewed by the other guy for the QA thing, but I realized it's not going to work. Especially since it was clear that they just thought about the QA thing recently and really hadn't worked out the details of the job yet. I didn't close on either positions, because I don't [u]want[/u] an offer as it's not one I can even dream of taking. Just curious if this has ever happened to anyone, and how did you handle it in the interview? Also, I'm wanting to write the thank you notes, but should I mention that I'm not interested in the job and wish them well in filling it? Or should I just write the thank you and not both with the "I want an offer" part? A direct of mine that was laid off at the same time would be perfect for either job and I'd like to call the VP who interviewed me and recommend him. Does any one have suggestions on how to do this? Thanks, - Steve
Submitted by John Hack on Friday June 20th, 2008 3:59 pm

Wow.

Write the thank you. Don't close. One of the great things about the close is that you simply don't do it when you don't want the offer.

And yes, you can recommend the direct. I would have the direct send a cover letter (with resume) that says "Steve suggested I contact you..."

You can then confirm his suitability for the job when you act as a reference.

John

Submitted by Inactive Membe… on Saturday June 21st, 2008 9:39 am

[quote="derosier"]Just curious if this has ever happened to anyone, and how did you handle it in the interview?[/quote]

Steve: I've had similar experiences because I'm in marketing - and ads often use "marketing" and "sales" interchangeably. So I'll find myself applying/interviewing for a Director of Marketing job, and it turns out to be a Sales Manager job.

Both are great jobs - but the sales management is something I did 12 years ago, before I moved into marketing.

I've learned to sniff these things out pretty well, first in the ads, and then in the screening interviews.

On occasion I've found myself in a phone or face-to-face interview for the "wrong" job. What I've learned to do is to "stick to my script" and fight the temptation to rationalize in my head about maybe how I [u][i]could [/i][/u]do this other job, and how if I answer questions a little vaguely, I might still be in the running, etc...

We end up agreeing that, well, they don't really need what I bring, or that's not what they're looking for (right now).

-Hugh

Submitted by Tom Waltz on Sunday June 22nd, 2008 7:08 am

From what you said about what they are looking for, I could almost see how the job could be rosy-colored to be what the posting says, except for the "Director" part of the title. A Director is supposed to be a manager of other managers.

To me, it sounds like a typical under-managed startup company trying to inflate its importance.

Submitted by Steve deRosier on Wednesday June 25th, 2008 12:01 pm

Normally I'd agree with you that it's a startup. But in this case it's a company with 20 years in the business.

My theory is simply that they posted what they hope the job will become in a few years assuming that the product takes off and sales go well and they make enough money to need someone to lead such a group.

The thing that gets me about it is, by posting a misleading description, they'll get lots of applicants that won't fit and it'll be harder to find the right person to fill the job. It's a lesson that I'll keep in mind next time I'm hiring and post a job description.

- Steve

Submitted by Inactive Membe… on Wednesday June 25th, 2008 12:37 pm

[quote="derosier"]The thing that gets me about it is, by posting a misleading description, they'll get lots of applicants that won't fit...[/quote]

[list]...and will be left wondering why they didn't get an interview for what looked like a perfect fit!

[i]How could the applicants possibly know that the company is looking for something other than what they say they're looking for?[/list:u][/i]

This reminds me of another recent thread - which touched on how bad it is that companies are really poor about getting back to candidates who apply. (If you want to see it, go to http://www.manager-tools.com/forums/viewtopic.php?t=3208&highlight=).

This is another reason why you CAN'T allow yourself to think you've been "rejected" when a company doesn't respond to your resume and cover letter: [i]hell, maybe the posting is wrong![/i]

So - hey fellow job-seekers out there: give yourself the benefit of the doubt. It might have NOTHING to do with you! :wink:

-Hugh

Submitted by Paul Moriarty on Wednesday June 25th, 2008 12:49 pm

I'm sorry to hear about your experience.

In the past when I have been interviewed for a position that clearly is not in line with what I was expecting, I wait for my turn to talk and politely say something like, "after hearing your detailed description of what the job entails, this isn't a good fit for me." Then wrap up. If you know of somebody who might be a good fit, mention it and see if they are interested in you passing that person along to them - they usually are. Thank them for their time and consideration and move on in your search.

I've done a similar thing when being the interviewer. I have no problem cutting an interview short and saying that it doesn't sound to me like we have a good fit and wrap up.

In both cases, it saves everybody a lot of time and, if handled professionally, leaves the door open for future opportunities.

Good luck with your search!