DevOps & Infrastructure Engineer · Lalitpur, Nepal

Hi, I’m Prazwal.
I make deploys boring.

I build and operate the systems that keep software running at Gurzu — and I like to understand them all the way down to the kernel.

Open to new work · based in Lalitpur, Nepal
Download CV
Portrait of Prazwal Bhattarai, smiling
Lalitpur, Nepal · UTC+5:45
About me

Good infrastructure is the kind nobody has to think about.

I keep the path from a developer’s commit to production short, boring, and reliable. Boring is the point — a deploy should be the least eventful part of anyone’s day.

I started in carrier networks, watching BGP routes at Worldlink and commissioning access networks at Huawei, so I still trace problems from the routing layer up. I’d rather understand a system all the way down than trust it as a black box.

What I do

The road from commit to production.

no meeting required
01

Zero-downtime deployments

Designed and shipped a health-checked rolling release process across our Kubernetes and CI/CD pipeline. No visible blip, no maintenance window — now the default way we ship.

Docker · Kubernetes · health checks
02

Cloud for enterprise clients

Scalable infrastructure on GCP, AWS and Linode for clients with very different availability and compliance needs — shaped around each product, not one house pattern.

GCP · AWS · Linode · Terraform
03

CI/CD pipelines

Built the team’s first pipelines with dev and ops, and keep them running across client environments — so a release is a pipeline run, not an event.

Jenkins · GitHub Actions
04

Monitoring & incidents

Services that report their own health instead of waiting for someone to notice. I lead root-cause response, then automate whatever keeps coming up.

Grafana · Prometheus · New Relic
How I work

Three things I optimise for.

Every pipeline, dashboard and runbook I touch gets measured against these.

Lead time

Commit to prod, no meeting.

Pipelines trusted enough to run themselves. If shipping needs someone to babysit it, that’s a bug in the pipeline.

Recovery

Notice it before the customer does.

Alerts that point at a cause, not a symptom. An alert nobody acts on is worse than no alert.

Toil

Delete the runbook.

Done twice, it gets written down. Done three times, it gets automated — and the doc gets deleted.

Experience

From the wire up to the pipeline.

Five years across telecom networks and cloud infrastructure — which is why I debug from the packet up.

Feb 2024 — now
DevOps & Infrastructure Engineer
Gurzu Inc. · Lalitpur · promoted from Associate in Feb 2026

Cloud infrastructure, CI/CD pipelines and production monitoring for enterprise clients on GCP, AWS and Linode.

Current
Jun 2022 — May 2023
Access Network Engineer
Huawei Technologies · Pulchowk, Lalitpur

Ran access network infrastructure for an internet-scale telecom customer, and installed and commissioned equipment in the field.

Networks
Oct 2021 — Jun 2022
Infra-Monitoring Assistant
Worldlink Communications · Jawalakhel, Lalitpur

Watched MPLS, DWDM and BGP across NPIX links around the clock, flagging anomalies before they became outages.

Monitoring
Toolbox

What I reach for.

Grouped the way I actually use them — from bare Linux boxes to managed Kubernetes.

Cloud
AWSGCPLinodeHetzner
Containers
DockerKubernetes
Delivery & IaC
JenkinsGitHub ActionsTerraformAnsible
Observability
PrometheusGrafanaNew RelicUptime KumaNagios
Systems & data
LinuxNGINXBashPythonPostgreSQLMySQLMongoDB
Certifications
CKA
CNCF
Certified Kubernetes Administrator
studying
AWS
Amazon Web Services
Solutions Architect – Associate
studying
Writing

Notes from the layer below.

Things I only understood after reading the source instead of the docs — practical, with real commands.

All notes on Hashnode →
Now

What I’m up to.

updated Sep 2026
  • Running a zero-downtime release process for production at Gurzu.
  • Studying for the CKA (Certified Kubernetes Administrator).
  • Studying for AWS Certified Solutions Architect — Associate.
  • Reading kernel networking code, one rabbit hole at a time.
Contact

Let’s make your releases boring too.

Hiring, scoping a piece of infrastructure work, or just want to trade notes on how things actually work underneath? I read every message.

Prefer plain email? bprazwal678@gmail.com

I usually reply within a day
Book a call
30 minutes over Google Meet, at a time you pick. Best for scoping work.
Send an enquiry
Describe the problem and I’ll come back with whether I can help, and how.
Write an email
Book a 30-minute call Open in new tab ↗