About Us
Handtevy is a leading provider of pediatric and adult emergency care solutions. Our SaaS platform is used by hospitals, EMS agencies, and fire departments to deliver evidence-based medication dosing, standardized clinical protocols, and real-time coordination tools for emergency medical services. Our software is used in ambulances and emergency departments every day, in moments where clarity, speed, and reliability are not optional.
Position Overview
We are hiring a Senior Software Engineer focused on Enterprise API Integrations to lead the design and delivery of our growing integration ecosystem, with a near-term focus on ePCR, narcotic (controlled substance) tracking and blood product tracking platforms used by EMS agencies and hospitals.
This role is the technical owner of how Handtevy talks to the rest of the healthcare operations stack. Integrations here are bidirectional, and you will own both directions:
- Integrate Handtevy as a client with partner systems that already expose APIs.
- Expose Handtevy's APIs as the system of record for partners who need to consume our data.
You will work directly with our CTO, engineering leads, product, and partner engineering counterparts at integration partners. You will own the integration platform end-to-end: contracts, security, reliability, observability, and the partner-facing surface area.
What You'll Own
Integration architecture and delivery
- Architect and build bidirectional integrations between Handtevy and third-party platforms.
- Design integration patterns that fit the partner: REST, webhooks, polling with cursors, HL7 v2 (MLLP), and FHIR R4 resources where the partner supports it.
- Build resilient sync engines: idempotent writes, retry with exponential backoff and jitter, dead-letter queues, reconciliation jobs, and replay tooling. Assume partner APIs will go down, rate-limit, change schemas without warning, or send malformed data and design accordingly.
- Define and own the canonical internal data model that integration adapters map into and out of, so a new partner is an adapter, not a rewrite.
Handtevy's outbound API platform
- Evolve our public-facing API into a partner platform.
- Own API authentication and authorization for partners: OAuth 2.0 client credentials, JWT, scoped API keys, and per-tenant rate limiting.
- Drive developer experience for partners: OpenAPI specs as the source of truth, generated client examples, Postman collections, sandbox data, and partner-facing documentation.
Reliability, security, and compliance
- Contribute to SOC 2 controls in integration code paths: change management, access reviews, secret rotation, evidence collection.
- Build observability into every integration: structured logs, correlation IDs that follow a record across systems, metrics on partner latency and error rates, and alerting on silent failures (a partner that stops sending data is not a healthy partner).
- Champion test coverage, contract tests against partner sandboxes, and integration-specific chaos testing.
Cross-functional leadership
- Partner with Product and Engineering Leads to scope integrations, define success metrics, and prioritize the integration roadmap.
- Partner with Clinical, Customer Success, and Implementation teams on customer-specific deployment and configuration.
- Lead technical conversations with partner engineering teams. You will be the engineer on the call when their API doesn't behave as documented.
- Participate in architecture discussions, code reviews, sprint planning, and mentorship of other engineers.
Required Qualifications
Engineering foundation
- Bachelor's degree in Computer Science, Engineering, or related field.
- 5+ years of backend development, with meaningful time spent on integrations, API platforms, or partner-facing systems.
- Strong production experience with Node.js and NestJS (or a comparable typed, modular backend framework you can demonstrate transfers cleanly).
- Strong proficiency designing and consuming RESTful APIs, including pagination, idempotency, error contracts, and versioning strategy.
- Deep understanding of authentication and authorization: OAuth 2.0 (authorization code, client credentials, refresh flows), JWT (signing, validation, key rotation), SSO/SAML, API keys, and mTLS.
Integration-specific depth
- Hands-on experience designing resilient integration patterns.
- Experience with webhooks as both producer and consumer: signing, verification, replay, and at-least-once delivery semantics.
- Experience with OpenAPI/Swagger as a contract, not just documentation.
- Comfort reading vendor API docs critically and finding the gaps before they bite you in production.
Data, infrastructure, and tooling
- Proficiency with relational and NoSQL databases:
- SQL: MySQL (optional: PostgreSQL, MSSQL)
- NoSQL: MongoDB / DocumentDB (optional: Redis, DynamoDB)
- ORMs: TypeORM (optional: Sequelize, Prisma)
- Experience with AWS services relevant to integrations: Aurora, SQS / SNS / EventBridge, Lambda, Secrets Manager, API Gateway, CloudWatch, S3, SES, CloudFront.
- Hands-on with Docker, Git, and CI/CD pipelines (GitHub Actions, Bitbucket Pipelines).
- Strong grasp of software design patterns, security best practices, and distributed system tradeoffs.
- Excellent collaboration and written communication. You will write integration specs and partner-facing docs, not just code.
Nice to Have
- Awareness of HIPAA requirements as they apply to engineering.
- Direct integration experience with controlled substance tracking platforms; familiarity with DEA recordkeeping, CSOS, and PDMP concepts.
- Direct experience integrating with blood product tracking systems and familiarity with ISBT 128 labeling and AABB standards.
- Integration experience with ePCR platforms (ESO, ImageTrend, Zoll, etc) or hospital EHRs (Epic, Cerner / Oracle Health, Meditech) via HL7, FHIR, or proprietary APIs.
- Experience standing up a partner / developer portal or public API documentation site.
- Familiarity with PHP and Laravel.
- Event-driven architecture experience: Kafka, Kinesis, EventBridge, or similar.
- Observability platforms: Datadog, New Relic, or similar.
Our Engineering Culture
- We use NestJS, TypeORM, Aurora MySQL, DocumentDB, and Angular with Tailwind in production.
- We leverage AI-assisted development (Claude Code, GitHub Copilot) and expect engineers to use these tools thoughtfully and well.
We invest in observability, testing, and clean architecture - - not just speed.
- Engineers have real input into tooling, architectural decisions, and technical direction.
Benefits
- Competitive salary commensurate with experience.
- Comprehensive health, dental, and vision coverage.
How to Apply
Submit your resume and a short note about an integration you're proud of. What made it hard, what you'd do differently, and how you knew it was working in production.
