About
Engineer by instinct,
builder by choice.
I'm Rafsal Rahim—a systems and infrastructure engineer with six years of experience designing and operating software that runs in production under real load, with real security requirements.
My work sits at the intersection of cloud infrastructure, backend systems, and blockchain engineering. I'm most effective when the problem requires thinking across layers: from the smart contract to the Kubernetes cluster to the Terraform module that provisions it all.
I run an independent engineering practice, working with startups, growth-stage companies, and technical teams who need someone who can take ownership of complex infrastructure problems—not just execute tickets.
The path here
From automation to enclaves.
Platform & Automation
Started by automating the boring stuff—Bash scripts became Ansible playbooks, manual deployments became pipelines. Learned that the highest-leverage work in any engineering team is removing toil.
Cloud Infrastructure & Kubernetes
Moved into cloud-native infrastructure full time. Kubernetes, Helm, Terraform—building platforms that teams could deploy to confidently, not cautiously. Infrastructure-as-code became a non-negotiable.
Blockchain & Distributed Systems
Got deep into Web3. Designed and deployed smart contracts, built Go services for on-chain integrations, and started thinking seriously about trustless systems and what decentralised infrastructure actually looks like in production.
Confidential Computing & Freelance
The frontier I'm most excited about: hardware-enforced privacy for cloud workloads. AWS Nitro Enclaves, TEEs, remote attestation—cryptographic guarantees that even the cloud provider can't read your data. Running this work as a freelance practice, taking on select infrastructure and blockchain projects.
Independent practice
Engineering as a founder.
Running an independent practice isn't just a business model—it's a lens. When you're accountable for the outcome, not just the output, you make different decisions about architecture, dependencies, and operational complexity.
I've learned to think like an owner: what will this cost to operate in a year? What happens when the team changes? What's the security posture if this gets popular? These questions don't come from a checklist—they come from having been the one on call.
I work with founders, technical leads, and product teams who want a senior engineer who can think about the business problem, not just the implementation detail.
What I take on
- Cloud infrastructure design and implementation
- Blockchain and smart contract engineering
- Platform and DevOps transformation
- Confidential computing architecture
- Technical advisory and architecture review
Availability
Currently open to new projects. I take on 1–2 engagements at a time to ensure full focus. Typical engagements are 3–6 months, with ongoing retainers available.
Start a conversationWorking style
How I work.
I start with constraints.
Before writing a line of code, I want to understand the security model, the scale requirements, and the operational reality. The design follows.
I document as I build.
Architecture decisions, runbooks, API contracts—written in real time, not as an afterthought. Future-me and future-teammates both benefit.
I prefer boring technology.
New doesn't mean better. I reach for proven tools and save novelty for the problems that genuinely require it.
I communicate like an engineer, not a consultant.
Precise, direct, and honest about trade-offs. If something has a risk, I'll name it. If a deadline is unrealistic, I'll say so.
Technical skills