Teams/Cloud & infra
Cloud & infrastructure engineers
The accounts, networks, and pipelines your product runs on. Dedicated cloud engineers working from our Dhaka office, on your platform and your hours — on one US contract, at flat monthly rates.
prod · landing-zone
01terraform plan → changes staged
02review → approved, no policy flags
03terraform apply → running
04resources created → state saved
05outputs exported → ok
06drift check → none · state clean
VPC
isolated
IAM
least privilege
Storage
encrypted
The layer everything else stands on.
Weak infrastructure doesn’t fail loudly — it fails slowly. Bills creep, permissions sprawl, and one bad outage exposes it all at once. That’s why we vet cloud engineers on architecture judgment and real infrastructure-as-code, not on console screenshots.
Landing-zone architecture
Accounts, environments, and guardrails set up before the first workload lands — so growth doesn't mean rework.
Networking
Subnets, routing, private connectivity, and DNS that make sense on a whiteboard and hold up in production.
Identity & access
Least-privilege roles and clean permission boundaries. Who can touch what should never be a mystery.
Cost management
Tagging, budgets, and right-sizing from day one. Cloud bills drift when nobody owns them; ours do.
Compliance readiness
Encryption, audit logging, and backup posture built in — so an audit is a checklist, not a scramble.
The platforms and tools we staff.
Tell us where you run — we match from our pipeline. These are the cloud platforms and infrastructure skills we most commonly place.
| Area | What we use it for | Where it shows up |
|---|---|---|
| AWS | Core compute, storage, and managed services | Startups and most US product teams |
| Azure | Enterprise workloads and Microsoft integration | Corporate systems, .NET shops |
| GCP | Data platforms and Kubernetes-first setups | Analytics-heavy products |
| Terraform / Pulumi | Infrastructure as code, reviewed like software | Every environment we manage |
| VPC / networking design | Segmentation, routing, private connectivity | Anything that touches production |
| Backup & disaster recovery | Tested restores, not just scheduled backups | Anywhere your data lives |
What you'll see on Bangladeshi cloud CVs.
Certifications aren't how we vet — our pipeline is. But they show what the market here trains for. Behind them sits an engineering-school pipeline — BUET, University of Dhaka, NSU and others — and a competitive-programming culture that takes fundamentals seriously.
| Certification | Issuer | What it signals |
|---|---|---|
| AWS Solutions Architect — Professional | Amazon | Deep multi-account architecture judgment |
| AWS Solutions Architect — Associate | Amazon | Cloud architecture fundamentals |
| AZ-104: Azure Administrator | Microsoft | Running production workloads on Azure |
| Google Associate Cloud Engineer | Hands-on GCP deployment and operations | |
| HashiCorp Terraform Associate | HashiCorp | Infrastructure-as-code fluency |
| AWS Security — Specialty | Amazon | Cloud security depth beyond the basics |
How we vet a cloud engineer.
Five stages before you meet anyone — and you still interview last and make the final call. Nobody joins your team without your sign-off.
- 1Architecture conversation — multi-account, landing zones
- 2Live infrastructure-as-code exercise
- 3Networking depth
- 4Security review
- 5English & communication screen
Our office in Dhaka — where your team sits. Real photos, real people.
Frequently asked questions
With Girmairi, a dedicated cloud & infrastructure engineer is a flat monthly seat: mid-level from $2,800, senior $4,000, and lead $4,800 per month, with junior seats available on request. The rate includes the office, equipment, HR, and management, and is billed monthly in advance in USD. The full rate card is at /pricing#infrastructure.
A full-time AWS, Azure, or GCP engineer costs from $2,800 per month at mid-level and $4,000 at senior level, with leads at $4,800. These are flat monthly rates for a dedicated, full-time engineer working your hours — not hourly freelance billing.
Yes. Girmairi staffs engineers who work in Terraform and Pulumi and treat infrastructure as code that is reviewed like software. Every candidate passes a live infrastructure-as-code exercise during vetting, and credentials like HashiCorp Terraform Associate and AWS Solutions Architect are common in the pipeline.
Girmairi's cloud engineers are full-time employees working from its managed office in Dhaka — no freelancers or scattered contractors. Each engineer works exclusively for one client, on that client's timezone, Slack, and standups.
Yes. Girmairi vets each cloud engineer first — an architecture conversation, a live infrastructure-as-code exercise, networking depth, a security review, and an English screen — then the client interviews last and makes the final call. Nobody joins the team without the client's sign-off.
The contract is with Girmairi LLC, a US company, so it works like any US vendor relationship: one monthly invoice in USD, billed in advance. An NDA and full IP assignment are signed before any work begins, so the client owns 100% of the infrastructure code and configurations.
Girmairi replaces the engineer from its pipeline under a replacement guarantee. A bad fit is Girmairi's cost, not the client's.
Yes — teams of 3 or more seats, or 12-month commitments, get 5–10% off the flat monthly rate. Every client company also gets one hour per month with Girmairi's founder, a working CTO, included at no extra cost.
Cloud seats are on the standard rate card.
Same flat monthly rate, same includes — office, equipment, HR, management, replacement guarantee.