How do you vet mid level and entry developers? I know that sounds like a dumb question. But I only expect a mid level developer especially enterprise developers to turn well defined requirements into code. The bar is especially low in the age of AI. One is basically interchangeable for another. I have only interviewed senior level developers - ie people who I expect to operate on a higher level of scope, impact and ambiguity.
Those are easy to filter out via a few behavioral questions.
At that point the process starts to look a lot like the secretary problem you mentioned — you’re trying to make a decision with incomplete information and limited time to evaluate each candidate.
Surely you will not manage to hire one of the top 20 developers matching any given criterion unless you are paying too 1% compensation. (I made this number up.)
One of the criteria somehow is “will show up for work and not ghost us”.
No affiliation but they talked with me long time ago. They take upon themselves to perform the first screening… looks like something smaller startups could take advantage of. I am not sure how good they are.
I noticed with linkedin premium - when you view a job listing it tells you how many other people have applied akready, and what number of them have masters, bachelors, phd, director level, etc.
in this day, it should be a law that all the boards must post this info clearly - just to save us all a lot of time.
The amount of time I have spent putting info together for some job listings and wondered how in the heck they found someone else with the same experience and knowledge.. and to think, there may have been 1500 that applied before hand and literally none of that matters.
They have the data, they should have to post it.
Surfacing more of that kind of signal — instead of just the listing itself — seems like a step in the right direction.
Verification alone wouldn’t solve that, but one of the things we’re exploring is helping employers surface stronger matches earlier instead of forcing them to manually sift through hundreds or thousands of applications.
That doesn’t have anything to do with the fact that “generic developers” are a dime a dozen and it’s hard to stand out from the crowd using an ATS. I just said I had the same issue when experimenting with ATS’s.
This shouldn't surprise me, knowledge of a code base is a competitive advantage. But there is just something depressing about it. Maybe it being closed source and you having to learn it by being burned by undocumented behavior? Please tell more
I talked a little bit about Connect here:
https://news.ycombinator.com/item?id=47241412
I worked at AWS ProServe / their internal consulting department - full time blue badge RSU earning employee - and I was one of the highest contributors to a popular at the time open source “AWS Solution” around Connect and I had my own open source projects published under AWS’s open source GitHub organization.
BTW, I would never use the “solution” now. There are a lot better ways to do it post gen AI.
The thing was, it was years before AWS introduced APIs around Connect and even longer before they have CloudFormation support. I was the first to use those APIs at scale for clients and found and reported bugs to the team while I was there.
In many cases the challenge isn’t just finding a job posting, but finding one where that specific experience is actually valued or understood by the hiring side.
It’s less about closed code and more about experience with real deployments, edge cases, and integration patterns that only appear at scale.
The idea behind verified listings targets a slightly different problem — reducing scams, fake postings, or roles that were never actually open.
The volume issue you describe is real as well. We’re exploring an additional feature intended to ease that situation by surfacing stronger matches instead of turning every posting into a flood of applications.
Verification alone wouldn’t solve the competition problem, but it could make the job board itself more trustworthy.
A job being “verified” doesn’t solve the main problem post around 2023. Every single job opening gets hundreds of openings within the first day of it being opened.
If you are looking for a job as any type of generic developer - full stack, front end, mobile, back end, it’s almost impossible to stand out from the crowd. No, “I reversed a btree on the whiteboard to get into big tech as a mid level developer” doesn’t make you special.
If you do have a specialized set of skills that allows you to stand out from the crowd, you still shouldn’t be randomly spamming job boards and you should be able to sell yourself to someone at the company.
My personal anecdote. In my specialty - AWS + app dev + leading strategic initiatives, I’m very well credentialed (trust me on this) and in a certain niche of AWS, I was considered one of the industry experts at the time (again trust me).
But when randomly spamming job boards on a lark in 2023, I heard nothing.
That was always a plan B while I was waiting for what ended up being three offers via my network and one by reaching out to a company who specialized in my niche of AWS.
I’m not bragging, I am old. I should have a network and credentials.