Integration Clinical Engineer
Kontakt.io
RemoteRemoteFull Time
Job Description
Kontakt.io is building the platform that care operations run on.
We reduce waste, cut costs, and improve throughput in hospitals by automating and orchestrating clinical workflows. Using AI, real-time location data (RTLS), and deep EHR integration, our platform enables care teams to operate with real-time intelligence and financial discipline—improving outcomes for patients and operators alike.
We work with some of the largest and most complex healthcare systems in the U.S. Our technology lives inside hospitals, alongside EHRs, nurse call systems, staffing tools, and operational platforms that cannot fail.
We are hiring an Integration Clinical Engineer to make sure it doesn’t.
Why this role is compelling.
This is not a back-office integration role. This is a frontline execution role.
You will work at the seam where hospital reality meets product ambition—where integrations either unlock real value or quietly break deployments. You will see firsthand how hospitals actually operate, not how diagrams say they should.
This role has real leverage:
- Direct impact on successful deployments and customer trust
- Deep exposure to hospital IT, clinical workflows, and operational constraints
- Tight partnership with Deployment Project Managers and customer stakeholders
- Influence on how our product integrates, scales, and evolves in the field
When integrations work, deployments accelerate and customers expand.
When they don’t, nothing else matters.
Why we are hiring an Integration Clinical Engineer
As Kontakt.io scales, integrations are no longer “one-off technical tasks.” They are core infrastructure.
Hospitals expect our platform to integrate cleanly with EHRs, ADT feeds, nurse call systems, staff scheduling tools, and other clinical and operational systems—often under tight timelines and real clinical pressure.
We are hiring this role to:
- Own integration quality during deployments
- Reduce friction between hospital IT, clinical teams, and our internal teams
- Ensure integrations reflect real clinical workflows, not just technical specs
- Raise the bar on how we design, test, and operationalize integrations
This role exists to protect deployments from silent failure modes.
Who this role is for
This role is for someone who is comfortable living between systems and people.
You are technically strong, but you don’t hide behind documentation or APIs. You can sit with hospital IT, talk through constraints, and still translate that into concrete integration decisions.
You understand that:
- Hospital systems are messy, political, and mission-critical
- Clinical workflows rarely match “standard” implementations
- Integration failures often show up as operational pain, not error logs
You take ownership. You follow issues to resolution. You don’t wait for perfect requirements. And you’re comfortable being the person everyone pulls into the room when something isn’t working.
What you will own
You will own the clinical and technical integrity of integrations during deployment, including:
Hospital system integrations
- Integrating Kontakt.io with hospital systems such as EHR/EMR, ADT, nurse call, staffing, and operational platforms
- Supporting and validating integrations using APIs, HL7, FHIR, or other healthcare data exchange methods
- Mapping real clinical workflows to system data flows and configurations
Deployment execution
- Partnering closely with Deployment Project Managers during implementation
- Supporting deployment planning, integration testing, go-live, and stabilization
- Participating in onsite or remote customer sessions as needed
Customer & clinical collaboration
- Acting as a technical bridge between hospital IT, clinical stakeholders, and internal teams
- Explaining integration behavior, limitations, and tradeoffs clearly and honestly
- Helping customers understand how to operationalize integrations effectively
Troubleshooting & improvement
- Diagnosing and resolving integration issues in production environments
- Supporting post-deployment optimization and expansion use cases
- Documenting integration patterns, risks, and best practices for scale
Internal feedback loop
- Providing grounded feedback to Product and Engineering based on field reality
- Helping shape integration standards, tooling, and deployment playbooks
- Improving repeatability and reducing deployment risk over time
What success looks like (6–12 months)
- Integrations consistently work at go-live, not weeks later
- Deployment teams rely on you as a critical execution partner
- Hospital IT teams trust Kontakt.io’s integration approach
- Integration-related deployment delays and escalations decrease materially
- Integration patterns are documented, repeatable, and scalable
- Product and Engineering decisions reflect real-world hospital constraints
What it takes to win here
- Experience working with hospital IT systems or clinical environments
- Hands-on integration experience (APIs, HL7, FHIR, or similar)
- Strong understanding of clinical and operational workflows
- Comfort operating in live hospital environments with real consequences
- Clear communication with both technical and non-technical stakeholders
- Bias toward ownership, follow-through, and pragmatic problem-solving
- Willingness to travel to customer sites when needed
Bonus points for:
- RTLS, IoT, or healthcare operations technology experience
- Prior deployment, implementation, or solutions engineering roles
- Background in biomedical engineering, health informatics, or healthcare IT
In short
If you like working where:
- Software meets clinical reality
- Integrations are mission-critical, not theoretical
- Execution quality directly affects customer trust
You can see the impact of your work inside real hospitals—this role is built for you.
We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us.
We reduce waste, cut costs, and improve throughput in hospitals by automating and orchestrating clinical workflows. Using AI, real-time location data (RTLS), and deep EHR integration, our platform enables care teams to operate with real-time intelligence and financial discipline—improving outcomes for patients and operators alike.
We work with some of the largest and most complex healthcare systems in the U.S. Our technology lives inside hospitals, alongside EHRs, nurse call systems, staffing tools, and operational platforms that cannot fail.
We are hiring an Integration Clinical Engineer to make sure it doesn’t.
Why this role is compelling.
This is not a back-office integration role. This is a frontline execution role.
You will work at the seam where hospital reality meets product ambition—where integrations either unlock real value or quietly break deployments. You will see firsthand how hospitals actually operate, not how diagrams say they should.
This role has real leverage:
- Direct impact on successful deployments and customer trust
- Deep exposure to hospital IT, clinical workflows, and operational constraints
- Tight partnership with Deployment Project Managers and customer stakeholders
- Influence on how our product integrates, scales, and evolves in the field
When integrations work, deployments accelerate and customers expand.
When they don’t, nothing else matters.
Why we are hiring an Integration Clinical Engineer
As Kontakt.io scales, integrations are no longer “one-off technical tasks.” They are core infrastructure.
Hospitals expect our platform to integrate cleanly with EHRs, ADT feeds, nurse call systems, staff scheduling tools, and other clinical and operational systems—often under tight timelines and real clinical pressure.
We are hiring this role to:
- Own integration quality during deployments
- Reduce friction between hospital IT, clinical teams, and our internal teams
- Ensure integrations reflect real clinical workflows, not just technical specs
- Raise the bar on how we design, test, and operationalize integrations
This role exists to protect deployments from silent failure modes.
Who this role is for
This role is for someone who is comfortable living between systems and people.
You are technically strong, but you don’t hide behind documentation or APIs. You can sit with hospital IT, talk through constraints, and still translate that into concrete integration decisions.
You understand that:
- Hospital systems are messy, political, and mission-critical
- Clinical workflows rarely match “standard” implementations
- Integration failures often show up as operational pain, not error logs
You take ownership. You follow issues to resolution. You don’t wait for perfect requirements. And you’re comfortable being the person everyone pulls into the room when something isn’t working.
What you will own
You will own the clinical and technical integrity of integrations during deployment, including:
Hospital system integrations
- Integrating Kontakt.io with hospital systems such as EHR/EMR, ADT, nurse call, staffing, and operational platforms
- Supporting and validating integrations using APIs, HL7, FHIR, or other healthcare data exchange methods
- Mapping real clinical workflows to system data flows and configurations
Deployment execution
- Partnering closely with Deployment Project Managers during implementation
- Supporting deployment planning, integration testing, go-live, and stabilization
- Participating in onsite or remote customer sessions as needed
Customer & clinical collaboration
- Acting as a technical bridge between hospital IT, clinical stakeholders, and internal teams
- Explaining integration behavior, limitations, and tradeoffs clearly and honestly
- Helping customers understand how to operationalize integrations effectively
Troubleshooting & improvement
- Diagnosing and resolving integration issues in production environments
- Supporting post-deployment optimization and expansion use cases
- Documenting integration patterns, risks, and best practices for scale
Internal feedback loop
- Providing grounded feedback to Product and Engineering based on field reality
- Helping shape integration standards, tooling, and deployment playbooks
- Improving repeatability and reducing deployment risk over time
What success looks like (6–12 months)
- Integrations consistently work at go-live, not weeks later
- Deployment teams rely on you as a critical execution partner
- Hospital IT teams trust Kontakt.io’s integration approach
- Integration-related deployment delays and escalations decrease materially
- Integration patterns are documented, repeatable, and scalable
- Product and Engineering decisions reflect real-world hospital constraints
What it takes to win here
- Experience working with hospital IT systems or clinical environments
- Hands-on integration experience (APIs, HL7, FHIR, or similar)
- Strong understanding of clinical and operational workflows
- Comfort operating in live hospital environments with real consequences
- Clear communication with both technical and non-technical stakeholders
- Bias toward ownership, follow-through, and pragmatic problem-solving
- Willingness to travel to customer sites when needed
Bonus points for:
- RTLS, IoT, or healthcare operations technology experience
- Prior deployment, implementation, or solutions engineering roles
- Background in biomedical engineering, health informatics, or healthcare IT
In short
If you like working where:
- Software meets clinical reality
- Integrations are mission-critical, not theoretical
- Execution quality directly affects customer trust
You can see the impact of your work inside real hospitals—this role is built for you.
We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us.