How would you build a job board?

Laravel + mysql. Runner up for Rails. I haven't found anything that provides the speed of development those two frameworks provide me.

Having built a job board myself for nearly 2 years, I would use an existing SaaS solution specifically for job boards. Sure, there will be a high monthly subscription, but it will save you a lot of time and effort you don't want to spend before you validate the idea and the market.

You can also use the API of Loopcv to collect jobs!
Find more here: https://www.loopcv.pro/developers

You can build this application with Softr + Airtable as #nocode solution. I built my first application https://www.apiland.xyz/ with the mentioned stack. You can try.

I would use the stack I am most comfortable with(React + Node + Postgres). Or start with something that doesn't scale. I.e., a simple site, and a Typeform for employers to submit job listings

I'm building it from scratch: https://remoteproduct.github.io/europeanstartups/

I feel I want something for the long haul, at that point a CMS inhibits how you continue developing it.

Having built both a headless job board with custom web API and then a rewrite using a traditional web app (server side rendered SSR HTML) I have tried two different approaches. Here is what I learned:

SEO is really important and you're much more likely to get traction using an SSR pages approach. Google doesn't always index headless sites well when content is injected into the DOM using client side JavaScript. When it does it takes longer to get listed. Keep in mind that jobs come and go quickly so you need to get them indexed as fast as possible.

With a static generated or SSR driven site you'll be able to inject Google Structured Data for jobs into each page and this will get your listed in their job specific listings.

JB sites require a lot of manual intervention, especially when they start off empty. I first begun by writing a command line tool that used Reed's API (Reed is a larger job/recruitment site in the UK). It scooped up jobs based on a filter and synced them to our local DB. I thought this would give us an edge, but this turned out to be a bad idea because the content in some of them was poor and the filters picked up jobs not related to the niche of the site. Some of the jobs has zero min and max salaries and this caused Google Search Console to grumble about malformed structured data. Since then my partner cherry picks jobs from other sites, manually adds them and tweets each job referencing the company. This gets recognition and the company get to know about us and often the tweets get bandied about (I have no idea of the details - believe it or not I've never sent a tweet lol).

Given that most of the jobs so far have been added manually to seed the site, it would have been better to write a really simple site with a job template and just maintained a bunch of YAML files - one for each job. This could even be pre-rendered with a custom static site generator.

Maybe it's the engineer in me, but I wouldn't reach for a CMS. I find I spent too much time learning new frameworks, platforms and other people's products instead of sticking to basics. I would be inclined to roll your own really really simple SSR site in whatever programming language is your go to language. I call it my "more of the same" approach. It's far better to write more of the same code (even if it takes slightly longer) than it is to shoehorn your job boards into a generic CMS. Just my opinion.

Is it a niche job board with a few 100 jobs or a huge one with 10,000s to millions?

If the 100ish can use a CMS like Versoly (founder here) it comes with search etc and great support from myself.

If you need 10,000+ then Remix sounds great.