Cloud Solutions Architect / Senior DevOps
Summary
Design and implement a scalable, multi-tenant SaaS platform on Azure for a climate-tech company, focusing on Kubernetes, observability, and high-availability data tier.
We are a climate-tech product team building a multi-tenant SaaS platform. We are scaling into enterprise customers and want an experienced architect to help us design the platform for that next stage.
This is a focused, well-scoped engagement with clear goals, not an open-ended retainer. You will work directly with the project lead.
What you will do
Design multi-tenant resource isolation so workloads stay predictable as customer count and data volume grow.
Architect the async and background-processing model for long-running, data-heavy operations.
Design and implement high availability for the data tier, including replication and verified backup and restore.
Mature the deployment pipeline for deterministic, auditable releases.
Define the service-level indicators that reflect real customer experience, and build the observability to measure them.
Right-size cloud resources against measured usage and introduce autoscaling.
Load and capacity testing at realistic data volumes.
Give us your long-term view on cloud strategy. We are on Azure and are not planning to migrate, but we want an architect's assessment to plan against.
What we are looking for
5+ years in cloud architecture, platform engineering or SRE, with real design ownership on at least one production system.
Multi-tenant SaaS experience. You have solved noisy-neighbour and tenant-isolation problems before and have views on how.
Strong production Kubernetes: Helm, resource management, autoscaling, disruption budgets, rolling-update strategy.
Azure preferred, ideally AKS. Equivalent depth on AWS or GCP is fine.
MongoDB operations at production scale: replication, migrations, backup and restore verification.
Prometheus, Grafana, Alertmanager, Loki. Able to design meaningful alerting, not just install exporters.
Terraform and CI/CD pipeline design.
Able to read Node.js well enough to reason about where memory and time go.
Comfortable disagreeing with a proposed design and explaining why.
English sufficient for written technical discussion and calls.
Nice to have
GitOps in production (Argo CD or Flux).
Load testing with k6 or JMeter.
Exposure to blockchain infrastructure or carbon markets. Genuinely optional, we will teach the domain.