Churn rate at the company and if there are people who left their phone number as references.
Ask HN: What info do you wish every job posting included?
41–50 of 85 posts
Re: Ask HN: What info do you wish every job posting included?
#42Salary, location.
Re: Ask HN: What info do you wish every job posting included?
#43Salary range, description of office environment (and/or actual pictures), remote work policy, expected hours, dress code, tech stack details, some details on what the project actually is , and a quick "Joel test" like summary of the current development practices. Also, a note indicating whether or not managers refer to people as "resources". Also, the name of the actual development methodology (if any) that is in use…
> Also, a note indicating whether or not managers refer to people as "resources" This made me chuckle. It's a pretty accurate measure of a companies culture though.
It's a pet issue of mine. I feel very strongly that a "resource" is something like a backhoe, a stack of lumber, a pallet of widgets, a computer, a building, etc. A person is... well... a person, damnit.
Calling people "resources" and treating them as fungible, disposable, commodities is extremely dehumanizing and is emblematic of the typical corporate newspeak bullshit that some people use as a dodge to avoid facing the fact that their actions affect actual people.
Re: Ask HN: What info do you wish every job posting included?
#44Visa sponsorship
Re: Ask HN: What info do you wish every job posting included?
#45Besides the obvious, I'd also like to see:
- Salary range for that specific position (not for the whole department (I've seen that))
- Remote work policy
- Visa sponsorship policy
- Vacation policy
- Interview process
- Link to future manager's technical background
Re: Ask HN: What info do you wish every job posting included?
#46How many people have work on the position before
Re: Ask HN: What info do you wish every job posting included?
#47Salary range, description of office environment (and/or actual pictures), remote work policy, expected hours, dress code, tech stack details, some details on what the project actually is , and a quick "Joel test" like summary of the current development practices. Also, a note indicating whether or not managers refer to people as "resources". Also, the name of the actual development methodology (if any) that is in use…
+1 for salary range. It's bizar that some companies require you to first go through the entire interview process and only do the salary negotation at the end. At which point you might find out that there never was a possibility for a match and you both have wasted your time.
At which point you might find out that there never was a possibility for a match and you both have wasted your time.
Exactly. It's ridiculous to do that.
What's arguably even worse is when you know that the company knows what your salary expectations are ahead of time, and they still go through the entire process, and then at the end either come up with an offer that's way below your bar, or decline to make an offer because "paying you that much would create a disequity on the team". Yeah, I got that last one once... AFTER going through two rounds of interviews. I'm thinking "if you knew you weren't willing to pay me what I was looking for, why did you waste hours of my time interviewing?!??"
Re: Ask HN: What info do you wish every job posting included?
#48Since I am a functioning adult and therefore have various obligations outside of work, I need an unambiguos breakdown of salary, holidays, overtime, flexitime and pension.
You can choose to be coy about it, but you will have to tell me eventually, so you might as well let me know up front. It will save time for all of us.
Re: Ask HN: What info do you wish every job posting included?
#49These are all great questions to ask in interviews for newbies as well.
Re: Ask HN: What info do you wish every job posting included?
#50Salary range, description of office environment (and/or actual pictures), remote work policy, expected hours, dress code, tech stack details, some details on what the project actually is , and a quick "Joel test" like summary of the current development practices. Also, a note indicating whether or not managers refer to people as "resources". Also, the name of the actual development methodology (if any) that is in use…
In addition, a summary of the hiring process.
The standard one-line HN Who's Hiring summary is also more informative than most the boilerplate crap I come across. Example:
> FormulaFolios | Full-Stack Rails Developer | Costa Mesa, CA | ONSITE Full-Time | $80k-100k
As a hiring manager, I've put a great deal of thought and effort not only in our job posting but in our whole process. It requires extra effort for sure, but having been on the other side of the process and suffered the many indignities of job hunting, I try to be spare our applicants from them as much as possible.
This means responding within 48 hours to any applications and notifying applicants when they've been rejected for consideration as soon as possible. These messages are all templated but I tailor them to each candidate.
Since I take some pride in our job postings, here's our most recent one:
https://stackoverflow.com/jobs/172538/full-stack-rails-devel...
(We're closing it soon so link will probably be dead by end of the week.)