Interviews as seen by HR and the candidate
-
Shocked Pikachu
People will work FOR MONEY!??!
- every HR team ever.
Ours tried to explain to project leaders that employees are not mostly interested in their salary, but in praise. That went over well.
-
I disagree because most people are applying for everything. So many people are putting in dozens of applications a day. "What resonated with you" is the fact that they're hiring at all. You can learn to love a job and find satisfaction in the work even if the company didn't "resonate" with you.
Sure. I wouldn't disqualify someone for being ambivalent towards what we're working on, but the person who seems interested is gonna be better to work with.
Likewise when looking for a place to work, if the tangibles are equivalent I'll prefer the place with better intangibles.
I'm not in HR or management, so I don't care about cost effectiveness or productivity beyond "not screwing me over". From that perspective, it's generally nicer to work with someone who finds it interesting than with someone who doesn't.
There's no point asking "why do you want to work here", because the answer is obviously a combination of money and benefits, and how food and healthcare keeps you from being dead.
I can't fault an interviewer who's clearly trying not to ask the obvious question and instead actually ask how the candidate feels about the work instead of disqualifying them for not volunteering the right answer.It's not unreasonable for an employer to ask a candidate how they feel about the work anymore than it's unreasonable for the candidate to ask about the working environment.
-
I disagree because most people are applying for everything. So many people are putting in dozens of applications a day. "What resonated with you" is the fact that they're hiring at all. You can learn to love a job and find satisfaction in the work even if the company didn't "resonate" with you.
Researchable before going there
-
Researchable before going there
So is my resume but they don't read it before the interview.
-
Look mate, I've been in Software Development for almost 3 decades, mainly in the Technical careed path (did some Project Management but, frankly, it's not my thing) and all the way to Technical Architect, in 3 different countries and most of it as a contractor, so I worked in quite a number of companies and work environment.
(I'm not trying to pull rank here, just showing that I've seen a lot)
In my experience, things like Enthusiasm are what bright eyed naive junior developers have: they're like me as a teen in the swiming pool having learnt to swim by myself and never having had lessons - intense strokes trowing water all over the place but moving very little for all that effort, or in other words lots of effort with little in the way of results.
Worse, Enthusiasm doesn't last forever and, further, most of the work than needs to be done is not exactly stimulating (if it was fun, people wouldn't have to pay money to others for doing it).
People who get at least some enjoyment of their work are good to have (and I'm lucky that after all these years I still get those moments of great enjoyment when at the end of doing something insanelly complex it all works), but in the real world most work that needs to be done is needed but boring so fun in that kind of task by itself won't be enough, plus such people are actually uncommon beyond the bright eyed young things, so if you want somebody who will actually deliver you results (rather than work a lot to achieve little) and you're not a prestigious company (say, like Google, which leverages their brand recognition to pull in such bright young things by the bucket load and drip them out drained of on the other side) and can't pay well above average, you're highly unlikely to get those kinds of people.
What you really want is people who have things like professional pride: they want to do a good job because they see themselves as professionals and feel a professional responsability to deliver good results in an efficient way that doesn't hinder the work of others.
I've seen over the years people with your perspective heading Startups or teams within small companies, and invariably they end up with unproductive teams filled with inexperienced people making all the mistakes in the book (and inventing new ones), enthusiastically. Maybe the people seeking such workers should've asked themselves what their real objective is in that: is it deliver the results needed by the company so that it prospers and grows or is it the pleasure of being surrounded by people having fun.
I'm lucky that after all these years still get those moments of great enjoyment when at the end of doing something insanelly complex it all works
I just think it's worth pointing out that that is an example of the work being engaging.
No one is so naive as to think that you work a job for anything other than money. The original post doesn't even seem to convey that it's bad to ask about the pay and benefits. It's saying that if, when directly asked, the candidate has no answer to what seems interesting about the job they might not be a good fit.
You seem to be an experienced software developer. You're easily qualified to do basic manual data entry. Same working environment, same basic activity. Would you be interested in changing roles to do data entry for $1 more salary?
I'm also a software developer, and I can entirely honestly say I would not, even though it would be less responsibility and significantly easier work.
Even the boring parts of my work are vaguely interesting and require some mental engagement.It seems there's this false dichotomy that either you're a cold mercenary working 9 to 5 and refusing to acknowledge your coworkers during your entitled lunch break, or you're a starry eyed child working for candy and corporate swag.
You can ask for fair money, do only the work you're paid for, have a cordial relationship with coworkers, and also find your work some manner of engaging.It's not unreasonable for an employer to ask how you feel about the work, just like it's not unreasonable for a candidate to ask about the details of the work.
-
I'm lucky that after all these years still get those moments of great enjoyment when at the end of doing something insanelly complex it all works
I just think it's worth pointing out that that is an example of the work being engaging.
No one is so naive as to think that you work a job for anything other than money. The original post doesn't even seem to convey that it's bad to ask about the pay and benefits. It's saying that if, when directly asked, the candidate has no answer to what seems interesting about the job they might not be a good fit.
You seem to be an experienced software developer. You're easily qualified to do basic manual data entry. Same working environment, same basic activity. Would you be interested in changing roles to do data entry for $1 more salary?
I'm also a software developer, and I can entirely honestly say I would not, even though it would be less responsibility and significantly easier work.
Even the boring parts of my work are vaguely interesting and require some mental engagement.It seems there's this false dichotomy that either you're a cold mercenary working 9 to 5 and refusing to acknowledge your coworkers during your entitled lunch break, or you're a starry eyed child working for candy and corporate swag.
You can ask for fair money, do only the work you're paid for, have a cordial relationship with coworkers, and also find your work some manner of engaging.It's not unreasonable for an employer to ask how you feel about the work, just like it's not unreasonable for a candidate to ask about the details of the work.
wrote on last edited by [email protected]Whilst I agree that it's nice to get people who do get some enjoyment from the work, I think it's unrealistic to expect to actually find it in senior professionals: maybe you'll be lucky, but don't count on it - such people need to have started with a natural knack for that domain, not having had all their enjoyment of that kind of activity totally crushed over the years by the industry (I'm afraid that over time having to do something again and again because it has to be done rather than because one wants to do it, crushes the fun out of any task for even for the most enthusiastic about it person), and not having been accepted or even demanded to get promoted to management as they became more senior because they were so good in the Technical side (were they'll most likely suck, but that's not consolation for you as they won't be available anymore).
It simply is very unlikely to find experienced people combining all those things.
Further, even if you do manage to find such people, don't expect that enjoyment of such tasks to be enough to drive an employee most of the time, since most of the work we have to do is generally something that needs to be done rather than something which is enjoyable to do.
If on the other hand you go for junior people who still retain their enthusiasm, you're going to be "paying" for them doing all the mistakes in the book and then some as they learn, plus if you give them the really advanced complex stuff (say, designing a system to fit into existing business processes) they're going to fuck it up beyond all recognition.
So statistically going for enthusiasm is and experience is like hoping to win the lottery.
If you do need to hire people with actual experience, it's more realistic to aim for professionalism as their driver of doing the work well and in time, rather than enthusiasm.
This is why, IMHO, asking people how they feel about the work is a bit silly unless you have yourself a truckload of recent graduates looking for their first job and you're trying to separate the gifted from the ones who went for it for the money (and there you're competing with the likes of Google and other companies with more brand recognition who will far more easily attract said gifted naive young things than the overwhelming majority of companies out there, so that too is probably not realistic an expectation)
I suppose Lemmy is frequented by older Tech professionals, hence the "you must be joking!" reaction to your idea that asking people how they feel about the work is in any way form or shape a viable way of finding good professionals.
-
Whilst I agree that it's nice to get people who do get some enjoyment from the work, I think it's unrealistic to expect to actually find it in senior professionals: maybe you'll be lucky, but don't count on it - such people need to have started with a natural knack for that domain, not having had all their enjoyment of that kind of activity totally crushed over the years by the industry (I'm afraid that over time having to do something again and again because it has to be done rather than because one wants to do it, crushes the fun out of any task for even for the most enthusiastic about it person), and not having been accepted or even demanded to get promoted to management as they became more senior because they were so good in the Technical side (were they'll most likely suck, but that's not consolation for you as they won't be available anymore).
It simply is very unlikely to find experienced people combining all those things.
Further, even if you do manage to find such people, don't expect that enjoyment of such tasks to be enough to drive an employee most of the time, since most of the work we have to do is generally something that needs to be done rather than something which is enjoyable to do.
If on the other hand you go for junior people who still retain their enthusiasm, you're going to be "paying" for them doing all the mistakes in the book and then some as they learn, plus if you give them the really advanced complex stuff (say, designing a system to fit into existing business processes) they're going to fuck it up beyond all recognition.
So statistically going for enthusiasm is and experience is like hoping to win the lottery.
If you do need to hire people with actual experience, it's more realistic to aim for professionalism as their driver of doing the work well and in time, rather than enthusiasm.
This is why, IMHO, asking people how they feel about the work is a bit silly unless you have yourself a truckload of recent graduates looking for their first job and you're trying to separate the gifted from the ones who went for it for the money (and there you're competing with the likes of Google and other companies with more brand recognition who will far more easily attract said gifted naive young things than the overwhelming majority of companies out there, so that too is probably not realistic an expectation)
I suppose Lemmy is frequented by older Tech professionals, hence the "you must be joking!" reaction to your idea that asking people how they feel about the work is in any way form or shape a viable way of finding good professionals.
So, I wasn't referring to enjoyment. I spoke of engagement or interest. It's why programming is more appealing than data entry.
You're just doubling down on the false dichotomy I spoke of. It's not at all uncommon to find someone with plenty of experience who can easily and honestly tell you why they think what the company they work for does is interesting.
Asking someone why they think working at the job they're applying for is appealing isn't "hiring for enthusiasm", and it's honestly odd that you keep casting it that way.
I get where you're coming from, and I partly disagree. It doesn't seem like you're parsing what I'm saying because of this "either one or the other" attitude though.
No offense intended, but it makes you come across as burnt out and sad. I don't work for small companies, with inexperienced people, and I'm not constantly shipping broken code that needs rewriting. I've been doing this for roughly 15 years and I can honestly say "working in security in general is interesting because it forces you to think about your solution from a different perspective, the attacker, and working at $AuthenticationVendorYouQuitePossiblyUse in specific is appealing because you get to work on problems that are actually new at a scale where you can see it have an impact".
That's not gushing with enthusiasm: it's why I'm not bored everyday. If you're actually just showing up to work everyday and indifferently waiting to be told what to do because it's all just the same old slog... That's sad, and I'm sorry. -
Ours tried to explain to project leaders that employees are not mostly interested in their salary, but in praise. That went over well.
As someone who works for a living: praise is nice, but pay is required.
... Fuck you, pay me.
-
The amount of underpaid/unpaid overtime I've heard of is terrible. At this point I will always ask if someone gets paid 1.5x if they're hourly working overtime, or if they're classed as salary exempt from OT pay. The former is blatantly illegal yet still happens often enough, while the latter can be legal but is usually taken advantage of with no compensated days.
Days in lieu, from working OT on salary.... IMO, is required.
I don't work for free; if you're paying me to be present for specific hours, regardless if it's salary or not, then I expect to work during those hours and not any other time.
If, as a salary employee, I'm paid for results and as long as I meet my deadlines (and deadlines are reasonable) I can work whenever, then yeah, I'll probably put in unpaid OT sometimes. I'll tell you something though.... With my level of experience, it would be unusual for anything to take so long that it requires that I work more than what is typical.
-
This post did not contain any content.wrote on last edited by [email protected]
I agree with the content of this post, but it seems like pure complaining rather than programmer humour, so I downvoted it for not suiting the community.
Mods, what are you doing letting this on here?
