Cloud Architect - Clinical Trials Platform

Cloud / Platform Architect

About The Role

MAESTRO is the unified clinical-trials operating system that sponsors, CROs, academic research centres and biotech teams run their studies on - CTMS, eTMF/eISF, QMS, ELN, workflows and more in a single, tenant-isolated, audit-ready platform. The trust our customers place in us starts with the infrastructure underneath: it has to keep the most sensitive data in clinical research safe, available, and provably under control.

You'll own the architecture that makes that real. MAESTRO runs as a multi-tenant SaaS with Canadian data residency, and also as dedicated, single-tenant deployments for customers where data sovereignty and isolation are non-negotiable. Your job is to make both of those models scalable, resilient, cost-efficient and compliant - and to set the technical foundation the rest of the engineering team builds on for years.

This is a hands-on architecture role with real ownership: you define the patterns, you prove them in production, and you keep them honest as we grow.

What you'll do

• Define the reference architecture for a multi-tenant platform that can also be deployed as isolated, single-tenant instances - with clear, documented patterns for tenancy, isolation and identity.
• Design for data residency, high availability and disaster recovery so customer data stays in-region and the platform keeps running through failures.
• Establish infrastructure-as-code standards, network design, secrets management and a clean path for promoting changes from development to production.
• Build the foundations for scalability, observability and cost control so the platform grows predictably as we add tenants, modules and data volume.
• Partner with security, quality and compliance so the platform is architected for GxP, 21 CFR Part 11, EU Annex 11, ICH GCP E6(R3) and Health Canada expectations from the ground up - not bolted on later.
• Lead architecture decisions, write the decision records, and mentor engineers on operating production infrastructure safely.
  
  

What you'll bring

• 5+ years designing and operating production cloud infrastructure at scale.
• Strong command of multi-tenancy and isolation models, networking, and identity/access management.
• Deep, hands-on infrastructure-as-code experience, plus containerization and orchestration in production.
• A proven track record of high-availability and disaster-recovery design and incident-grade operational thinking - you've been on call for systems that can't go down quietly.
• The ability to translate regulatory and data-residency requirements into concrete, testable infrastructure controls.
  
  

Nice to have

• Experience with regulated, healthcare or life-sciences workloads and strict data-residency requirements.
• Multi-region, multi-provider or hybrid deployment experience.
• Familiarity with event-driven and data-intensive architectures.
  
  

Education

• Minimum: a Canadian Bachelor's degree (baccalauréat) in Computer Science, Computer/Software Engineering, Information Systems or a related technical field - or a college diploma / advanced diploma (DEC, 2–3 years) in a relevant program combined with extensive production infrastructure experience.
• An asset (not required): a Master's degree (maîtrise) in a related technical field; or recognized cloud architecture or infrastructure certifications.
• Internationally educated candidates are welcome; foreign credentials should be assessed for Canadian equivalency (e.g. WES, ICAS or a comparable recognized service) to confirm the equivalent Canadian level.
  
  

Location & eligibility

This role is open only to candidates who are based in Canada and legally entitled to live and work in Canada (Canadian citizens, or permanent/legal residents with valid Canadian work authorization). We are not able to sponsor relocation or work authorization for this position.

Why join

You'll set the technical foundation of a platform that research organizations trust with their most sensitive data - at an early enough stage that you get to architect it properly, not inherit someone else's shortcuts. The infrastructure you design is held to the same standard we sell our customers: continuously validated, inspection-ready, and built to last.