Job boards start easily, but you'd be surprised at how much they can spiral into some of the most convoluted code you've ever seen. They're almost the exact definition of a scope creeping CRUD app. This is compounded by the fast that an MVP job board is so low hanging that corners are often cut into oblivion, causing inescapable technical debt :)
I expect "We work remotely" was rooted partially in an attempt to burn down the old job board codebase and start over with more defined and scalable scope.
I started a bunch of niche job boards (pythonjobs.com, bigdatajobs.com, railsjobs.com, etc) using a 3rd party platform - but wasn't happy with the platform so built my own.
Fast forward blood, sweat and tears I now offer the platform as a SaaS offering for other looking to create niche job boards (www.JobBoard.io).
Starts out as simple CRUD - gets much more complex - especially when multi-tenancy is involved.
I expect "We work remotely" was rooted partially in an attempt to burn down the old job board codebase and start over with more defined and scalable scope.