
I Tried to Beat Google Alerts to a Job Posting. Here's What I Learned (and Broke).
Building a real-time job notification system on AWS taught me the difference between a job board and an alert system and cost me a few hours to PowerShell's ampersand parsing along the way.
The problem that started it all
A few weeks ago I was tracking a specific IAS officer's name on Google Alerts, out of pure curiosity. It took Google hours to surface a news article that was already indexed elsewhere. That got me thinking: if Google Alerts is this slow for news, it's catastrophically slow for jobs
where "hours late" doesn't mean "missed a headline," it means "300 people applied before you even knew the role existed."
So I set out to build something that would notify me the second a job opened at a company I cared about. Not a digest. Not a daily email. The moment it's posted.
I did not expect this to turn into a four-day fight against PowerShell's ampersand parsing, a bot named after myself accidentally, and a fairly humbling realization that I'd built the wrong product entirely twice.
Attempt #1: I accidentally built... a job board
My first instinct was "scrape everything, show it in a nice UI." So that's what I did. Connectors for Greenhouse and Lever, a slick 3D hero section with React Three Fiber, GSAP scroll animations, the works. It looked great.
And then I stopped and asked myself what I was actually building, and the honest answer was: LinkedIn Jobs, but worse, with extra particle effects.
The entire point was never "browse jobs beautifully." It was "know before anyone else." A browsable feed is the opposite of urgency it assumes the user has time to scroll. I didn't want time to scroll. I wanted my phone to buzz.
Attempt #2: the actual architecture
Once I reframed it, the fix wasn't a rewrite it was adding a delivery layer on top of everything I'd already built:
- Connectors (Greenhouse, Lever, Workday, Smart Recruiters) poll company career APIs no LinkedIn, because LinkedIn's ToS and legal team will find you, and no fully custom scrapers for sites like Google or Microsoft unless you enjoy your code breaking every time they redesign a button.
- The moment a genuinely new job is detected (post-deduplication), it fires an event through Amazon EventBridge.
- That event triggers a match engine that checks it against every user's saved watch rules, instantly not on the next scheduled poll.
- Matches fan out through Amazon SNS to two delivery channels: a WebSocket push for anyone with the app open, and a Telegram bot for everyone else, because in India, people check Telegram faster than they check email.
The AWS pieces did exactly what they're supposed to do here: decouple detecting a job from delivering the alert. Adding the Telegram channel later took maybe twenty minutes of actual work, because it just meant subscribing a new consumer to the SNS topic. Nothing upstream had to change. That's the entire value of building this way cheap to extend, hard to accidentally break.

The bug that made me feel something
Somewhere around hour 40 with no sleep, I tried testing the Telegram bot manually with curl. PowerShell decided my
& character in chat_id=X&text=Y was a reserved operator and refused to run the command, throwing an error that, in the moment, felt personal.The fix was switching to
Invoke-RestMethod , which is objectively the more "correct" Windows-native way to do it but I will never forgive PowerShell for making me feel incompetent over a single ampersand.Right after that, I copied my chat ID from the wrong place and spent ten minutes confused why my bot token's numeric prefix and my actual chat ID looked suspiciously identical. (They were not supposed to be identical. That was the bug.)
What actually shipped
By the end: a working connector system across ten-plus companies, an event-driven notification pipeline on EventBridge and SNS, a WebSocket toast that fires within seconds of a new posting, and a Telegram bot that puts the alert directly on my phone with a live-updating "posted 2 minutes ago" timestamp so I always know exactly how fresh it is.
What I'd tell someone starting this from scratch
Build the ugly, working pipeline before the pretty UI. I had a gorgeous 3D hero section before I had a single working notification completely backwards for a product whose entire pitch is speed, not looks.
And test your Telegram bot with a standalone curl call before wiring it into your app. If it fails inside your app, you won't know if the problem is your code or your bot config. If it works standalone first, every future bug is guaranteed to be yours.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article