For those who don't know (like me): https://instances.vantage.sh/aws/ec2/m6i.16xlarge?currency=U...

This is a VM with 64 vCPUs running at 3.5GHz, with 256GB RAM.

It presently costs about ~3USD per hour to run.

They have an API endpoint you can use.

https://github.com/HackerNews/API

This definitely would have been me.

I burned 100s of hours into my 400 level classes, some of those hours were completely wasted on things that I could never figure out how to get them to work.

If its helpful, that would be great!

The matching algo is very raw at this point, so if you find posts that _should_ have matched but didn't, please reach out (email is in my profile) and I'll see what I can do.

> But the optimal for those isn't to post a generic who wants to be hired but have a LLM rewrite your resume to match the job description isn't it?

If anyone was depending on this to actually make interview decisions, yes, that would be something a candidate might do. Fortunately there's not that pressure on this project. :D

This is something I'm considering. I was thinking we could probably hum it in with plain old vector embeddings, maybe?

I left an incomplete section in the post body, then went shopping.

So here it is:

---

Some observations when looking at the matches pair up right now:

- individuals looking for jobs have extremely general postings

- companies looking to hire have extremely specific postings

- generally, match scores are very low (<50%) because of this mismatch

- individuals don't typically mention domain knowledge in any specific way

- individuals don't typically mention prior work history beyond time-in-industry (this makes sense on a public forum)

- individuals typically list technologies used

I don't have any conclusions to make right now, no advice for job posters or job seekers. It'll take two or three more of these before I've seen enough to start gelling the domain problems in my head.

> It'll take two or three more of these before I've seen enough to start gelling the domain problems in my head.

I don't understand - there's years of historical data to look at?

I suppose I could look backwards instead of forwards.

Tbf, at this hour, it hadn't even occurred to me.

> Tbf, at this hour, it hadn't even occurred to me.

I am refreshed when I such honesty like this.

No defensive quip. No snarky response.

A gentle reminder that we are all human and we get tired and miss things.

I wouldn't bother unless you just want to try to compile stats. The active job seekers and the open positions from more than a month ago probably aren't valid today.

It's a bit like backtesting, in finance. Quite useful to establish whether your algorithm is sane and coherent, no use at all in determining if it is actually useful, to my understanding.

I'm confused. How do you figure this is a thing that needs to be done?

I guess this boils down to the Copyright of posts on HN, and what is considered to be fair use.

No, I'm not paying anyone. The compute is on my own dime and I'm not making any money off of this.

"quality" here is such an abstract thing.

There's a few metrics: seniority, salary range, enumerated skills (as requirements or as a person's skill set), and domain specific knowledge.

These are far from perfect, and I think in the future I will probably tweak how matches are scored, because how job postings are written and how 'Who Wants to Be Hired?" posts are at odds.

The former is one-to-many, where the job posting enumerates very specific requirements in order to filter that 'many' down to as few eligible candidates as possible.

The latter is one-to-many, where the 'I'm for hire' posting seeks to match as many of the 'many's as possible. This means down playing domain experience or specific technologies in order to appeal to as many possible viewers as possible.

Trying to pair 'precise and specific' with 'as general as humanly possible' is ... hard. Here we use 'tags' extracted from postings to match the domains and skills together. It isn't perfect. From what I've seen in this first run there aren't any matches that make it over 50% -- where 50% is a heuristic for the metrics mentioned above. This just means there's room for improvement.

The other side is the old game of 'tailor your resume to the job', which isn't in the spirit of 'Who Wants to Be Hired?' posts. You could very easily game this by just dumping a bunch of keywords into your post.

> I'm sure you mean well but as someone who has considered posting on who wants to be hired in the past.... this is creepy AF and feels like a giant invasion of privacy. If you did it privately, or authenticated people in some way, sure, but as is it feels like you're putting people on blast.

It's public information on a public forum. I'm not sure what the big deal is. There are lots of tools that do essentially what I've done here for various purposes.

> Also this sounds way more like an advertisement for "abacus.ai" than a side project announcement.

I have an account with them. I figured it was fair to say "I used this tool for vibe coding the idea". I suppose I could have left that out.

> Your post also starts a list of "things" ("Some observations when looking at the matches pair up right now:") with no list.

Yup. I got distracted before I finished writing the post. I'll enumerate those things in another comment here in a minute. Life prevails.

> Actually, nothing about this really feels good faith, or real.

I'm not sure what you mean. I made a thing, I shared it. I dunno what else you want from me.