I build things that
stay up when it matters.
I'm Yaser — recently graduated from two years of hands-on DevOps engineering training in Sweden. Here's the honest version of what that means: I know how to set up the systems that make your software reliable, your deployments uneventful, and your cloud bill something you can actually predict. That's a more specific thing to be good at than it sounds.
Tools I work with
What DevOps actually means now
AI can write a bash script in seconds. That changes the job description. Here's what it changes it to.
Being valuable meant writing clever scripts and setting up servers manually. The code was the deliverable.
The deliverable is a system that runs reliably, scales under pressure, costs what you expect, and doesn't surprise you at 2am. The code is just how you get there.
Boring is the goal.
When your infrastructure is working the way it should, there's nothing dramatic to report. Here's what a quiet morning looks like:
Things I hear from clients, and what happens next.
Not a list of tech tools. The actual problems that bring people to a DevOps engineer.
Every deployment is a stressful event. Something always breaks.
I set up automated testing and staged rollouts so new changes are checked before they reach users. Deploys stop being events and start being non-events.
CI/CD automationOur cloud bill keeps growing and nobody knows why.
I audit what's actually running, right-size the resources to what you actually need, and set alerts before spending runs away. Most small setups have 30–40% unused capacity.
FinOps · Cost optimizationWe had a security scare and it's made us nervous about everything.
I apply the fundamentals that stop most attacks: proper access controls, automated secret rotation, security scans on every deploy. Not glamorous, but consistently effective.
DevSecOpsOur site went down exactly when we had our biggest traffic spike.
I build monitoring that catches issues before users notice, and infrastructure that scales automatically when traffic climbs. The spike becomes a non-story.
Monitoring · Auto-scalingMy team spends too much time on manual, repetitive tasks.
Almost everything repetitive in a software workflow can be automated. I map those tasks out and remove them. The team gets that time back for the work that actually needs humans.
Workflow automationWe need to move to the cloud but it feels risky and complicated.
It's a methodical process when you know what you're doing. I can map exactly what moves, in what order, and what the monthly bill will look like. No surprises.
Cloud migrationSecurity and cost. In that order.
These are the two things small businesses worry about most, and the two areas where I try to have a concrete answer rather than a vague assurance.
Security isn't an add-on
The most common mistake I see in small infrastructure setups is treating security as something you bolt on at the end. By then it's already a liability.
I treat it as part of the design from the start. That means: access controls that work the way they're supposed to, secrets that rotate on a schedule nobody has to remember, daily backups that are actually verified, and alerts that tell you something is wrong before your users find out.
"The goal is that a security problem becomes something we noticed and fixed, not something a customer reported."
Cloud costs should be predictable
Cloud providers make it easy to spend more than you need to. The defaults are generous — to them. Most small setups I've looked at have meaningful unused capacity.
I go through what's actually running, match resource sizes to real usage patterns, set up budget alerts before spending runs away, and find the places where a better architecture means a lower bill.
This site is itself the demo.
The website you're reading is deployed through a CI/CD pipeline I built and maintain myself.
Every change I push goes through an automated check before it goes live. No manual FTP uploads, no "I'll just fix it directly on the server." The same discipline I'd apply to your infrastructure, I apply to my own.
The code is public on GitHub. If you're technically minded and want to see exactly how this works — the pipeline configuration, the deployment setup, the whole thing — it's there to look at. That's intentional.
From Hultsfred, Sweden.
I'm Yaser — originally from Palestine, now living in Hultsfred in southern Sweden. I spent the past two years in full-time training through Sweden's YH system, which is a practical, work-focused form of higher education. Both programmes I'm finishing — DevOps Engineering and Application Engineering — are built around real projects rather than theory alone.
I'm a recent graduate, and I'm not going to oversell that. What I can say honestly is that I've already built things that work: a full CI/CD pipeline deploying to Red Hat OpenShift, a Django web app managing repair jobs for a small business, infrastructure-as-code setups, and monitoring stacks. The portfolio section below shows the actual code, not just descriptions of it.
I also use AI tools — Claude, and various open-source models — and I won't pretend otherwise. I use them to work faster and catch things I might miss. But I read, understand, and test everything before it goes anywhere near production. The AI helps me work; it doesn't replace knowing the work.
I speak Arabic, English, and Swedish, which turns out to matter more than you'd think for a DevOps role. Being able to explain a deployment issue to a developer, a business owner, and a non-technical client in different languages — and in different registers — is actually useful.
Things I've actually built
All open source. You can read the code, not just a description of it. That's the point.
Full CI/CD to OpenShift
Built with two classmates: a complete pipeline that automatically builds, tests, and deploys to Red Hat OpenShift. A feature push to production went from a manual process to something that takes 6 minutes and requires no human intervention.
View on GitHubRepair Shop Manager
A web app that tracks repair jobs from the moment they come in to the moment they go out. What was previously tracked in a notebook — and occasionally lost — became a searchable, status-tracked system.
View on GitHubDjango Starter Kit
A reusable Django starting point with user accounts and a shop module already in place. Lets me start a new client project with the boring infrastructure already solved, not rebuilt from scratch each time.
View on GitHubERPNext on Docker
A customised Docker setup for running ERPNext — full business management software — self-hosted. The equivalent of a €200/month SaaS subscription, running for the cost of a €5 server.
View on GitHubTwo years, finishing now.
YH — Yrkeshögskola — is Sweden's applied higher education system. It's built around actual working environments, not lectures. Here's what I've completed and what I'm finishing.
DevOps Engineering
Lernia Yrkeshögskola · 400 YH-p
Oct 2024 – Jun 2026
Application Engineering
Hermods Yrkeshögskola · 400 YH-p
Oct 2024 – May 2026
Also completed
Microsoft Azure Fundamentals (AZ-900)
Microsoft · Issued August 2021
Advertisement
Honest answers, no pitch
You just graduated. Is that enough experience?
Honestly — it depends on the project. I've shipped real things during training and I know how to do the work properly. For straightforward projects, a junior doing it carefully is often better value than a senior doing it quickly. For complex, high-stakes infrastructure I'll tell you upfront if something is beyond what I should take on solo right now.
Do you only work with technical clients, or can you help non-technical business owners too?
Non-technical clients are actually most of who I'd like to work with. I speak Arabic, English, and Swedish, and I've had a lot of practice explaining infrastructure decisions to people who don't want to think about infrastructure. That's a skill I take seriously.
You mentioned using AI tools like Claude. Does that mean the work isn't really yours?
No. I use AI the way a carpenter uses power tools — it helps me work faster and catch things I might miss. Everything I deliver I've read, understood, and tested. If I can't explain why a piece of code does what it does, I don't ship it. The AI doesn't replace understanding the job; it helps me do it better.
Are you looking for a job, or only freelance?
Both. I'm looking for junior DevOps or cloud engineer roles in Sweden, and I'm open to freelance and contract work alongside that. If you have a project rather than a position, I'm interested in hearing about it.
Can you work remotely with clients outside Sweden?
Yes. I'm based in Hultsfred but I work remotely with clients across Sweden and the wider EU. Most of what I do doesn't require being in the same room.
What do you charge?
It depends on the scope. A one-time audit or small setup is different from ongoing monthly support. I quote clearly before anything starts — no vague estimates that expand later. Get in touch and I'll give you a straight answer.
Let's make your systems boring.
In infrastructure, boring is the goal — no surprises, no 2am phone calls, no "the site is down" messages from customers. Tell me what you're trying to fix or build. I reply within a day or two, and I'll be straight with you about what's realistic.
If something I built or wrote saved you time, you're welcome to:
Buy me a coffee