The Problem
In early 2025, I spent nine months looking for a WordPress support job. Nine months of scrolling job boards, tweaking cover letters, hearing nothing back. My buddy Patrick would find posts on WP Remote Work and send them to me on WhatsApp. Most went nowhere.
But one of Patrick's shares struck gold. I got the job at LiquidWeb — working on LearnDash, later SolidWP and StellarSites, plus The Events Calendar.
That experience planted a seed. Patrick was doing exactly what a bot could do — scanning sources, filtering for relevance, sending offers directly to someone's phone. What if there was an automated version of that? A system that surfaces WordPress job offers before you even go looking for them?
The Catalyst
December 2025. LiquidWeb laid off 50 people. Among them was Ben Meredith — one of the best managers and leaders I've ever worked with. The WordPress job market suddenly had a lot of talented people looking.
If there was ever a time to build this thing, it was now.
First Build
February 15, 2026. The initial pipeline was straightforward: RSS feeds pulling from jobs.wordpress.net and WP Remote Work, a Greenhouse API integration for Automattic listings, and an HTML scraper for Incsub careers. Jobs came in, got deduplicated, and posted to a Telegram channel.
Simple pipeline. Nothing sophisticated. But it worked — and it was running in production from day one.
Scaling the Pipeline
The source list grew fast. Lever API brought in Kinsta, SiteGround, and Hostinger. Workable API opened the door to 14+ companies — 10up, Awesome Motive, Human Made, Wordfence, WP Rocket, Patchstack, and more. Every major WordPress employer that published jobs through a structured API got wired in.
Then came AI classification. Claude Haiku reads every listing and extracts role type, category, required skills, work mode, and a concise summary. Each post gets tagged with searchable hashtags and formatted with branded Telegram markup.
One rule became non-negotiable: nothing posts without AI enrichment. If classification fails or the daily API cap is hit, jobs stay pending. Quality over volume. Always.
The Rewrite
By March 11, the original shared-template architecture had served its purpose but was holding the bot back. Independent deployment, dedicated scaling, platform-specific optimizations — all blocked by the shared codebase.
So we rewrote it. 19 commits in one day. A clean standalone TypeScript application with its own Docker container, SQLite database, and GitHub Actions CI/CD pipeline. Database migrated to prevent re-posting old listings. v3 went live on March 12.
24+ sources. Posting every 5 minutes. Running cold on EC2.
The Community
At 176 subscribers, I posted about the channel on LinkedIn. 21 people liked it. 9 reposted to their networks. Five left comments.
The people who amplified it: Ben, Ali, Luigi, Sharif, Aditya, Jovan (who wrote his own post pointing people to the channel), Marcel, Youssef, and Patrick.
Patrick. The same Patrick whose WhatsApp messages started this entire thing. Full circle.
200
The philosophy behind this channel has always been simple: if even one person finds something that fits them and makes them happy, the effort was worth it.
200 people decided it's worth their attention. That's enough.