Cloud bills, cut. Kubernetes, shipped.

Yes — freelance and contract engagements are most of what I do, fully remote for clients in the US, EU and APAC. That covers fixed-scope projects (a cloud cost audit, a Kubernetes or GitOps platform build, a CI/CD pipeline rebuild) and ongoing fractional DevOps retainers. I contract directly and through the usual freelance platforms.

Based GMT+6 (Bangladesh) but built for async. Overlap with EU mornings, US Pacific evenings, and the full APAC business day. Most clients see me responsive 12+ hours a day on Slack / Linear / email.

Openly: I'm the infrastructure owner for a commercial multi-tenant SaaS platform, and I take a small number of outside engagements alongside it. That is why the experience on this site is current rather than remembered — I'm operating production Kubernetes this week, not describing a platform I left three years ago. In practice it means async delivery, a cap on how much I take on at once, and no scope I can't hold. If an engagement needs more hands or full business-hours coverage, I bring in engineers from a small delivery company I co-founded — you contract with me, and I stay accountable either way.

Fixed-scope whenever the work allows it — that protects both of us. Retainers are quoted monthly. I don't publish hourly rates because the deliverable is what matters. Pricing is discussed on the intro call once we've scoped the problem.

Then the audit says so in writing, with the working shown — which is worth having when a board or an investor asks the question. I would rather tell you there is 6% on the table than manufacture a finding to justify the invoice. In practice it is rarely all-or-nothing: teams with disciplined rightsizing often still have no reserved-capacity strategy, or no way to answer "who owns this workload and can we delete it". The governance half of the engagement is what stops an already-efficient estate drifting back over the following year. And if the intro call makes it clear there isn't enough on the table to justify the fee, I'll say so on the call rather than scope it.

Audits and advisory sessions usually start within 1–2 weeks of signing and run 1–2 weeks. Larger projects (cluster builds, platform work) typically kick off 2–4 weeks out. If something's on fire, say so on the intro call — I keep a small amount of capacity for urgent work.

Both. Most engagements run alongside an internal team — I embed, pair with your engineers, and leave them able to operate what I've built. Where there isn't yet a platform team to pair with, I deliver directly, and for larger builds I pull in engineers from the delivery company I co-founded. Scope isn't capped by one person's calendar.

Week 1: scoping interviews, access, written engagement doc. Week 2: discovery / audit, surfaced findings, prioritised plan. Weeks 3–4: implementation on the agreed scope, weekly written check-ins, live demo at end of week 4.

You contract with me personally. I invoice in whatever currency works for you, paid by direct bank transfer or Wise — if you need something else, we'll make it work. Fixed projects usually bill by milestone; otherwise terms are negotiable. Either way the exact terms go into the written engagement doc before any work starts.

Yes — happy to sign before the first call. I've worked under client NDAs across ISO 27001, GDPR, FADP and SOC 2 environments.