multicloud
Architecture on AWS and Azure
Cloud-native environments designed for availability and fault tolerance rather than assembled by default — landing zones, network topology, identity, and the boundaries between workloads.
Jashan Sandhu · Brampton, Ontario
Senior Systems Engineer working across AWS, Azure, and on-premises platforms. Ten years spent making enterprise infrastructure scalable, secure, and cheaper to run — starting on a datacenter floor and ending up architecting the multicloud environments that replaced it.
What I do
Most of the work falls into one of these, and the interesting projects touch all four at once.
multicloud
Cloud-native environments designed for availability and fault tolerance rather than assembled by default — landing zones, network topology, identity, and the boundaries between workloads.
automation
Environments defined in Terraform and CloudFormation, deployed through pipelines in Azure DevOps, Jenkins, or CodePipeline. If a change is made by hand, it isn't finished.
hybrid
vSphere estates, storage, and physical networking kept healthy alongside cloud — including the migrations where workloads move up and the ones where they stay put for good reasons.
operations
Monitoring that catches problems before users do, tuning that keeps latency flat, and spend reviews that cut cloud bills without quietly trading away resilience.
Technical depth
Read it from the bottom up — that's also the order I learned it in, starting in a server room and working upward.
Physical hosts, power and cooling, capacity planning, and the on-call rotations that keep thousands of servers answering.
The abstraction that made everything above it possible — clustered hypervisors with high availability, fault tolerance, and tested recovery.
Enterprise workloads architected across two providers, with the networking and identity design that decides whether the rest of it holds together.
Infrastructure declared in code and shipped through pipelines, so environments are reproducible and every change has a commit behind it.
Where applications actually live now, and the instrumentation that makes their behaviour legible at three in the morning.
ground → skyten years, bottom to top
Security and networking run vertically through all five. A master's in information systems security and an AWS Advanced Networking specialty mean the segmentation, routing, and access model get designed in at the start rather than audited in at the end.
Experience
OMERS
Rackspace Technology
FlexITy Solutions Inc.
SoftLayer, an IBM Company
Background
I'm Jashan Sandhu, a Senior Systems Engineer based in Brampton, Ontario. I design, deploy, and operate cloud infrastructure across public and private platforms — and because I started in a datacenter rather than a console, I tend to know what the abstraction is actually sitting on.
That path runs through hardware operations, VMware estates, and integration work before it reaches multicloud architecture, which is why hybrid environments hold no mystery for me. Most organizations aren't purely cloud or purely on-prem; they're mid-migration, indefinitely, and the engineering that matters happens at the seam.
Alongside the technical work I spend a lot of time translating it — turning architecture decisions into terms a stakeholder can weigh, and staying the point of contact between the technical and business sides of a project. Sky Technologies is where I collect that work.
The Linux Foundation · 2023
Amazon Web Services · 2022
AWS · Azure · Red Hat · VMware
Get in touch
Whether it's a migration you're scoping, an environment that costs more than it should, or a role you think I'd fit — send a note and I'll come back to you.
Prefer email? jsandhu@skytechnologies.ca — or find me on LinkedIn.