A few months ago I got tired of how job hunting actually works. You find a role you like, you apply, and then you realize it was posted three days ago and already has 400 applicants. By the time a job shows up in your normal scroll, you're already late.
So I built FindMeJobs to flip that around. Instead of me checking job boards, it checks them for me, constantly, and messages me the second something matches what I'm actually looking for.
Here is how it is put together.
You define a search once: keywords, boolean include/exclude rules, location, and so on. From then on a pipeline scrapes fresh postings every few minutes, filters them against your rules, runs the survivors through an AI relevance check, and if something matches you get a Telegram or email alert within minutes of it going live.
Being early is basically the entire value, so the whole system is built around latency.
The app itself is a fairly standard T3-style setup:
Nothing exotic there. The interesting part is the scraping and notification pipeline, which does not live inside the Next.js app at all.
Scraping runs entirely on Cloudflare Workers + Queues on a cron schedule:
Splitting it into queue stages meant each step scales on its own, and one slow scrape never blocks notifications for a different user.
The product is live at findmejobs.co, and I put up a repo with more detail and a discussions space here: https://github.com/ali-moussavi/findmejobs. Happy to get into the architecture in the comments.
And if you have job hunted recently, I would honestly like to hear which part of the process annoyed you the most. That is mostly what I have been building against.