Created a Job Board Because I Was Tired of Lying Job Boards
A few weeks ago I was hacking around with Claude Code in Visual Studio.
Job boards will say “remote” but when you drill into the detail, you find that whilst a role will say “remote” in the title, it goes on to say “3 days in the office” in paragraph four.
I decided to vibe a simple web app that lets you find 100% remote gigs.
Not “remote-friendly,” not “remote considered,” not a listing that says remote in the title and “3 days in the Leeds office” in paragraph four.
Contract and permanent .NET work, genuinely remote, pulled from a range of sources into one page. Closer to the truth than any single job board gives you, even if it’s not perfect yet.
~
The Itch
Every general job board treats “remote” as a vibe rather than a fact. You search, you get forty results, and twenty of them are hybrid roles that just happen to mention remote somewhere in the copy. Multiply that across the boards you’d need to check to get real coverage and the search itself becomes the job.
Full transparency – this isn’t a platform. It’s a console application that harvests job data using free APIs and two static web pages that let you view jobs and stats about jobs that have been ingested.
It saves you time.
Most of it got built talking it through with Claude Code.
~
What This Does
Some key points on what this tool does:
- Pulls from eleven sources – RemoteOK, Remotive, Arbeitnow, Himalayas, Jobicy, Working Nomads, WeWorkRemotely, The Muse, Adzuna, Reed and Careerjet. Eight need no API key at all; three need a free one you register for yourself.
- Matches on
.NET/C#/ASP.NET/Blazoror AI/ML terms –LLM,generative AI,machine learning,agentic AI– as two separate categories, not an intersection. A pure AI role with nothing .NET about it counts too, which matters more to me now than it would have a couple of years ago. - Only matches on the title and tags, never the description. Job boards pad every single listing with “…React, Golang, PHP, Vue, .NET…” regardless of what the role actually is, and that’ll false-positive on roles with nothing to do with either category if you let the description in.
- Tags every match with a work mode –
100% remote,hybrid,onsite, orunknown– rather than silently dropping anything that isn’t remote. First version of this only surfaced 5 jobs, and I didn’t know why until I built a Stats page to look. Out of 582 raw postings that run, 13 were genuinely relevant after dedupe. The filter wasn’t broken. Remote .NET roles are just a thin slice of any given day’s market, and now the tool shows you that instead of hiding it.
There is no backend and no database. The tool writes flat jobs.json + stats.json files then reads them client-side.
~
Two Pages, Nothing Else
There’s the search page – title, company, tags, search box, country/work-mode/comp filters, sorted newest first by default:

There’s also a “Stats” page, linked off the top of that one. This exists because the “only 5 jobs” moment made me curious:

