Above all: a "can do", solution-oriented mentality — someone who picks up new technical areas quickly rather than someone who already has years of depth in every tool we use
Background in Software Engineering or Backend Development, with 3+ years building integrations between systems — Java preferred; comparable depth in another JVM/backend language is also welcome
Demonstrable production integration work: routing and transformation, mapping between systems with different data models, error handling, and automated testing of interfaces. Apache Camel experience is a plus since it's our orchestration layer, but not a requirement
Working knowledge of REST APIs (auth, versioning, error handling) — depth in idempotency/versioning nuances can be picked up on the job
Comfortable working with Infrastructure as Code (Terraform, OpenTofu, Pulumi, or AWS CDK) — prior hands-on experience is a plus, not a requirement
Basic understanding of security fundamentals for cross-organizational interfaces (mTLS, certificates, secrets management) — willingness and ability to get up to speed here matters more than existing depth
Proficiency with Linux and scripting in Python or Bash
The ability to sit with a hospital IT architect or a laboratory manager and agree an interface without either side leaving the room confused
English at professional level, written and spoken
Responsibilities
Above all: a "can do", solution-oriented mentality — someone who picks up new technical areas quickly rather than someone who already has years of depth in every tool we use
Background in Software Engineering or Backend Development, with 3+ years building integrations between systems — Java preferred; comparable depth in another JVM/backend language is also welcome
Demonstrable production integration work: routing and transformation, mapping between systems with different data models, error handling, and automated testing of interfaces. Apache Camel experience is a plus since it's our orchestration layer, but not a requirement
Working knowledge of REST APIs (auth, versioning, error handling) — depth in idempotency/versioning nuances can be picked up on the job
Comfortable working with Infrastructure as Code (Terraform, OpenTofu, Pulumi, or AWS CDK) — prior hands-on experience is a plus, not a requirement
Basic understanding of security fundamentals for cross-organizational interfaces (mTLS, certificates, secrets management) — willingness and ability to get up to speed here matters more than existing depth
Proficiency with Linux and scripting in Python or Bash
The ability to sit with a hospital IT architect or a laboratory manager and agree an interface without either side leaving the room confused
Linked-in
Google