That's maybe the point. It's very good. Looks good, feels good, and works well. It's a Show HN, which normally means provide critical feedback. If you have none, then it probably works well. Which it does!
Hah, not a growth hack from Indeed, but I appreciate you checking it out. Yeah, it's pretty basic right now. Just wanted to put it out there anyway and get some feedback as I continue to build it out.
Thanks for taking a look! It's definitely on my list of things I need to fix. Haven't decided what approach to take yet. At the very least I won't show locations that have no postings. A map is a potential option.
The challenge is when I pull from sites without robust apis that don't offer great location info. Some sites offer lat/lon but others might just say a city and some will even just say a region like "Greater New York City".
I thought the same thing but on scroll to bottom more entries were added in "infinite" fashion and as new cities appeared filter worked. Not ideal though.
Nice work! My first ever Vue.js project [0] had just basic functionality like this, but it was a great learning introduction to the framework.
The only thing I noticed was that the 'infinite scroll' seemed a little 'off'. Hard to describe, but the experience was a little jarring. I would scroll to the bottom and it looked like there were no more items, but then there was a short stutter, and more items were added. Perhaps a visual representation that this isn't the bottom of the list and that more items are below might make the UX experience better? Somthing like a faded out bottom of the last box on screen, or a simple '...' or down arrow below it if there are more?
Yep, thanks for picking that up. I did notice that during development, but put it down for a 'fix it later'. I did find the code snippet to prevent unrendered tags from flashing, but haven't incorporated them in there yet. Will do so in the next few days.
Appreciate the feedback. Yeah, it's a bit jarring. I might try executing the infinite scroll earlier so that it starts trying to load more before you reach the end.
Looks good. What are you using to get the jobs in the first place?
I recently wrote a scraper in Python using BeautifulSoup that scrapes TechnoJobs, Indeed and some others. It looks for keywords, does some other stuff, then sends the weekly results to my Slack channel.
You definitely make a good point. On the one hand, everyone who goes to look for jobs would love to use one site and feel confident that they're seeing everything available. On the other, it creates a lot of repetitive listings.
I'm planning to add more value with additional resources for prospective PMs and ultimately I'd like to have unique listings as well. I think aggregating other sites will help build the audience at first though. Otherwise, no companies would bother to share unique listings on the site.
Uh, what? That sounds horrible. Why would you want to be forced to check n job boards, filtering through hundreds of overlaps, to find the m << n unique opportunities?
Nice! The 3 main ways of getting jobs will be through APIs, RSS, and scraping, so I started out connecting to each type. Indeed and GoRemote API, Mind the Product's RSS, and scraping a few sites using Ruby & Nokogiri, which isn't actually in production yet.
Did you do the keyword filtering when you connected to the services (like pass a query to indeed) or parse the results after?
One of the challenges with Indeed is that there are so many results and it's hard to identify actual product jobs among the results. For example, Microsoft called their PM position "Program Manager", but if you search for program manager you get all kinds of other results that have nothing to do with tech or startups.
Sounds like a cool thing you build. I would like to use this. Please ping me on my email address - it is in my HN-profile. (You haven't put your email in your profile.)
It doesn't do a lot, and it's far from production ready! Some of the other stuff is just things like filtering out bogus salary ranges or doing the opposite to keyword finding and ignoring jobs that use lots of tech I don't know about. It's quite buggy and hacked together, I tweak it often.
I was thinking of using it to power a small UI like OPs, if I do I'll drop you an email. It's fairly easy using BeautifulSoup though, and was quite fun to learn! I'd encourage taking a look if you're a Pythonist.
This was the first thing I built with Vue. Found this Udemy course to be super helpful! Max does a great job teaching and Udemy runs their $10 promos all the time so it's not expensive either. Definitely worth it since there aren't that many comprehensive tutorials / articles out on Vue yet.
FWIW I built a little calculator project using Vue and Vuetify this summer and I really liked Vue's easy-to-run-with feel, but I couldn't jibe with how difficult Vuetify was to customize. Maybe I wasn't reading the docs correctly, or maybe it was my concurrent learning of Vue that made Vuetify seem obtuse, but I just found the whole experience frustrating. My god was the result pretty though. 7/10 would star on GitHub.
Yeah, I struggled with Vuetify a bit too. It looks nice, but I think a lot of the props could use more explanation and examples. The guy behind it recently announced that he'll be working on it full-time though, so I think it'll just continue to get better. Vue's super easy though. I've really enjoyed working with it so far.
It's the most basic project possible, made with a popular library, built with an external API that offers no additional functionality.
Sounds to me like a little growth hack from Indeed.