Anass A.

Most automation projects start as a script and end as a rewrite. I build them as systems from day one. I am a Python backend engineer working with FastAPI, PostgreSQL, Redis and Playwright. I design with Clean Architecture and DDD so the business rules stay separate from the tools around them. When a website changes, a data source is swapped or a new rule is needed, you change one piece, not the whole thing. A recent example: a client hired me to automate one chart on a betting stats site with Playwright. He came back for a second version, and this time I built it as a foundation: a clean domain layer, a FastAPI REST and WebSocket gateway for live control and telemetry, and configurable rules. Adding a new chart or strategy no longer means untangling old code. What I work on: • Backend APIs and services with FastAPI, JWT/OAuth2 and async I/O • Browser and API automation with Playwright • Data pipelines and document processing on PostgreSQL and Redis • Tested code (TDD) and Docker deployments with CI/CD You get clear written updates, honest estimates, and code another developer can pick up without me.