DEVOPS ENGINEER02+ YEARS IN PRODUCTION

Infrastructure
that holds
under pressure.

02+YEARS HANDS-ON

06CORE PROJECTS

4SYSTEM LAYERS

24/7PRODUCTION MINDSET

THE OPERATING MODEL

I connect the full path—not isolated tools.

01SOURCEGit / Repos

→

02BUILDCI / Images

→

03SHIPAnsible / Helm

→

04OPERATEObserve / Recover

METRICSLOGSTRACESALERTSRUNBOOKS

01PROFILE

I don’t just deploy software.
I make it operable.

I’m Saied Awad, a hands-on DevOps engineer working across production infrastructure, delivery automation and platform reliability.

At Nixpend, I support environments that span ERPNext/Frappe platforms, APIs, microservices, databases, CI/CD systems and a full observability stack. The work is practical: ship changes safely, diagnose failures across layers, protect data, and make recovery repeatable.

My strongest work happens at the intersection of application, container, network, proxy, database, storage and host—where production problems rarely respect team boundaries.

02CAREER

Production is the
real classroom.

My experience is built around systems that people actually depend on.

2023 — PRESENTAMMAN, JORDAN

CURRENT ROLE

DevOps Engineer

Nixpend — Sequential Technologies

Operate Linux development, testing, monitoring and production infrastructure. Maintain containerized application stacks, Frappe/ERPNext environments, databases, reverse proxies, backup systems and delivery automation across multiple servers and customer sites.

Design and maintain branch- and tag-aware Azure DevOps pipelines.
Coordinate production releases through GitLab, Ansible and manual approval.
Operate Grafana, Prometheus, Loki, Tempo and alerting infrastructure.
Troubleshoot incidents spanning queues, storage, TLS, networks and builds.
Create runbooks so critical operations can be performed safely by others.

ENGINEERING DEGREEJORDAN

EDUCATION

Bachelor of Engineering

Al-Balqa Applied University

The engineering foundation behind a systems-first approach: understand the whole, reason through constraints, and design practical solutions that can be maintained.

03 / SELECTED WORK

Systems I’ve helped
build and run.

Not demos. Working infrastructure shaped by deployment windows, incidents, storage limits, dependencies and recovery requirements.

01OBSERVABILITY

One view across the whole stack

Operated a centralized platform for infrastructure metrics, container telemetry, logs, traces, alerts and endpoint monitoring.

02DELIVERY

A release path built for confidence

Maintained multi-stage delivery from source and image build through manual production approval, multi-server rollout and version validation.

03PLATFORM

ERP infrastructure at multi-site scale

Managed independent Frappe benches and customer sites across development, testing, demo and production—not a single installation.

04KUBERNETES

Stateful workloads, made portable

Worked through readiness, ingress, shared database and persistent-storage challenges for ERPNext workloads on Kubernetes.

05RECOVERY

Backups designed to come back

Operated structured, date-based backups covering databases, public files, private files and site configuration with tested recovery procedures.

06APPLICATIONS

Repeatable microservice delivery

Managed registry-driven deployments for public APIs, private APIs and frontend applications with environment-specific configuration.

04INCIDENT LESSON

WHEN “START THE SERVICE” ISN’T ENOUGH

Recovery needs context,
not just a restart.

A failed Frappe queue stopped appointment reminders. Restoring it would have released obsolete queued messages all at once.

I identified the second-order risk and improved the recovery procedure: inspect and remove stale jobs before bringing workers back. That is how I approach operations—restore service without creating the next incident.

DETECT→UNDERSTAND→CONTAIN→RECOVER→IMPROVE

05CAPABILITIES

A broad toolkit.
One systems view.

Tools are useful when they reduce risk, clarify ownership and make good operations repeatable.

Containers

Docker · Compose · Dockerfiles · Registries · Networking · Volumes

Kubernetes

K8s · Helm · Ingress · StatefulSets · PV/PVC · CronJobs · NFS

Delivery

Azure Pipelines · GitLab CI/CD · Ansible · Git · Azure Repos

Observability

Prometheus · Grafana · Loki · Tempo · OTel · Alertmanager

Data

MariaDB · PostgreSQL · MongoDB · Redis · S3-compatible storage

Edge & security

Nginx · Traefik · Cloudflare · Zero Trust · TLS · pfSense

Cloud

GCP · Oracle Cloud · Scaleway · CloudStack · VMware · Proxmox

Automation

Ansible · Bash · YAML · rclone · Cron · operational runbooks

HOW I WORK

Trace the whole path.

Application → container → network → proxy → database → storage → host.

Automate the repeatable.

Pipelines, scripts and playbooks replace fragile operational memory.

Design for recovery.

A backup only matters when the restore path is clear and tested.

Leave a runbook.

The next engineer should be able to act safely without guessing.