Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hacker News “Who is Hiring?” top-level comments over time

blog.joewoods.dev

Post reply on HN
Print view View original

31–40 of 126 posts

Re: Hacker News “Who is Hiring?” top-level comments over time

#31

Post by cwkoss »

ryandrake wrote: post #18

I started and abandoned a little side project a while ago where I wanted to see which employers tended to have the exact same (or fuzzy-the-same) "Who's Hiring" post month after month. Goal would be to find some signal about which posts were actually resulting in hiring (in other words, the company didn't come back with the same posting) and which ones were just trawling for the same job month after month without act…

We tend to hire multiple developers in bursts, and recycle our text between months. We only remove the role-specific blurb if we hit capacity for that role.

So, not sure this methodology identify quite what you're looking for.

Re: Hacker News “Who is Hiring?” top-level comments over time

#32

Post by thedufer »

ryandrake wrote: post #18

I started and abandoned a little side project a while ago where I wanted to see which employers tended to have the exact same (or fuzzy-the-same) "Who's Hiring" post month after month. Goal would be to find some signal about which posts were actually resulting in hiring (in other words, the company didn't come back with the same posting) and which ones were just trawling for the same job month after month without act…

Companies posting every month could just as easily be continuously growing (or, I suppose, have consistent attrition problems). Most of the places I've worked at have had a perpetually-open listings for SWEs, despite regularly hiring them.

Re: Hacker News “Who is Hiring?” top-level comments over time

#33

Post by pcthrowaway »

speakspokespok wrote: post #17

Your blog post starts by discussing posts being down this month (June 2022) but the graph provided starts in 2011. For the sake of the discussion, a second graph that starts June 2021 to current, and in monthly increments would be more enlightening. Because ultimately I think that's what we all want to know. In your copious free time would you mind adding that? Thank you for writing this.

Here's a bar chart comparing "Who is hiring" with "Who wants to be hired" over the last year: https://jsfiddle.net/9d1f534b/

Re: Hacker News “Who is Hiring?” top-level comments over time

#34

Post by dekervin »

Since I spent a lot of time looking at "Who is hiring post" for fun anyway, I was looking for a way to make it productive and came up with a different idea [0].

I was wondering if you could detect the slow rise of a new technology and profit from it. Either by retraining or more directly, in the case of crypto, by trading on that info. I put together something, focused on a couple of crypto technologies and as luck would have it, it's still online !

[0] https://datum.alwaysdata.net/static/data-hnjob-trends/index....

Re: Hacker News “Who is Hiring?” top-level comments over time

#35

Post by Laforet »

polote wrote: post #30
paxys wrote: post #23

Earlier quoted context omitted.

A $5 DO droplet will easily handle peak HN traffic with a bit of optimization. Set cache headers, cache static assets on the server side (or even better, with an external CDN), or even cache the entire page if there's no dynamic content.

Even without optimization. Peak HN traffic is in the 20 req per second order of magnitude

Without optimization, Nginx defaults to allowing a maximum of one worker process with 512 connections and 60s timeout. 20 unique visitors per second will lead to 500 errors in less than a minute.

Re: Hacker News “Who is Hiring?” top-level comments over time

#37

Post by weird-eye-issue »

Laforet wrote: post #35
polote wrote: post #30

Earlier quoted context omitted.

Even without optimization. Peak HN traffic is in the 20 req per second order of magnitude

Without optimization, Nginx defaults to allowing a maximum of one worker process with 512 connections and 60s timeout. 20 unique visitors per second will lead to 500 errors in less than a minute.

Are you assuming each request takes a second, or how long? A blog should return fast enough that this isn't the case

Edit: Yes, even WordPress. Unless there are 50 plugins, an unoptimized theme, zero caching, and a resource constrained server.

Re: Hacker News “Who is Hiring?” top-level comments over time

#40

Post by LukeShu »

thedufer wrote: post #32
ryandrake wrote: post #18

I started and abandoned a little side project a while ago where I wanted to see which employers tended to have the exact same (or fuzzy-the-same) "Who's Hiring" post month after month. Goal would be to find some signal about which posts were actually resulting in hiring (in other words, the company didn't come back with the same posting) and which ones were just trawling for the same job month after month without act…

Companies posting every month could just as easily be continuously growing (or, I suppose, have consistent attrition problems). Most of the places I've worked at have had a perpetually-open listings for SWEs, despite regularly hiring them.

Yeah. I know the ~same text as the post that became my current job kept getting posted many months after I was hired.
Post reply on HN