That’s the whole surface area. No settings page, no accounts, nowhere else to click. Clean and simple.
~
Why Non-Remote Jobs Are In Here Too
The obvious move for a “100% remote” tool is to just throw away anything that isn’t. That’s what the first version did, and it’s also what made it nearly useless – 5 jobs on a good day, with no way to tell whether that was the filter being strict or the market actually being that thin.
Maybe that’s a signal of where the industry is swinging back to, or maybe it’s just poor job descriptions.
Keeping hybrid and onsite postings, tagged rather than deleted, answered that question for me. The Stats page can only show “582 raw, 13 relevant, 5 remote” because the other work modes are still sitting in the data instead of having been thrown away before anyone got to see them. It also costs nothing on the default view – 100% remote is still the default filter, and nothing that used to show up has stopped showing up.
I’d rather show the full picture. The filter lets you decide what you want to see.
~
Classifying and Tagging Work Mode
Work mode used to be a hard filter – hybrid and onsite roles just got thrown away before you ever saw them. Now it’s a classifier instead, and every match gets kept and tagged:
public static WorkMode Classify(RemoteTrust trust, string combinedText)
{
if (trust == RemoteTrust.TrustedRemoteOnly) return WorkMode.Remote;
if (LooksHybrid(combinedText)) return WorkMode.Hybrid;
if (LooksOnsite(combinedText)) return WorkMode.Onsite;
if (trust == RemoteTrust.TruncatedDescription) return WorkMode.Unknown;
if (trust == RemoteTrust.RequiresExplicitRemoteMatch)
return LooksExplicitlyRemote(combinedText) ? WorkMode.Remote : WorkMode.Unknown;
return WorkMode.Remote;
}
Every source carries a trust tier. Boards like RemoteOK and Himalayas are remote-only by nature, nothing to check. A general board like Reed has to positively say “remote,” not just avoid saying “hybrid.” Adzuna and Careerjet get a stricter tier again – more on why below – that never resolves to Remote at all, only Hybrid, Onsite, or Unknown. What used to be instant rejection for all of these is now just a tag, which is the only reason the work-mode filter and the Stats page can exist at all – you can’t show hybrid/onsite volume for data you already threw away.
~
The RegEx’s Doing All the Work
If this were more fancy, an AI/LLM call or agent could do this. In the interests of simplicity and minimal dependencies, a few regular expressions are used.
Relevance is one pattern, .NET and AI/ML terms as alternatives rather than two filters ANDed together:
private static readonly Regex Pattern = new(
@"(?<![a-z0-9])(\.net\b|asp\.net\b|dotnet\b|blazor\b|c#|ai\b|llm\b|genai\b|nlp\b|machine learning|generative ai|artificial intelligence|agentic ai|ml engineer)",
RegexOptions.IgnoreCase | RegexOptions.Compiled);
The leading (?<![a-z0-9]) is doing real work: none of the alternatives has its own leading \b, just a trailing one, so ai\b alone would match the tail end of Dubai, Mumbai, Chennai, Shanghai – city names ending in those two letters. The lookbehind closes that off.
Work mode runs on three more patterns – hybrid, onsite, and an explicit-remote check with a negative lookahead so a company “developing remote monitoring systems” doesn’t get read as offering a remote job:
private static readonly Regex HybridPattern = new(
@"\bhybrid\b|\b(?:\d+|once|twice|one|two|three|four|five|six)\s*(?:times?|days?)?\s*(?:a|per|/)\s*week\b",
RegexOptions.IgnoreCase | RegexOptions.Compiled);
private static readonly Regex OnsitePattern = new(
@"\bon[\s-]?site\b|\bin[\s-]office\b|\bbased\s+(?:at|in)\s+(?:their|our|the)?\s*(?:site|office)\b|\b(?:office|site)[\s-]based\b",
RegexOptions.IgnoreCase | RegexOptions.Compiled);
private static readonly Regex ExplicitRemotePattern = new(
@"\bremote\b(?!\s+(?:monitoring|sensing|control|access|support|management|desktop|connectivity|devices?|systems?|session))|\bwork\s*from\s*home\b|\bwfh\b|\bremote[\s-]first\b",
RegexOptions.IgnoreCase | RegexOptions.Compiled);
Simple to read, cheap to run – no API calls, no tokens, no network dependency. Just text in, a tag out.
~
Bolting On a New Source
This is the part I actually designed for, because I knew day one that eleven sources wouldn’t be the last number. The whole thing hinges on one small interface:
public interface IJobSourceAdapter
{
string SourceName { get; }
Task<List<JobPosting>> FetchAsync(HttpClient http, CancellationToken ct);
}
Adding a source means three things, and none of them touch the pipeline:
- Write a class that implements it – hit the API, map whatever data it gives you onto the shared
JobPostingmodel (title, company, location, tags, salary if it has one). - Pick a
RemoteTrusttier. Remote-only board, no office jobs mixed in?TrustedRemoteOnly. Remote-focused but could carry the odd hybrid listing?AssumedRemoteUnlessFlagged. General board that covers ordinary office jobs too?RequiresExplicitRemoteMatch. Does that general board’s API also truncate descriptions, so you can’t fully trust an explicit “remote” mention either?TruncatedDescription– the one that learned that lesson the hard way. - Add one line to the adapter list in
Program.cs.
That’s it.
Relevance matching, dedupe, work-mode classification, the Stats page – none of it knows or cares where a JobPosting came from. It was built against RemoteOK’s data first, then proven against nine more completely different ones, so by the time other job boards were added, it was just steps 1 through 3 above and not a redesign.
This makes it easier for you to extend.
~
Where It’s At
This tool is open source and available on GitHub here. Feel free to clone/branch/adapt to your needs.
~
Enjoy what you’ve read, have questions about this content, or would like to see another topic covered?
You can schedule a call using my Calendly link to discuss consulting and development services.
~
Courses
Check my AI courses. From developers to decision makers, these have you covered:
~