Not even a new thing either. Barely any jobs are done because people want to do specific types of work, and those jobs tend to be severely underpaid (teaching, social services).
People didn’t flock to factories in the 60s and 70s because they wanted to work in a factory, they wanted the pay and benefits. Same for office work today.
IMHO, in Software Development it’s a good idea for a candidate to ask about the project, if only because any good professional would want to know if they’re a good fit or not.
Mind you, that makes sense in the Technical interview rather than with HR - no point in asking about what are the practical professional details of the work you will be doing from a person who doesn’t really have a clue (the HR person) when you know you will be facing an actual professional peer in a technical interview who knows the work that needs to be done in your terms and with the level of detail and understanding only domain professionals have.
In my experience doing the Technical Interview side of things (and most of my career I was a Contractor - so a Freelancer - which is hardly a “company man” with a rosy view of my relationship to them or somebody who thinks people work for fun), people who don’t ask about the project during the Technical Interview tend to as the interview proceeds end up get revealed as technically weak: an experienced “Engineer” would want to make sure they’re well matched to the kind of work they’re be doing (as well as, in my experience from the other side of the interviewing table, spot the messy fucked up situations before you take the contract so that if you can avoid ending in such disfunctional environments).
The thing is that that kind of information is usually in the offer. I’d be polite and and for confirmation and clarification but not everyone has that kind of tact and not hiring someone because they didn’t ask you to repeat what it’s written on the offer is kinda harsh tbh.
Let us not forget that there is not a single employer on the planet who would willingly hire and pay someone more for their time than that person’s time is worth. Each employee of a company is making that company money. They deserve comfort because they are the company.
I have a client who helps their personal out way more than they should. Even paying them extra so they can pay their tax debt.
Not that some of his employees deserve it, heck the one he paid the tax debt for is even leaving the company after this all happened.
Corporate bosses suck, small company bosses can be pretty decent depending on the type of company and how much money is being made. These are the companies that generally don’t have a HR deparment or a C level employee.
Comfort hunter is a very snobbish and entitled way to refer to someone offering their time and effort to you.
And wait, was the 2nd post ‘liked’ by the first poster?
That means that the HR account thinks what the employee account wrote is bad, too. Both posts are bad extremes.
As an employee, if i find a prospective colleague who doesn’t ask about what they’re supposed to be doing at all, I’d be wary of them, too.
To many people nowadays, the actual job itself doesn’t matter, it’s the fact that it’s a job and it pays.
Not even a new thing either. Barely any jobs are done because people want to do specific types of work, and those jobs tend to be severely underpaid (teaching, social services).
People didn’t flock to factories in the 60s and 70s because they wanted to work in a factory, they wanted the pay and benefits. Same for office work today.
Me c:
IMHO, in Software Development it’s a good idea for a candidate to ask about the project, if only because any good professional would want to know if they’re a good fit or not.
Mind you, that makes sense in the Technical interview rather than with HR - no point in asking about what are the practical professional details of the work you will be doing from a person who doesn’t really have a clue (the HR person) when you know you will be facing an actual professional peer in a technical interview who knows the work that needs to be done in your terms and with the level of detail and understanding only domain professionals have.
In my experience doing the Technical Interview side of things (and most of my career I was a Contractor - so a Freelancer - which is hardly a “company man” with a rosy view of my relationship to them or somebody who thinks people work for fun), people who don’t ask about the project during the Technical Interview tend to as the interview proceeds end up get revealed as technically weak: an experienced “Engineer” would want to make sure they’re well matched to the kind of work they’re be doing (as well as, in my experience from the other side of the interviewing table, spot the messy fucked up situations before you take the contract so that if you can avoid ending in such disfunctional environments).
The thing is that that kind of information is usually in the offer. I’d be polite and and for confirmation and clarification but not everyone has that kind of tact and not hiring someone because they didn’t ask you to repeat what it’s written on the offer is kinda harsh tbh.
Let us not forget that there is not a single employer on the planet who would willingly hire and pay someone more for their time than that person’s time is worth. Each employee of a company is making that company money. They deserve comfort because they are the company.
I have a client who helps their personal out way more than they should. Even paying them extra so they can pay their tax debt. Not that some of his employees deserve it, heck the one he paid the tax debt for is even leaving the company after this all happened.
Corporate bosses suck, small company bosses can be pretty decent depending on the type of company and how much money is being made. These are the companies that generally don’t have a HR deparment or a C level employee.
Heck they can also drive to you in a Volve stationwagen with the child like sun protectors on the windows that’s a clear sign they have kids as well.