News for hackers. Stuff that matters.
Re:Rejecting a candidate for over-qualification results in a... by Clubber on Thursday October 12, 2017 @08:31PM (#15462496)
I didn't downvote you, but I didn't agree with the first half of what you said (I'm also past the hill). In fact I just upvoted you, because down voting isn't for disagreements, it's for shallow and unproductive arguments (which yours was not).

>However, just as an employer may look at something like commuting time and say to themselves "wow, they're going to commute for 2 hours, that's going to be tough", an employer can look at someone who is older and assume more expenses and say "wow, they might be digging into savings, that's going to be tough".

I think it really boils down to context. If you are a 6 figure developer taking a $40K job, yea, maybe, but if someone is paying $40K for US developers, they don't get to bitch about turnover, that would be a given.

So let's take something more realistic (and I'm framing everything in terms of development, because that's what I know). Say a $150K guy drops down to $100K. To me that isn't a red flag, maybe the guy wants to do something different in a new language. Say a Windows guy wants to do iOS or Linux or vice versa. Unless they are crazy with their money $100K is easy to live on for most people, even as a sole provider with a family.

Another example is they are unemployed and looking for work. A lower paying job is better than no job, so they would already be digging into savings, so I would consider that a moot point. I would imagine that person would be more likely to stick around because they have to dig out of that hole and knows the sting of being unemployed. (It happened to me in 2001 and it sucked.)

It also greatly depends on where you live and what industry you are in. I happen to live in a low cost of living city.

Re:Rejecting a candidate for over-qualification results in a... by mooreds on Thursday October 12, 2017 @08:53PM (#15462576)
Thanks for the additional example and context. I guess the point that I'd take away (and another way to deal with this if I confront it) is to provide that context as the candidate, rather than letting the employer guess the context. Maybe it'd be good to confront it head on and say "I'm willing to take a pay cut because I'm a windows guy who wants to transition to iOS".
Re:Rejecting a candidate for over-qualification results in a... by Clubber on Thursday October 12, 2017 @09:08PM (#15462633)
You're welcome. It's all a game. Employers pretend like they can tell the difference between a good developer and a bad one during the interview process, and the candidate pretends like they can prove how good a developer they are in the interview process.

Whenever I interviewed (this was a long time ago) I would always take control of the interview. So when they would ask me about my prior projects, I would go on and on about them, enough so the person had a pretty good idea I knew what I was talking about.

The best antidote for being over the hill I have found is I usually ask friends first if they have any openings. They usually do and they will vouch for me. I also stick around a while: 6.5 year and 8 years for the last two. I make sure I push for new technology projects and make sure I do a good job so I'll get more. I really find the recruitment process distasteful.

A college friend of mine gave me the best advise for starting a new job. The first task they give you, make sure you bust your ass to get it done fast and well. That will set the tone.

Re:Rejecting a candidate for over-qualification results in a... by toomuchtodo on Thursday October 12, 2017 @09:52PM (#15462757)
> A college friend of mine gave me the best advise for starting a new job. The first task they give you, make sure you bust your ass to get it done fast and well. That will set the tone.

Underrated advice.