DevOps & Cloud Infrastructure Engineer, AWS, Terraform, Kubernetes, Migrations, FinOps
I'm a DevOps and cloud infrastructure engineer. I have an MSc in Software Engineering and Computer Science. Most of my work has been in payments and banking systems where things breaking isn't just a technical problem, it costs real money.
That shaped how I work. I don't cut corners. I document what I build so the next person doesn't need to call me to understand it. And I treat every setup as if someone else will have to run it one day because they usually do.
On the technical side I work across the full infrastructure stack. Cloud architecture on AWS and Azure. Terraform. Kubernetes. CI/CD pipelines with GitHub Actions and GitLab CI. Containerised deployments. DevSecOps. I've led a full legacy-to-cloud migration without disrupting live operations, and built payment systems running 10,000+ daily transactions with near-zero downtime.
Freelancing is not something I'm doing on the side. It's where I'm putting my focus and every project I take on is a chance to do solid work and build a reputation that reflects that.
I work on cloud architecture, cost audits, infrastructure provisioning, CI/CD, serverless design, and resilience planning. And before I talk about what I offer, I'll ask what you actually need.
Work Terms
Availability: Monday to Saturday, 9:00 AM to 9:00 PM GMT+1 (Casablanca, Morocco). I typically respond to messages within a few hours during these hours.
Payments: For most projects, I prefer milestone-based payments. It keeps expectations aligned and ties every invoice to something delivered. For smaller, well-defined tasks, a fixed-price agreement works fine.
Scoping: Before I send a quote, I will ask a few clarifying questions. Not to slow things down, just to make sure I scope it right and do not deliver something that misses the mark.
Environment Access: If a project requires read-only access to your systems, I always ask for the minimum permissions needed. I never touch live systems without a written agreement on scope first.
Revisions and Scope: Revisions are part of the process. I would rather get it right than close out work that does not fully land. If the scope changes significantly mid-project, we agree on the adjustment before I continue.
Capacity: I do not take on more than I can deliver. If I am at capacity or your project is not the right fit for my skills, I will say so upfront.
Premium Commitment: I reserve my best work and fastest turnaround for clients who value and invest in premium engagement.