Backend engineer at Cosmic DATA · Casablanca, Morocco
I build the layer where one “Publish” button becomes a fistful of vendor APIs.
Multi-channel social and local-listing management — publishing, reviews, and analytics across the major networks.
Most of the work is translation. One button labelled “Publish” has to become a handful of vendor APIs that each hold a different opinion about what a post is, what counts as an image, and how a date should be written.
Reconciling those opinions is the actual work. The button is the easy part.
| Async by default | Anything touching a third-party API goes on a queue and reports back when it's done |
| Never trust a vendor | Third-party APIs do not belong anywhere near your request/response cycle |
| Fail loudly | A swallowed HTTP error is a bug that surfaces three weeks later, in production |
Mostly PHP, with a solid JavaScript / TypeScript side — integration plumbing, API backends, and the occasional thing built purely to find out whether it would work.
On GitHub since 2022, reconciling OAuth flows for most of it · LinkedIn



