1. 28
    1. 12

      After getting frustrated with existing job boards during my last job search, I set out to build a simple one that focuses on ease of use & privacy. This meant

      • No login or data collection (except for anonymous analytics)
      • Up-to-date data
      • Fast/easy browsing and filtering system
      • Save & export jobs to CSV

      Although there’s still many features I want to add (mostly around filtering/searching), I wanted to share this here to see if it’s useful to others and gather feedback.

      Thanks!

      1. 5

        From whence comes the data on these jobs? Do companies post jobs to algojobs specifically, or are you scraping other sites?

        1. 14

          At the moment, all content is scraped from companies’ career pages. Right now, I’m tracking ~12k companies, but hope to add more in the future.

          1. 2

            How do you compile the company database? This is important for the user to know.

            How does the scrapper work? Do you use machine learning to extract the job description from the webpages?

        2. 3

          Not to discourage you, but there’s too many job boards these days.

          Yours seemed potentially interesting, but the options locally (Hamburg) seem pretty limited. I wish you luck regardless!

          I think your current location filter is searching for where a job is located (which is good), but it doesn’t seem to account very well for states or for companies hiring elsewhere in the country/continent/globe.

          If I could wish for more filters in general (not necessarily for you, but for any job board):

          • Being able to filter where a job is located and where they are hiring would be nice. (justification: for visa reasons I can work in Germany for any German company, being hired by other countries is a more complex process)
          • Language requirement filter would help in cases like mine also.
          • Fulltime/parttime/contract/etc filters, maybe even a permanent or timed contract filter are also generally much appreciated.
          • Remote/hybrid/in-person filter is a must.
          1. 2

            Thanks for the feedback!

            I agree the local options are limited for now - I hope to improve this as I add more data. Adding “Remote” to the location box can be used in combination with locations - i.e Remote in Germany, but I should make that more clear. As you said, showing jobs near the selected location geographically could be useful too, right now it only uses what you select.

            The filters you mentioned are a great idea too. I actually have plans to add some of these, but I’m still prototyping ways to detect these with either an LLM or classifier, although some can be detected with text-search.

            1. 2

              All of these are good, A filter to remove positions with unlisted compensation ranges would be good, too.

            2. 2

              Looks interesting! Might be a good idea to add some logic to the query tags: what if I want to browse Go-related jobs that do not belong to the “blockchain” category?

              1. 2

                Will definitely add this, I also tend to avoid crypto companies. Exclusions can be good for tech/languages that people don’t want to work with as well.

              2. 2

                The title says tech-focused, but first N entries for UK are bartending jobs.

                1. 4

                  I’m still working on a classifier to strip out those jobs, but it works best if you add a job title or keyword for the time being, i.e Software Engineer in UK.

                  Fair feedback though, thank you for taking a look.

                  1. 3

                    Hey, if it worked for jwz…