I help engineering teams deploy applications confidently, automate infrastructure, and improve production reliability through practical DevOps engineering.
An example pipeline: commit, build, test, publish, deploy, and verify. Select a stage to see representative configuration.
Kubernetes
AWS
Docker
Terraform
Ansible
GitHub Actions
Argo CD
Helm
Prometheus
Grafana
Nginx
Linux
PostgreSQL
MySQL
MongoDB
Redis
Kafka
RabbitMQ
Python
Bash
Go
Kubernetes
AWS
Docker
Terraform
Ansible
GitHub Actions
Argo CD
Helm
Prometheus
Grafana
Nginx
Linux
PostgreSQL
MySQL
MongoDB
Redis
Kafka
RabbitMQ
Python
Bash
Go
// When to hire me
Does any of this sound familiar?
You don't need to know the technical terms. If one of these describes your situation, I can help — usually faster than you'd expect.
Your app is finished — but it isn't live yet
The product works on your laptop or a test server, and now it needs a real home: a domain, HTTPS, a database, backups, and a setup that won't fall over on launch day.
I take it from your repository to a secure, production-ready URL — and document how it runs.
Kubernetes, AWS, containers, pipelines, or a plain server — if it needs deploying, I can help. Every project is quoted after I review your requirements; no fixed packages and no outcomes promised before I understand your system.
01
Kubernetes Deployment & Operations
Run your applications on Kubernetes — Amazon EKS or self-managed — with rollouts, scaling, and recovery handled by the platform instead of by hand.
Deliverables
Deployments, Services, and Ingress (manifests or Helm charts)
Liveness and readiness probes
Resource requests, limits, and autoscaling (HPA)
ConfigMaps and Secrets management
Zero-downtime rolling updates and rollback
Cluster and workload documentation
Ideal for: Teams outgrowing a single server, or adopting Amazon EKS for the first time.
Design and build your AWS environment as Terraform code — networking, access, compute, and data — so it is reviewable, reproducible, and secure by default.
Deliverables
VPC with public and private subnets
IAM roles and least-privilege policies
EKS, ECS, or EC2 compute
RDS, S3, ECR, Route 53, and TLS certificates
Reusable Terraform modules with remote state
Infrastructure documentation
Ideal for: SaaS teams moving to AWS, or bringing an existing account under code control.
Replace manual release steps with a pipeline that builds, tests, publishes, and deploys — to AWS, Kubernetes, or plain servers — with a clear path back if something goes wrong.
Deliverables
Build and test automation
Image publishing to Amazon ECR or another registry
Automated deployments to Kubernetes, ECS, or VMs
Environment-specific configuration
Deployment verification and rollback strategy
Ideal for: Startups and agencies shipping often enough that manual releases slow them down.
Whatever you are deploying and wherever it runs, I can help. Kubernetes or a single VPS, AWS or another cloud, a monolith or microservices — I review how you build, deploy, and operate software and help you get it into production properly.
Deliverables
Infrastructure and architecture review
Deployment strategy for any stack or platform
Kubernetes and AWS adoption guidance
Cloud migration planning
Reliability and cost improvements
Security and operational recommendations
Ideal for: CTOs, founders, and agencies who need an experienced DevOps partner for any deployment challenge.
A remote DevOps engineer who works like part of your team
Hands-on infrastructure work for startups, SaaS companies, and agencies across North America, Europe, Australia, and Africa — without the cost and delay of a local hire.
One person, end to end
From your code repository to a live, monitored production system. No hand-offs between agencies, no finger-pointing.
Clear, jargon-free communication
I explain options and trade-offs in plain English, send regular written updates, and you always know what's happening.
Working hours that overlap with yours
Based in UTC+6, I overlap with the business day in Europe, Africa, and Australia, work overnight for North America, and schedule calls in your time zone.
Fixed scope, honest quote
We agree on deliverables, timeline, and price in writing before work starts. No surprise invoices.
Secure — and you own everything
Least-privilege access you can revoke anytime. All code, infrastructure, and documentation live in your accounts — no lock-in.
Flexible engagement
A one-off project, a part-time monthly retainer, or support when you need it — at remote rates that are typically more affordable than hiring locally.
Your business hours, covered
I work with clients in Bangladesh and remotely across North America, Europe, Australia, and Africa. Calls are scheduled in your time zone, and work often progresses while you sleep.
Bangladesh
UTC+6
Same time zone — and happy to meet in person in Dhaka.
North America
UTC−8 to UTC−4
Dhaka is 10–14 hours ahead — work moves forward overnight, ready for your morning.
Europe & Africa
UTC+0 to UTC+3
Dhaka is 3–6 hours ahead — your morning is my afternoon.
Australia
UTC+8 to UTC+11
Dhaka is 2–5 hours behind — your afternoon is my morning.
Your time
--:--
My time
--:--
Dhaka · UTC+6
// Industry experience
Two years inside Bangladesh's capital market
I've worked on systems connected to the Dhaka and Chittagong stock exchanges — where downtime during trading hours is not an option. That discipline comes with me to every project.
Each case study walks through the problem, architecture, decisions, and trade-offs. Professional work and personal lab builds are labelled clearly; client details are never published.
Two years supporting systems in Bangladesh's capital market, connected to the Dhaka Stock Exchange (DSE) and Chittagong Stock Exchange (CSE). These run on Nasdaq trading technology, using the FIX protocol for order flow and FAST for market data.
A production-style Kubernetes platform on Amazon EKS, provisioned with Terraform: multi-AZ VPC, managed node groups, ALB ingress with TLS, autoscaling workloads, images in Amazon ECR, and Prometheus/Grafana monitoring.
A Docker Compose platform running multiple application services with PostgreSQL, MongoDB, Redis, and Kafka behind an Nginx reverse proxy, with health checks, resource limits, and isolated networks.
Terraform provisions the infrastructure, Ansible roles configure it, and environment-specific inventories keep staging and production consistent — with secrets handled through Ansible Vault.
A Harbor registry for versioned, access-controlled container images, integrated with the build pipeline and deployment workflow.
Harbor
Docker
CI/CD
TLS
// Technical expertise
Kubernetes, AWS, and the toolchain around them
Hands-on experience across the full delivery path — from AWS networking and Kubernetes clusters to the dashboards that tell you it's healthy. These are areas of practical experience, not certifications.
Kubernetes & Containers
Containerized workloads from laptop to cluster.
Kubernetes
Amazon EKS
Helm
Kustomize
Ingress
Docker
Docker Compose
AWS Cloud
Secure, well-structured AWS environments.
EC2
VPC
IAM
EKS
ECS
ECR
S3
RDS
Route 53
CloudWatch
Infrastructure as Code
Repeatable provisioning, configuration, and scripting.
Terraform
Ansible
Linux
Bash
Python
Go
CI/CD & Delivery
From commit to running workload.
GitHub Actions
Argo CD
GitOps
CI/CD pipelines
Amazon ECR
Harbor
Rolling deployments
Observability
Metrics, logs, dashboards, and alerts.
Prometheus
Grafana
Loki
Grafana Alloy
Node Exporter
cAdvisor
CloudWatch
Security & Reliability
Operational safeguards built in.
Secrets management
IAM least privilege
TLS and HTTPS
Health checks & probes
Rollback procedures
Network isolation
Databases & Messaging
Stateful services, run reliably.
PostgreSQL
MySQL
MongoDB
Redis
Kafka
RabbitMQ
Capital Markets
Exchange connectivity and trading systems.
FIX protocol
FAST protocol
Nasdaq trading platforms
DSE
CSE
Market data
// Architecture
From commit to observed production
The delivery path I typically build on AWS and Kubernetes: every change is reviewed, built once, stored as an immutable image in ECR, rolled out on EKS, and watched in production. The same pattern adapts to ECS, plain VMs, or other clouds.
Metrics and logs are collected from nodes, pods, the load balancer, and application services.
Delivery flow: Developer, then Git repository, CI/CD pipeline, container registry, deployment environment, reverse proxy, and application services. Monitoring and logging observe every runtime layer.
// How we work together
A predictable engagement, start to finish
You always know what's being done, why, and what it costs before it starts.
Clear, regular written updates
Least-privilege, revocable access
Every change documented and reviewable
Transparent scope — no surprise work
01
Discovery
Understand your application, team, constraints, and what success looks like.
02
Assessment
Review the current infrastructure, deployment flow, and operational risks.
03
Proposal
Agree on scope, deliverables, budget, and timeline in writing before work starts.
04
Implementation
Build and configure the solution in small, reviewable, documented changes.
05
Validation
Test functionality, security, failure modes, and the deployment path end to end.
06
Handover
Deliver documentation, walk your team through it, and provide the agreed support.
// About
Hi, I'm Omor Faruk.
I'm a DevOps engineer with 7 years in the software industry. I help teams get software into production — and keep it running.
Beyond infrastructure, I have a solid programming background. I can read and debug your application code, and I write my own automation in Python and Bash — so I work directly with your developers, not just hand over servers.
For the past two years I've worked on Bangladesh's capital market, supporting systems connected to the Dhaka and Chittagong stock exchanges. That's where I learned to treat every production change with care: planned around market hours, tested, and always reversible.
Today I work with startups, SaaS companies, and agencies in Bangladesh and across North America, Europe, Australia, and Africa — on Kubernetes and AWS, CI/CD pipelines, infrastructure as code, and monitoring. Whatever you need deployed, from a single VPS to an Amazon EKS cluster, I'll help you run it properly.
How I work
01Automate the repeatable
If it's done twice by hand, it becomes reviewed, versioned code.
02Make failure boring
Health checks, rollbacks, and runbooks turn incidents into routine.
03Observe before guessing
Metrics and logs first; opinions second.
04Leave it documented
Your team can run what I build without me.
// FAQ
Hiring a DevOps engineer: common questions
Straight answers about cost, cloud platforms, access, and what you get at the end.
How much does it cost to hire a DevOps engineer?
Every project is quoted in writing after I review your requirements, so you know the price before work starts. Engagements range from small fixed-scope tasks to a part-time monthly retainer, at remote rates that are typically more affordable than hiring locally.
Can you deploy my application to AWS or Kubernetes?
Yes. I deploy applications to AWS (EC2, ECS, or Amazon EKS), to Kubernetes clusters, to Docker on a single server, or to other clouds. I'll recommend the simplest setup that meets your needs, not the most complex one.
Do I really need Kubernetes?
Not always. For many applications, Docker on a well-configured server or AWS ECS is simpler and cheaper. Kubernetes pays off when you run many services, need autoscaling, or have a team that will operate it. I'll give you an honest recommendation either way.
Do you work with clients in the US, UK, Europe, and Australia?
Yes. I work remotely with teams in North America, Europe, the UK, Australia, and Africa, as well as in Bangladesh. Based in UTC+6, I overlap with the business day in Europe, Africa, and Australia, and schedule calls in your time zone.
Can you set up a CI/CD pipeline for my project?
Yes. I build CI/CD pipelines with GitHub Actions, GitLab CI, or Jenkins that test, build, and deploy your code automatically, with rollbacks so a bad release can be undone quickly.
Do you need access to my production systems?
Only what the work requires. I use least-privilege access that you can revoke at any time, and I never ask for credentials through the inquiry form. All code, infrastructure, and documentation stay in your own accounts.
What do I get at the end of a project?
Working infrastructure, version-controlled code for it, and clear documentation, so your team can run what I build without me. I walk your team through the handover and provide the support we agreed on.
Do you offer ongoing DevOps support?
Yes. Besides one-off projects, I offer a part-time monthly retainer for ongoing improvements, monitoring, and support, or help when you need it.
// Contact
Let's discuss your project
Tell me about your infrastructure and goals. I'll review the details and reply with questions or a proposal — there's no obligation.