Team Lead — Federated Platform Development
(Barcelona based, 90-110k EUR base salary, performance incentive, stock option)
Role Summary
We are building a federated healthcare data platform enabling secure, privacy-preserving research across hospitals and medical devices in multiple regions.
We are seeking a Team Lead for Development who will own the technical delivery and execution of this platform — translating architectural direction into implemented systems and coordinating multidisciplinary engineering teams.
This role sits between architecture design and operational deployment.
While a separate Architect defines reference architectures (IRIS-based and Open-Source stacks), the Team Lead ensures those designs are implemented, integrated, and delivered across real-world hospital environments.
You will work closely with:
- Architect
- Delivery Manager
- DevOps & Backend Engineers
- Data Engineers (OMOP / ETL)
- Visualization & Full-stack Developers
- Clinical & Research Teams
Mission of the Role
Your mission is to turn federated architecture into working production infrastructure.
This includes:
- Onboarding new hospitals into the federated network
- Delivering research workspaces and analytics pipelines
- Supporting platforms integrating medical device data
- Coordinating engineering execution across regions
You are responsible for how the platform gets built and shipped, not just how it is designed.
Key Responsibilities
1. Technical Delivery Leadership
- Lead engineering execution of the federated healthcare platform
- Translate architecture decisions into concrete implementation plans
- Coordinate backend, DevOps, data, and frontend teams
- Ensure delivery timelines align with business and research goals
This is hands-on leadership, not pure management.
2. Federated Infrastructure Implementation
Work across both architecture scenarios:
Enterprise Stack
- IRIS for Health integration
- HL7/FHIR ingestion pipelines
- Secure anonymization workflows
- Federated research workspace deployment
Open Architecture Stack
- PostgreSQL-based analytical infrastructure
- Containerized ETL pipelines
- API-driven federated query orchestration
- Cloud-native deployments
You don’t need to invent the architecture — you must operationalize it.
3. Hospital & Device Platform Onboarding
- Coordinate technical onboarding of new healthcare partners
- Oversee deployment of secure data nodes
- Align implementation with regulatory constraints
- Support development of patient platforms receiving device data
This is critical for Traverse Health’s expansion (KSA, Mexico, Brazil, UAE).
4. Engineering Coordination & Execution
You will lead a distributed team including:
- DevOps engineers managing cloud/on-prem nodes
- Data engineers performing OMOP transformations
- Backend developers building APIs and orchestration services
- Visualization engineers building research dashboards
Your role is to:
- Define implementation milestones
- Remove technical blockers
- Maintain delivery velocity
5. Platform Governance & Technical Quality
- Ensure secure data boundaries and governance models are respected
- Maintain auditability and compliance awareness
- Drive infrastructure reproducibility and automation
- Align implementation with federated analytics principles
To avoid confusion:
❌ Not a pure architect
❌ Not a project manager
❌ Not a product owner
Required BackgroundStrong Fit Profiles
- Lead Backend Engineer transitioning into leadership
- Platform Engineering Lead
- Healthcare interoperability technical lead
- Data platform technical lead
- Distributed systems engineer with team leadership experience
Core Technical Experience
- Distributed systems or platform architecture delivery
- Cloud-native environments (GCP, Azure, Huawei or hybrid)
- Containerization & infrastructure automation
- Data pipelines and analytics platforms
- APIs and backend systems
Highly Valuable (but not mandatory)
- IRIS for Health or similar enterprise platforms
- Healthcare interoperability (FHIR / HL7)
- OMOP or clinical data models
- Federated analytics
Leadership Expectations
Given how Traverse operates globally, this person must be comfortable with:
- Remote-first teams across regions
- Rapid onboarding of new hospital nodes
- Working with evolving architecture decisions
- Balancing enterprise and open-source ecosystems
Success Criteria (First 6–12 Months)
- Deliver first production deployment aligned with architecture decision
- Standardize onboarding workflow for new hospitals
- Establish predictable engineering delivery cadence
- Reduce dependency on ad-hoc engineering coordination