Shaheer Sarfaraz

I build and fix web scraping systems that need to keep working after the demo is over.

That can mean building a scraper from scratch, but a lot of the interesting work starts when something already exists and isn’t quite reliable enough: flaky sessions, proxy issues, anti-bot changes, expensive browser automation, messy data, poor logging, or a target site that keeps moving the goalposts.

I can help with:

• Crawlee and Apify implementations
• debugging unreliable or failing scrapers
• API and hidden-data-source reverse engineering
• reducing unnecessary browser/proxy costs
• data normalisation and delivery pipelines
• logging, monitoring and ongoing maintenance

I’m a software engineer at Autodesk, and I’ve spent a lot of time building scraping infrastructure in the wild.

I created JobOps, an open-source job search platform with around 4,000 GitHub stars, pulling jobs from 10+ job boards for 1000+ weekly job seekers. I also built Scraperecon, a CLI for figuring out what a site is doing before you build the scraper: bot protection, TLS fingerprinting, rate limits, embedded data, and whether browser automation is actually necessary.

I’ve also written for the official Crawlee blog about debugging anti-bot and redirect issues I ran into while building JobOps.

If you need a scraping system built, or already have one that works 90% of the time and need help with the other 10%, feel free to reach out.