Please read the below if you are planning to post here and would like to have your offer looking good on the map.
I've been doing this since August last year, both parsing the thread and adding this comment here. But this time I would like to only slightly improve one thing: the format.
First, I would like to say that I really like that this thread is one of the few places where hard format for jobs isn't required. The format change that I'm asking for is minimal and a lot of people already post their posts in similar or exactly the same format.
What I’d like to ask is for the format of the first line to be like this:
1) {company} | {job title} | {locations} | {attrs: REMOTE, INTERNS, VISA, company url}
Google | Software Developer | SF | VISA https://google.com
DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA
or
2) {company} | {job title} | {locations}
Google | Site Reliability Engineer | London, Zurich, Sydney
Facebook | Web-developer | London, Zurich
You can test it in Python or here https://regex101.com/r/relwQD/3 (for match look right). What if you do not comply? Absolutely nothing. I will continue to do my best to parse your job post as it is.
To HN moderators. Apologies for highjacking the thread. I'm getting really positive feedback about what I'm doing here. I just want to improve this one thing.
Seconded :). Also upvoted every post I found that shown a salary range. Let's make it more appealing for announcers to disclose the offered salary. Please upvote the posts where a salary or salary range is advertised.
That's a wonderful site/service. I find the UI very clean and attractive but of course that's subjective. I really enjoy map-based data visualizations. It's particularly interesting to me to pick out the middle-of-nowhere companies and try to imagine why they were founded where they were, given the hiring, logistics and (I would imagine) the funding hurdles that would have resulted from the decision. In my experience talking to a few such founders, it's often a matter of "dammit, I love it here, this is where I'm going to start my business, and let the chips fall where they may" ... an attitude I find admirable.
Who'd have thought there'd be so many gigs in Remote, Oregon? :)
I was surprised by the number of jobs near where I live - until I realized they were all in the town of Remote, OR. Sorry that my state abbreviation is also a word.
I'm not handling a salary right now. But it looks like I should. I will try to do something about it.
Just a note. To have the search enabled on a salary, values have to be normalised to something, dollars sound good to me.
As for the keyword. This is something probably HN crew could decide on. In my opinion isn't needed as long salary is in first row with $xxx or $xxx-$xxx format. But since many people seems to be interested here. Maybe would be good idea to mention something about salary in the thread description.
What would we do with multiple job offerings? It gets pretty unreadable quickly if we have more than one or two jobs on offer, if we follow that spec.
What if we added a regex test against the post body?
> It gets pretty unreadable quickly
Yep. That and the Regex also breaks down very quickly / easily. I tested 5 jobs listed in this thread after OP's post with Regex. Only 1 got it right (20% success rate)
Here's the one from the Binti job listing in this thread. The regex determined that title` is `San Francisco, CA` and the `locations` is `Software Engineer`
- Use window.location.replace() until the text box loses focus, or the list is scrolled, or for a bit of time, or something to indicate that the user has finished typing out a query, and then use window.location.assign()?
Navigating back immediately replaces the query in the url with what's in the textbox making back useless, and the history has a ton of entries (one for each character typed). Without those changes, navigating back is a painful experience, but with them it should be significantly easier.
Yes, the broken back behaviour is the really serious negative with this map. I had to abandon my browser tab to go back to hacker news to complain about this! Please fix it! :)
Wow, didn’t expect that my comment will have this amount of attention. Thanks for the comments here and all the emails.
As for the format. Many people actually used used the format. 182 posts matched the format. As a result those post are displayed on https://whoishiring.io with correct company name, location and thanks to ClearBit Logo API even logos. As for the rest I was doing my best to get them in the proper form as well.
Seems not to work on my iPad. I hit enter after filling the location field and the page just reloads. Also, e second input field shows something like {{placeholder}}.
From the site's <META> tag, it looks like they are scraping ( i.e. "aggregating") other sites also.
> <meta name="description" content="The map with the collection of jobs for Software Engineers, Software developers, Programmers, Designers and remote. Aggregator of job post from Hacker News, Stack Overflow, Github, and many more ...">
https://whoishiring.io
Please read the below if you are planning to post here and would like to have your offer looking good on the map.
I've been doing this since August last year, both parsing the thread and adding this comment here. But this time I would like to only slightly improve one thing: the format.
First, I would like to say that I really like that this thread is one of the few places where hard format for jobs isn't required. The format change that I'm asking for is minimal and a lot of people already post their posts in similar or exactly the same format.
What I’d like to ask is for the format of the first line to be like this:
or I will be using this regex to test the firstline. You can test it in Python or here https://regex101.com/r/relwQD/3 (for match look right). What if you do not comply? Absolutely nothing. I will continue to do my best to parse your job post as it is.To HN moderators. Apologies for highjacking the thread. I'm getting really positive feedback about what I'm doing here. I just want to improve this one thing.
Feedback welcome.