Your rebuttal however feels very much from the company's perspective.
If the company squirms or is concerned because they're asked questions like this, I think it's actually worrying. Companies will ask why you stayed at a company for a short period of time. Asking about tools is a good way to evaluate how easy it would be to get things done: if a company won't spend an extra $2k on a new computer of your choice, it's not a good sign. Asking about work/life balance is the same thing: you won't get a definite answer but you should get a glimpse of if you'll be asked to travel across the country at the last minute on your daughter's birthday or not.
In the end, you won't get completely truthful answers but the way they are answered will give you hints. (and to be fair, interviewees also embellish their answers)
Asking "what's in it for me?" seems a fair question. Generally, the feeling is that the risk is on the company's part, but as an employee you might be wasting your time, your opportunities and later you'll have to explain why you worked for only three months at a company.
No no no no... I agree with the general tone of your post Edward, but strongly disagree with this. Anyone working in a field they have any possibility of working in again should never sign something that will complicate that. And the same with ownership of IP developed on personal time.
Once a company has made the decision to hire you they are invested in you. If you can't get them to bend on amending the contract don't sign it. Starting your own company is stressful enough without the possibility for an ex-employer to take legal action. Add that to the fact that people are much less likely to start a business in a field totally unrelated to what they currently do, and you have something that is entrepreneurial suicide.
I recommend asking to exclude any ideas developed on personal time OR not formally documented or manifested in specs or code.
You don't want to be worried that if you have a conversation with a colleague about some problem which sparks an idea for a product that just the vague idea becomes company property.
Any of your ethereal ideas that your employer doesn't execute on should never be at risk of getting claimed later if you decide to do something with them. Get that in writing before you start.
That said, overly restrictive non-competes tend to be unenforceable, but I agree you don't want the hassle of a legal fight even if you ultimately prevail.
But for a professional developer/engineer position for with minimum severance it's completely unreasonable. It's like asking a lawyer to not practice law for a year after leaving a firm, or a doctor not to practice medicine for two years after leaving a partnership. That's your bread & butter, how you feed your children, and the idea of asking someone in that situation not to ply their hard-earned skills in their trade is nuts.
The only exception would be, and I personally agreed to this at my first job after graduating from college, is if the company provided an extensive training program that taught you all the skills you know. My first company provided three months all-day classroom/lab training while paying us full wages, then an additional three months of mixed OTJ and classroom/training. I was Econ grad and they taught us app development, and then asked us to sign a 1-year NCA that started on the date our training officially ended. They just wanted to make sure they didn't make a huge investment training people (and paying them full salary during training) who would then jump over to a competitor right afterwards, which was totally reasonable.
Later, another company asked me to sign an NCA that would go into effect my last day of work with them, but offered no training, professional development, or year-long severance. I and another new developer sat down with the CEO and explained the above, and she cancelled the whole program after realizing our side of it, which was very cool of her.
So yeah, it depends on the situation, type of employee, etc.
In practice I no one cared what their phone goons did after they left, but I suspect it was applied to everyone they hired, either directly or through outsourcing (like I was).
In fact, after the outsourcer lost the contract several of the people I worked with immediately went to do phone support for Samsung or Motorola (all three were in the same building).
What's wrong with that? If I'm being hired on with a salary, that's my expectation. They can ask me to work extra, but they can also pay me to do that.
I've been under the assumption that by going on salary, you pretty much forfeit your right to get paid more(forget bonuses for a moment) if you work more hours. Conversely, you will still get paid for 40 hours of work even if the week is slow and you only really needed to do, say, 36.
Investment bankers work 60+ hrs/wk and make $200K a year and get massive bonuses. Most of them are mercenaries who will go wherever they can get the best comp, because what they're selling is the opportunity for the bank to generate profit from their ideas/network whatever. (Please try to read the previous without getting wound around the axle about financiers moral value.)
So, to the extent that you view yourself in the business of "selling value I create," then a few things follow... 1) you'll want highly measurable criteria for success, 2) you'll want comp that is highly meritocratic, and 3) and hours worked don't matter much at all.
Clearly, this post was geared to people who view themselves as being in the business of selling their time, not their value.
I ask because these questions all would have thrown up a red flag at my previous company, where within 2 months I found myself trying to run a very specific old version of Eclipse (so they wouldn't have to pay for the non-free version of a plugin) on a 10 year old desktop (with a keyboard and mouse I bought myself), on completely unreasonable schedules, embarrassed to leave before 10pm, with no programmers left that I could ask any questions, and at least mildly concerned about whether the non-compete agreement would prevent me from taking another job in Japan.
Being terrible at interviews as I am, I failed to ask enough questions for fear of leaving the kind of bad impression you describe, since I saw myself as having few alternatives as a fresh grad in a bad economy, and convinced myself that the offer was a pretty good deal. There must be a way to at least get some indication that a company isn't going to make me beg for scraps without coming off as unhireable.
> You don't like when they ask, "Why did you only stay with Company X for 3 months?" They'll feel the same way.
Actually I do like it when they ask. It gives me a chance to explain my position. Heaven forbid somebody's feelings get hurt.
> This question shows lack of initiative
How does a question about the company's business show lack of initiative? It shows the candidate is at least thinking about the bigger picture and future.
> just assume that the answer to this question is "Yes" and sign it.
Honestly, I cannot believe you are saying this seriously. Never, never, never just sign something.
>Ask not what the company can do for you, ask what you can do for the company.
When you are interviewing someone, are you really following your own advice and thinking "What can I do for this candidate?" while ignoring your own company? I sincerely doubt it. The whole reason you are looking to hire is to get a ROI on the person.
I say all these as someone who has asked tough questions of my interview, been hired and then been told "we hired you because we liked the questions you asked of us during the interview."
They're important data, though. Probably best to wait until you've got an offer in hand.
The candidate has the most power in the hiring process between the moment they have received an offer and before they have given a decision. The company at that point has invested a lot of time and money into the process and you are their number 1 choice.
This would be the best time to ask any "iffy" questions or to push back on any of the points they brought up which you had issues with.
“How many clients has the company added in the past year?”
I would prefer trying to assess growth rates outside the interview. In many cases, you should be able to get an idea some other way. This question shows lack of initiative. And, in many cases, the interviewer may not even be permitted to answer it.
“What has the employee turnover rate been over the past 24 months?”
Too much focus on the negative. You don't like when they ask, "Why did you only stay with Company X for 3 months?" They'll feel the same way.
“What’s the company’s policy on work/life balance?”
You might as well say, "I intend to deliver 40 hours of my time for 40 hours of pay. If you need extra help, ask someone else. Big turnoff.
“What kind of tools are provided to help me do my job?”
Better: "What kinds of things do you need me to do to help the company achieve its goals.
“In the first 60 to 90 days, what’s my first priority?”
Actually, this is a great question. It can paint a good picture of your life and shows that you're ready to get to work.
“Are employees required to sign a non-compete contract?”
By asking this, you are identifying yourself as a problem. If someone asked me this question, the first thing I would think would be, "What is he up to and what is my risk?"
For technology companies, just assume that the answer to this question is "Yes" and sign it.
When interviewing someone else, I appreciate good questions. They show interest and possibility. But I get a bit concerned when too many questions are of the variety of "What's in it for me?"
I think it's always a better idea to present yourself with President Kennedy's attitude: "Ask not what the company can do for you, ask what you can do for the company." Find a way to present yourself that way while still learning everything you need to know.