Make state visible
A system should explain what ran, what failed, and what happens next.
I work best on operational problems with repeated manual steps, fragmented tools, difficult web data, and failure modes that need more than a quick script.

Good automation is not the shortest route from input to output. It is the clearest route through validation, retries, ownership, history, and recovery—without making the people who use it become its permanent support team.
A system should explain what ran, what failed, and what happens next.
Retries, timeouts, rate limits, and cancellation need explicit rules.
Extraction, validation, persistence, and delivery should be independently testable.
Documentation and operability are part of delivery, not optional polish.
TayyabAutomates · Islamabad / remote worldwide
Upwork Top Rated Plus · Fiverr
Pir Mehr Ali Shah Arid Agriculture University
Credential links were not supplied, so no verification URLs are invented.
Google / Coursera · completed July 2026
micro1
Listed with LinkedIn Learning in the supplied résumé
LinkedIn Learning