Description:
Role Overview
We are seeking a Backend Lead Engineer to provide day-to-day technical leadership for our API team. In this critical role, you will convert architectural vision into scalable, production-ready APIs and services, integrating healthcare standards such as FHIR, enabling secure deployments on GCP, and supporting AI-enabled workflows. You will collaborate closely with architects and cross-functional teams to maintain the security, reliability, and interoperability of our platform.
Requirements:
Key Responsibilities
-
Lead API design and implementation for internal platform services, partner integrations, and interoperability workflows.
-
Translate architecture and security standards into concrete service patterns, interface contracts, and coding standards for the team.
-
Design and develop FHIR-based APIs, including resource mapping, validation, and interoperability workflows.
-
Lead the technical implementation of MCP wrappers around key APIs and services, enabling AI-driven agents to safely access approved tools and data.
-
Conduct design and code reviews; mentor backend, DevOps, and QA team members.
-
Collaborate with architects to enforce security best practices, auditability, tenant isolation, and operational reliability across deployments.
Qualifications
-
7-10 years of backend or API engineering experience with demonstrable technical leadership.
-
Proven expertise designing RESTful APIs, including service contracts, versioning strategies, error handling, and scalability.
-
Hands-on experience with FHIR APIs and healthcare interoperability standards.
-
Experience building or exposing APIs and services to support AI or agent-based workflows; familiarity with MCP is strongly preferred.
-
Proficient with GCP services such as Cloud Run, GKE, Pub/Sub, Cloud SQL, API Gateway, IAM, logging, and monitoring.
-
Excellent communication skills, with the ability to guide and lead execution in a fast-paced environment.
Preferred Experience
-
Background in healthcare, payer operations, or working with regulated data environments.
-
Familiarity with event-driven architectures and asynchronous processing patterns.
