Open to remote roles and relocation

AhmedBenhmida

DevOps & Cloud Infrastructure Engineer, and technical lead.

google cloud
kubernetes
terraform
gitlab ci/cd
vault

I design, automate and operate reliable cloud infrastructure, and help engineering teams ship production-ready platforms.

View projects Download CV LinkedIn

Tunis, Tunisia

delivery pathhealthy

years in DevOps: 4years in DevOpsCloud, containers and Linux since 2022
platforms led: 2platforms ledTechnical lead on DeepSocial and Agent4All
client sites supported: 100+client sites supportedHosting, DNS, SSL and mail in production
production servers: 5+production serversOperated, migrated and monitored

about

Production is the only environment that counts.

I build and operate the infrastructure other engineers deploy to. In practice that means Google Cloud described in Terraform, workloads running on GKE, pipelines in GitLab that carry a commit all the way to production, and secrets that live in Vault instead of a repository.

I came to cloud work through Linux operations, and I think that is the right order. Before GKE there were production servers and 100+ client sites — DNS records, certificate renewals, mail deliverability, migrations run at night, and incidents where service has to come back first and the root cause second. That work sets your standard for what ready means.

On DeepSocial and Agent4All I led the technical side: choosing how things get deployed, writing those decisions down so they outlast me, reviewing infrastructure changes, and keeping the team unblocked when production has an opinion of its own.

Cloud platforms

Google Cloud footprints written in Terraform — VPC, IAM, GKE node pools, remote state — so an environment is a file, not a memory.

Delivery

GitLab pipelines that take a commit to production: build, test, image, rollout, health check. No manual steps in the middle.

Operations

Linux, hosting, DNS, SSL and mail in production, and the incident response that goes with them at the hour it breaks.

Leadership

Technical direction for small teams: choosing the deployment model, writing the decisions down, reviewing the changes.

Ahmed Benhmida — ahmed benhmidatunis, tn

education

2023National Software Engineering DiplomaESPRIT — Private Higher School of Engineering and Technology
2020Licence, System and Network AdministrationHigher Institute of Computer Science of Mahdia

languages

Arabic Native
French Advanced
English Professional

work

Three platforms, and what it took to run them.

Each of these is production infrastructure someone depends on. Open one to see the problem, the decisions and what changed.

Cloud platform2025 — present

DeepSocial

Tech Lead · Cloud Infrastructure

The cloud foundation for a social intelligence platform on Google Cloud — from an empty project to a reproducible GKE environment with a governed release path.

GCP
GKE
Kubernetes
Terraform
Vault
Docker
GitLab CI/CD
Kaniko

the problem

Engineers needed an environment they could deploy to many times a day, without hand-edited infrastructure, leaked secrets, or clusters nobody could rebuild.

the outcome

Deploying became a pipeline run rather than a manual operation, and the environment can be rebuilt from code.

what I built

Modelled the whole footprint in Terraform — VPC, subnets, IAM, GKE node pools, remote state — so every environment is created the same way.
Ran workloads on GKE with rolling updates, health checks, resource limits and readiness gates in front of each release.
Moved secrets into HashiCorp Vault with Kubernetes auth, so pods request credentials at runtime instead of carrying them in manifests.
Built GitLab CI/CD pipelines that lint, build, push and deploy, with Kaniko building images inside the cluster.
Containerised data and ML services alongside the teams that own them, tuning images for size and start-up time.

Team leadership2025

Agent4All

Technical Lead

Led the technical team delivering the Agent4All platform: scoping the work, making the infrastructure calls, and owning the path to production.

Docker
Kubernetes
CI/CD
Cloud infrastructure
Technical leadership

Industrial IoT2024 — 2025

ENERCO

DevOps Engineer

An industrial monitoring platform streaming telemetry from field devices, containerised into one reproducible stack with deployment and monitoring around it.

Docker Compose
Node.js
React
Kafka
MongoDB
GitLab CI/CD
Linux

experience

Four years of production, in order.

From hosting operations to cloud platforms — each role added a layer without dropping the one underneath.

Oct 2025 — present
Euklydia
DevOps Engineer
Tunis, Tunisia
- GCP
- Terraform
- GKE
- Vault
- GitLab CI/CD
Building and operating the Google Cloud platform behind production workloads.
- Provision VPC, IAM and GKE across environments with Terraform and remote state.
- Operate Kubernetes releases with rolling updates, health checks and deployment validation.
- Run secrets through HashiCorp Vault with Kubernetes auth instead of static credentials.
- Standardise build, test and deploy in GitLab CI/CD.
- Containerise data and ML services with the teams that own them.
Apr 2024 — Nov 2025
Electrosoft / HyperMedia
DevOps & Linux Infrastructure Engineer
Sfax, Tunisia
- Linux
- WHM/cPanel
- Plesk
- DNS & mail
- Docker
Kept 100+ client sites and 5+ production servers online, and modernised how they ship.
- Operated production servers across WHM/cPanel, Plesk and VPS/SSH environments.
- Ran site and mail migrations end to end: DNS, SSL, mailboxes, MX, SPF, DKIM, DMARC and reverse DNS.
- Monitored availability, backups and security posture to cut production risk.
- Responded to incidents on hosting, DNS, SSL and mail — restoring service first, fixing causes after.
- Containerised the ENERCO platform and added CI/CD and monitoring around it.
Dec 2022 — Dec 2023
Ridcha Data
DevOps Engineer
Tunis, Tunisia
- Terraform
- Kubernetes
- Argo CD
- Helm
- Prometheus
Automated cloud infrastructure and moved on-premises workloads into the cloud.
- Wrote Terraform modules with remote tfstate in GCP, and reusable GitLab CI/CD templates.
- Ran Kubernetes runners and Kaniko so images build inside the cluster.
- Deployed with Argo CD and Helm, and added Prometheus and Grafana for visibility.
- Migrated on-premises websites to cloud environments.
- Managed secrets in Vault and analysed GCP spend to cut waste.

stack

The tools, grouped by what they are for.

Everything here has run in production, not only in a lab.

Google Cloud as the primary platform, described entirely in code.

Google Cloud
GKE
Terraform
VPC
IAM
OpenStack

also deployed and supported: kafka, mongodb, node.js and react services

certifications

Certified by Google Cloud, twice.

Both exams cover the work directly: architecting on Google Cloud, and operating what you ship.

Google Cloud

Professional Cloud Architect

Designing cloud architecture, and the trade-offs between reliability, security and cost.

architecture design
networking & iam
reliability
cost control

Google Cloud

Professional Cloud DevOps Engineer

Building delivery pipelines and operating services with SRE practices on Google Cloud.

ci/cd pipelines
sre practices
monitoring
incident response

Credentials are listed on LinkedIn.

contact

Need someone who can build the infrastructure and stay on call for it?

I read every message. Tell me what you are running, what is breaking or what you want to build, and I will tell you straight whether I am the right engineer for it.

Send an email Download CV LinkedIn

availabilityopen

based in: Tunis, Tunisia
open to: Remote roles and relocation
focus: Cloud platforms, Kubernetes, delivery