Cloud Architect
Vitestro
·Today
- Location
- Utrecht, Utrecht, Netherlands
- Workplace
- Hybrid
- Type
- Full-time
- Department
- Software
- Seniority
- Senior
- Source
- Recruitee
Description
About Vitestro
Founded in 2017 in Utrecht, Vitestro is pioneering the future of blood collection with the Aletta® Autonomous Robotic Phlebotomy Device™ (ARPD™). This groundbreaking medical device combines advanced multi-modal imaging (near-infrared, ultrasound, and Doppler ultrasound) with robotics and AI to perform the entire diagnostic blood draw procedure autonomously.
By addressing critical healthcare staffing shortages and improving patient experience, Vitestro is transforming one of the most common and essential medical procedures. With more than 130 team members and growing rapidly, we are scaling our impact. As we placed our first devices with customers, we are now expanding our team to ensure successful implementation and long-term reliability.
At Vitestro, we are committed to continuous innovation and improvement.
We are looking for a Cloud Architect to shape and implement Vitestro's cloud platform with a clear, pragmatic technical direction. Our infrastructure runs on AWS and supports mission-critical, regulated medical device software. Vitestro is also realizing its first integration with Laboratory Information System (LIS) over the cloud, and delivering that connection is a core part of this role. We need someone who translates real operational and business constraints into working systems — someone whose first instinct is "what does this actually need to do, reliably and affordably," not "what's the most sophisticated way to solve this."
You will join the Platform & Connectivity team and build alongside its cloud, backend, and DevOps engineers. This is an individual-contributor technical leadership role, not a people-management position — you carry the architectural vision and build it hands-on with the team, rather than designing something for others to execute.
If you'd rather ship a solid, working solution than iterate endlessly toward a theoretically ideal one, and you have a track record of keeping cloud costs under control at scale, you'll thrive in this role.
First months at Vitestro
In your first months, you get to know our cloud platform, the device connectivity and the team. You review the current architecture, its costs and its production-readiness, and identify where the biggest risks and quick wins are. You take ownership of the cloud architecture for our first LIS integration, and you agree with the team on the first architectural standards for observability, logging and infrastructure as code.
This is what success looks like:
After 12 months, our first LIS integration runs reliably in production, with monitoring, alerting and failure handling in place. Cloud costs are predictable and under control, and key architectural decisions and trade-offs are recorded. The team uses shared patterns instead of reinventing solutions, and is confident running production systems as we move from pre-market to post-market.
Key Responsibilities:
Set the technical direction for our AWS-based cloud platform and build it hands-on with the team — weighing cost, operability, and production-readiness as first-class concerns, not afterthoughts
Own the cloud architecture of Vitestro's first LIS integration over the cloud: secure, reliable, and traceable data exchange between our platform and the hospital laboratory
Choose solutions on their merits rather than defaulting to the most AWS-native option — including other clouds, self-hosted tooling, or dedicated infrastructure when that's genuinely the better fit
Take implementations from a working prototype to something that's production-ready — monitoring, alerting, and failure handling included. You bring experience with production systems and advise the team on how to navigate from pre-market to post-market stages.
Establish architectural standards and patterns so similar problems (e.g. observability, logging, data pipelines) get solved consistently instead of reinvented each time
Keep cloud costs in check as part of everyday engineering decisions, catching expensive mistakes before they show up on an invoice
Balance short-term solutions driven by business needs and deadlines against the long-term architecture: make each trade-off explicit, record it, and plan the path from the tactical fix to the durable solution
Diagnose and resolve production issues across the cloud platform from logs, metrics, and traces