<aside> 💡

Upload your work as a zip on this form. If the roadmap, PR, or other deliverables live in Notion or a private repo, include those links in the zip (typically in the README). For questions, email [email protected].

</aside>

Instructions Technical Test

<aside> 🖼️

What you get

</aside>

• Read-only access to our infra monorepo (Terraform/Terragrunt on AWS, Terraform on GCP/"crypt3ns" for the sovereign-cloud migration, Ansible for on-prem client deployments, Packer, GitHub Actions CI/CD).

• Our business & product strategy (vision, 2026–2028 roadmap, business objectives, GTM, and "what we won't do" — attached below)

  Business Context — Primer for the DevOps/SRE Case

<aside> 🎯

Objective

</aside>

We want to see how a senior translates business strategy into infrastructure priorities, navigates an unfamiliar real codebase, and communicates trade-offs. Reliability, security (we handle hospital data), and "does this move the business" are the lenses.

<aside> 👩‍⚕️

Format

</aside>

• ~2 hours of prep on your own with the repo + context.
• 1-hour session: 30 min you present, 30 min discussion.
• Deliverables: whatever communicates best (slides, a written doc, diagrams). AI tools allowed; be ready to defend every choice as your own.

<aside> 🏮

Bonus Points

</aside>

• Cost / FinOps view: Propose how you'd give the team per-client and per-environment cost visibility across our providers, and one concrete lever to cut spend as we scale.
• Compliance & data residency: We process French hospital data and are moving toward a sovereign cloud. Call out what an HDS-type / data-residency posture demands from infra (secrets, logging, encryption/CMEK, access control, audit) and where the repo is currently short.
• Scalability: where's the toil today and what would you work on first?

<aside> 📂

What to Include in Your Submission

</aside>