Implementation Manager

Translate approved client solutions and requirements into a technical work breakdown covering configuration, integrations, data, environments, testing, deployment and documentation.

Configure OpenLoop’s platform and implementation-specific workflows using established standards and reusable patterns.

Implement and validate client and third-party integrations using APIs, webhooks, authentication, data mapping and other supported connectivity methods.

Execute data migration, cleanup, transformation, backfill and reconciliation activities.

Use SQL, APIs, logs, payloads, configuration tools and AI-assisted scripting or development to complete implementation work and diagnose problems.

Configure event-driven automation and triggering logic across the platform (user creation, firing downstream workflow actions when defined conditions are met, etc)

Partner directly with client technical teams to clarify requirements, exchange specifications, resolve integration issues and validate expected behavior.

Build and execute technical test plans covering complete workflows, failure paths, retries, duplicate events, data integrity, permissions and external dependencies.

Prepare the technical environments, data and functionality required for UAT; resolve technical defects and provide evidence to the TPM and other readiness owners.

Determine whether the implemented solution meets OpenLoop’s technical definition of done and provide technical sign-off.

Troubleshoot implementation and production-stabilization issues by comparing expected with actual behavior, isolating the failing layer and establishing reproducible evidence.

Distinguish configuration issues, deployment defects, data problems, client integration failures, third-party failures and genuine OpenLoop product gaps.

Resolve implementation-owned issues directly and escalate genuine product defects or capability gaps with clear reproduction steps, evidence, impact and required behavior.

Protect the long-term supportability of the platform by using standard configuration and integration patterns whenever possible.

Identify when a client request requires an approved exception, reusable implementation capability or Product and Engineering support.

Produce and maintain complete technical documentation, including configuration records, mappings, integration specifications, deployment notes, test evidence, known limitations and as-built implementation details.

Provide the Technical Project Manager with accurate estimates, technical status, dependencies, risks and changes affecting the integrated plan.

Support go-live and stabilization, then transition the implementation cleanly into Support and Customer Success with current documentation and clear ownership.

Use AI thoughtfully to accelerate configuration, scripting, debugging, test creation and documentation while personally validating the accuracy and safety of the resulting work.

Contribute reusable configurations, scripts, test packs, documentation and implementation patterns that make future launches faster and more reliable.

Operationally and clinically fluent: Understand the operational and clinical processes a system serves (not just its technical components) and can translate a requirement or clinical protocol into patient workflows that reflect how the care actually happens. Validate the journey from the patient's and operator's perspective, not only the system's.

A technical builder: You want to configure, integrate, test and troubleshoot—not merely coordinate the people doing that work.

A complete-journey thinker: You consider how the full patient and operational workflow functions, not only whether one API returned a successful response.

Evidence-driven: You use logs, payloads, configuration records, database results and test evidence to establish what is happening.

Pragmatic about implementation design: You prefer a supported standard pattern over an elegant one-off solution that no one can maintain.

Customer-facing: You can work directly with a client’s engineers, operators and business stakeholders without losing technical precision.

Accountable through production: You do not declare success when configuration is complete; you remain responsible through validation, launch and stabilization.

Clear about product boundaries: You solve implementation problems inside implementation and escalate only genuine product defects or capability gaps.

Comfortable with ambiguity: You can turn incomplete requirements into concrete technical questions, assumptions and validation steps.

Careful with healthcare consequences: You understand that incorrect identity, eligibility, clinical, prescription, pharmacy or lab behavior can affect real patient care.

Able to build while the system evolves: You can deliver live client work while also strengthening the reusable patterns and documentation behind it.

Self Starter: You can prioritize and execute on your own within an ambiguous environment.

We have a relatively flat organizational structure here at OpenLoop. Everyone is encouraged to bring ideas to the table and make things happen. This fits in well with our core values of Autonomy, Competence and Belonging, as we want everyone to feel empowered and supported to do their best work.

Sound like a good fit? We’d love to meet you.