Live data from Hacker News

Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

tamerc.com

81–90 of 173 posts

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#81

Earlier quoted context omitted.

Read the second part of what they said > it's hard to verify without code because there are so many false positives for "go" on any post. Hence grep being insufficient in this case.

You can’t really trust that the LLM gets it right either, though.

It didn't. As noted elsewhere, there the bubble cloud has Vue.js and "Vue Js", among others.

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#82

This is very neat! Thanks for using your time and literal dollars to work through this! As an added detail regarding the "remote" v "in-person", another interesting statistic, to me, is to know how many of those in-person job-seeking companies are repeats! It could absolutely mean they're growing rapidly, OR it could mean they're having trouble finding candidates. Equally, missing remotes could mean either they're ge…

We're a growing B2B company in Norway. We struggled for years to fill in-person positions. We've been at least 2-3 devs short for the past 6+ years.

That is, until December last year. Then it was like a flood gate had opened up. Suddenly we had tons of candidates to try to select from.

I knew things were bad over in bay area and such, but I didn't expect it to hit the market over the pond here so quickly and abruptly.

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#84
I think it's bad to stack bars in a graph, because it means you can't properly gauge the second layer (for example, the remote jobs quantity, at the beginning of the results section). Better to have two bars side by side (for each timestamp), one for remote, and another for not remote.

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#85

This is very neat! Thanks for using your time and literal dollars to work through this! As an added detail regarding the "remote" v "in-person", another interesting statistic, to me, is to know how many of those in-person job-seeking companies are repeats! It could absolutely mean they're growing rapidly, OR it could mean they're having trouble finding candidates. Equally, missing remotes could mean either they're ge…

We're a growing B2B company in Norway. We struggled for years to fill in-person positions. We've been at least 2-3 devs short for the past 6+ years. That is, until December last year. Then it was like a flood gate had opened up. Suddenly we had tons of candidates to try to select from. I knew things were bad over in bay area and such, but I didn't expect it to hit the market over the pond here so quickly and abruptly…

It is getting more and more apparent that BLS has been cooking jobs numbers.

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#86

Cool analysis with GPT-4o! I was doing some messing around with the same dataset recently around the "Who is Hiring" and "Who wants to be hired". Although I was just using pandas and spacy. (I was job supply and demand with the US FED interest rates here: https://raw.githubusercontent.com/bobbywilson0/hn-whos-hirin... ) I can actually see how nice it would be for an llm to be able to disambiguate 'go' and 'rust'. How…

I've been working on similar functionality for jsonresume -> https://github.com/jsonresume/jsonresume.org/blob/master/app...

What the author could have done, and what I should have (but didn't) also, is add a bunch of possible values (enums) for each possible field value. This should solve it from coming up with variations e.g. node, nodejs

In zod/tooling it would look like this; remote: z.enum(['none', 'hybrid', 'full']), framework: z.enum(['nodejs', 'rails']),

But this just shifts the problem further down, which is now you need a good standard set of possible values. Which I am yet to find, but I'm sure it is out there.

On top of that, I am working on publishing a JobDescription.schema.json such that the next time the models train, they will internalize an already predefined schema which should make it a lot easier to get consistent values from job descriptions.

- Also I tend to forget to do it a lot recently in LLM days but there are plenty of good NER (Named Entity Recognition) tools out there these days, that you should run first before making robust prompts

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#87
post #6

I wonder how this would compare against a random sample of jobs on, say, Indeed or LinkedIn. My experience of Hacker News is that it’s a very biased group (in a good way) to the general industry.

I've had few interactions with HN crowd as I've posted my availability for consulting/freelancing and I feel like I don't like the bias. People needing freelancers for few weeks/months to complete projects where the requirements are glueing the usual APIs and solving the usual Safari bugs asking me Leetcode questions are out of their mind. I am not applying for a full time position, I'm not a cofounder that is going…

I assume there are specific Discord servers per ecosystem? How do you find those?

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#88
post #6

I wonder how this would compare against a random sample of jobs on, say, Indeed or LinkedIn. My experience of Hacker News is that it’s a very biased group (in a good way) to the general industry.

I've had few interactions with HN crowd as I've posted my availability for consulting/freelancing and I feel like I don't like the bias. People needing freelancers for few weeks/months to complete projects where the requirements are glueing the usual APIs and solving the usual Safari bugs asking me Leetcode questions are out of their mind. I am not applying for a full time position, I'm not a cofounder that is going…

Mind to share the discord server/link?

Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o

#89

I think it's bad to stack bars in a graph, because it means you can't properly gauge the second layer (for example, the remote jobs quantity, at the beginning of the results section). Better to have two bars side by side (for each timestamp), one for remote, and another for not remote.

Stacked bars are the right choice when you care more about the magnitude of the sum and less about the precise relative breakdown. Separate bars are the right choice when you're comparing multiple things that are similar and their combined magnitude isn't meaningful.
Post reply on HN