In an ideal world, this would be a union.
In (what I worry might be) the real world, the word union conjures unhelpful barriers to action.
I'm less interested in fighting idealogical battles. I'm more interested in achieving a practical goal - getting a large group of people to say no to leetcode.
My guess is more people will say no to leetcode if they think of it as a general group anyone can join. This allows a larger amount of people to ignore idealogical barriers they might have to joining. So for now it's a "group/job board".
I agree with you that the trend of asking Leetcode (or any rote-learning) style problems hurts candidates. I have no moral problem with software engineers bargaining collectively to reverse a trend that is harmful to the industry.
That being said, I think there is a tendency for organizations created around a cause to find themselves rudderless when that cause is finally achieved. The urge to not disband and instead look for another cause is often too strong, even if they don't feel quite as strongly about the new cause.
I genuinely would like to know how traditional unions obtained their negative stigma. My guess is they were started with equally noble aims.
In this case it happens that people who are good at rote-memorization problems probably aren't the best people to lead the industry. But the union doesn't exist to serve the industry, it exists to protect the people working in it.
I assume you mean LC to be a stand-in for the types of interviews that focus on LC-style questions? LC didn't invent these and they're certainly not to blame when companies ask senior SWE candidates to invert binary trees.
Is there another, more general term I could use? I'm looking for a term that would be as clear to as most people as possible.
I don't think LC is entirely useless, I've seen people graduate with CS degrees but couldn't do fizzbuzz. But the prominence of it for certain interviews is frustrating in many cases.
There is no solidarity left : earlier this year my country ( NL ) threw all elderly under the bus ( we have no room for you on intensive care ).
You know what happened? They got scared. That was all.
I remember the 80ties : all unions would have united and the entire country would have revolted.
The data could be community-driven, but of course that risks sufficiently big players fudging the input data (sort of like the fake reviews on e.g. Amazon). Even so, it may be possible to detect which companies are faking it.
This site would basically be the same list - with the added goal of explicitly filtering employees and employers who want to hire this way.
I respected that decision but it none of those engineers every got hired by companies I was working with. They all had jobs already so clearly that was fine with them but it seems like there needs to be a better alternative.
One developer would ask what the role entailed, then find a relevant job/project that showed he had done similar work. That was helpful but obviously only works if you have a longer career with many projects to pull from.
There are a lot of “experienced” engineers out there who don’t know how to tie their shoes once they’re out of their comfort zone. Try interviewing people, you’ll see.
Why does it need to be a group? Refuse to do them, explain why, and move on to the next company. Talented developers are in high demand. There are plenty of other opportunities.
If you're the type of job seeker who has no objection to leetcode, you wouldn't join. And if you're the type of employer who refuses to do anything else, this would be the last place you'd look for hiring.
The goal is to publicly show employers how many "refuseniks" there are. The situation right now is that refusal only happens privately and anecdotally.
"If you're the type of job seeker who has no objection to leetcode, you wouldn't join. And if you're the type of employer who refuses to do anything else, this would be the last place you'd look for hiring."
This is very well said and exactly what I'm hoping for.
"The goal is to publicly show employers how many "refuseniks" there are. The situation right now is that refusal only happens privately and anecdotally."
This is exactly the goal and what I'm hoping to improve.
If it's just a niche job board then that's not an issue, but it also seems like one of those things that should have been done already, probably has been, and isn't popular for a reason.
A public group actually makes it easier for people to avoid defecting. It's very difficult for a job candidate to talk to employers about this when you're just some lone weirdo with idiosyncratic principles. It's much easier to have that discussion when there's a public group of people you can point to with the same principles. There's strength in numbers.
Consider it a kind of "Alcoholics Anonymous" for interviews. You wouldn't say that can't work because people defect. Yes, people defect and drink again, but they joined AA in order to avoid drinking, and the purpose of the group is to help them with the goal of not drinking. And also to remove the private shame of admitting a problem, by showing publicly that it's a very common problem. This is not a perfect analogy by any means, but the gist is similar.
I'm interested in raising the incentive for people to say no.
I'd do this by offering another job board for people who aren't likely to leetcode anyway. I would tailor it to people with great open source projects/ experience that might get looked over in a more traditional interview.
This seems like a classic coordination problem. If enough people refuse, companies will have their talent pool limited.
We could use this group to help match companies and developers who don't want to leetcode.
If it's true that leetcode filters out great developers, than companies who 'can't find talent' should be able to use our group to find some. In fact, it could be a great sign of how willing the company is to think against the current hiring zeitgeist.
Edit: Here's a quickly built site. say-no-to-leetcode.netlify.app