Joblint – Test tech job posts for issues
joblint.org
joblint.org
There's the easy stuff: "ninja" for example. Nobody, in the year 2023, should be using that word in a job post.
But then there's the hard stuff that really matters. If you want someone who has experience being a "white hat" hacker, that's perfectly alright, but if you want "white people only" well that's obviously bad. If you don't flag the latter you look like a joke, but if you flag every instance of the word "white" then it feels overbearing and like the tool isn't very smart.
I'm pretty sure these will never actually be useful on a superficial word-matching basis. They need to look at broader phrases and context.
And then there's the real problem that even if the tool helps the hiring manager / recruiter sweep their inbuilt biases under the rug to get better applicants, they're still the ones making the hiring decisions.
Example: https://old.reddit.com/r/recruitinghell/comments/zkh9pf/anyo...
I've heard of multiple language and framework designers who failed to score a job when it really should have been a slam dunk. There might be rockstars among the foot soldiers of tech, but virtually none outside of that.
Relatedly, no US Marines have ever defeated a lava monster with a magic sword.
NO PIRATES, ONLY ROBOTS, WHO ARE CLEARLY NOT HUMAN AS WE ARE.
Why is "white hat" hacker inherently used to mean "ethical" or "good"? Most normal people wear black hats.
Seriously though, if learning the meaning of two (three if you throw in grey hat) terms is too difficult, never mind the rest of the requisite knowledge to meaningfully participate, you may want to consider an alternate area of study.
Yeah, anything that boils down to "you don't need to know about X, you just need to know that white X is good and black X is bad" is not a great look for technical terminology in the current context.
There are countless words and idioms that will make no sense when you're not familiar with them. You could consider these annoying, or you could consider these the interesting parts of a language.
I for one very much like words with interesting history.
I'm aware that I'm moving the goalposts a little bit, or at least making them more explicit. Sorry? Just trying to voice explicitly why my (admittedly subjective) stylistic sense is going "Eh, this one is better off replaced by explicit terms".
If you can't figure out how to google white hat, how are you going to figure out what the FHBTYU (made up acronym) is in your tech stack?
Perl nerds only!"
Zero issues reported.
There's such a striking lack of racist/homophobic rules that I'm almost willing to believe it's a satire project.
Edit: this got me -2: "We provide seeds to local farming communities to ensure they always have the green fields they need to supply their local markets."
I built Joblint literally 10 years ago as a fun side project. I was fed up with a spate of really terrible job ads and decided to write something to help me as an engineer vet whether I wanted to work at a company.
It's not a solid tool, it doesn't represent the way I'd build things now, and it codifies my fairly limited view of what made a bad job when I was a bright-eyed 20-something. I should probably add a note to the repo and site to express this but I'm always surprised when it gets dug up tbh.
If I were building it again then yeah it'd spot a lot more issues, it wouldn't be built using a massive RegExp , and it'd probably go harder on trying to spot red flags around homophobia and racism. I'm sure some of the foaming gammons here on HN would be overjoyed.
Anyway, see you all in another 10 years. Lots of love
> ...
> I'm sure some of the foaming gammons here on HN would be overjoyed.
The comments here don't feel that out of line that you need to be this defensive / thin skinned. It's an interesting idea, and worth expanding on, even if it's been languishing.
It's not the first time that this tool is discussed and, unfortunately, looking at the comments made in the past, I would definitely consider them out of line.
So I'm not surprised that the parent poster feels like that about this place.
When I started doing this, we had to teach people to watch for red flags like unpaid internships, companies with extreme turnover, or jobs trying to demand full-time employment but paying people as contractors without benefits.
In recent years, I feel like I spend more time talking people out of simple things they’ve determined are “red flags”, such as job postings that don’t use exactly the right words or interviews that don’t proceed exactly like the student imagines they should. In the past year, I’ve had students tell me that their “red flags” include things like any interview process that takes more than 1 hour total (this is for college grads) or any job that doesn’t pay FAANG level compensation, or any job that requires them to do any on-call for their own work. We spend a lot of time resetting expectations to get students aligned with healthy jobs that won’t take advantage of them, but nevertheless can’t match their unrealistically perfect ideals.
This tool has good intentions, but I’m afraid it might contribute to some of these unrealistic expectations about job searching. I often have to remind people that the job posting is never perfect and might be written by someone who doesn’t know how to write well. It might be written by an HR person who was copying things from some bad boilerplate text. You should always be wary of issues in job listings, but if you’re interested in the job it’s worth spending 20-60 minutes communicating with the company to learn more details first.
I’ve also noticed a secondary trend wherein some of the most toxic local companies have become very good at signaling: They know how to say all the right things in job listings, sponsor all the right events, and present themselves as exactly the “right” company to work for, but everyone who goes their ends up burned out and depressed by the toxic environment. Ironically, they’ve become experts at recruiting because they’re constantly recruiting to backfill their high turnover rates.
What I’m trying to say is: Be on the lookout for issues in your job search, but try to get the full picture before you rule companies out or select an employer.
> I need someone to inculcate my employees with rote
> identity politics without doing anything genuinely
> useful. Bonus points if they can also serve as a token
> minority hire.
and it passed with flying colors.
(pun intended?)
Also - kudos for open sourcing it. I look forward to contributing and using the library.
0: https://devscreen.io/inclusive-language-check 1: https://github.com/retextjs/retext-equality/blob/main/rules.... 2: https://github.com/retextjs/retext-profanities/blob/main/rul...
Edit: I have just noticed that this hasn't had any commits in 3 years, and no releases for much longer than that. OP: are you the author of the library? It would be good to hear what the plans are for it.
I think it's stupid for candidates to get through the interview process just to discover after many wasted hours that the salary range of the position is incompatible with their expectations