Engineering Manager (Digital Health & AI)

Software Engineering Manager (Digital Health & AI)Abu Dhabi, United Arab Emirates | Posted on 03/01/2026Housecall is a tech-enabled primary care company delivering virtual and in-person care with a mission to measurably improve healthcare outcomes and people’s quality of life.Job DescriptionWe’re hiring an Engineering Manager to lead a small, fast-growing engineering team while remaining meaningfully hands‑on. You’ll partner closely with Product and Clinical stakeholders to deliver predictable outcomes, establish durable quality and release practices, and raise the bar on reliability, resiliency, and security. You’ll help the team build and integrate systems that support core healthcare workflows, including EMR/EHR‑adjacent capabilities and third‑party clinical integrations.This is a player/coach role. You will spend your time across people leadership and delivery ownership (team health, execution, stakeholder alignment) and hands‑on technical contribution (high‑leverage coding, reviews, pairing, architecture guidance). Hands‑on contribution typically starts around ~30–50% and flexes with team needs as we scale.Team and ScopeLead a single, small product engineering team (growing headcount).Work in a mixed backend stack: PHP/Laravel and TypeScript/Node.js.Cloud environment: Azure preferred (or equivalent) with infrastructure managed via Terraform.Reliability and operational ownership are part of product engineering (incident response, runbooks, postmortems).On‑call is shared team ownership; rotation details will be discussed during the process.What Success Looks LikeIn the first ~90 days:Delivery cadence is clearer: backlog is healthier, priorities are explicit, and stakeholders understand tradeoffs.The team has a crisp Definition of Done and lightweight release readiness criteria.You’ve shipped meaningful product work while improving at least one reliability/quality choke point (tests, CI/CD, observability, release safety, etc.).One high‑impact integration or workflow area (e.g., scheduling, charting, labs, messaging, payments/billing, referrals) has clearer ownership, reliability, and delivery cadence.In ~6 months:Delivery is predictable with a consistent planning/review rhythm and fewer last‑minute surprises.Quality improves measurably: fewer regressions, faster diagnosis, and smoother releases.Reliability and resiliency practices are routine (good alerts, runbooks, postmortems with follow‑through).Security/compliance practices are embedded (traceability, least privilege, audit readiness).Integrations are easier to ship and safer to operate (clear contracts, monitoring, retries/idempotency, well‑defined failure handling).RequirementsPeople and Culture:Lead, coach, and grow engineers through 1:1s, feedback, performance management, and career development.Build a healthy team environment with strong ownership, continuous improvement, and sustainable pace.Hire and onboard effectively: role definition, structured interviews, and high‑quality onboarding.Delivery and Planning (Scrum, pragmatically):Own execution: turn priorities into plans, manage scope and dependencies, and communicate timelines and risks clearly.Run (or ensure strong ownership of) Scrum rituals to support predictability: backlog refinement, sprint planning, stand‑ups, reviews/demos, and retrospectives—adapting as needed to maximize outcomes.Partner with Product and Clinical stakeholders to clarify requirements, make tradeoffs explicit, and deliver incrementally.Technical Leadership (Player/Coach):Contribute directly to the codebase in high‑leverage areas (critical paths, reliability/security work, complex features).Provide architectural guidance across Laravel and Node.js services: clean interfaces, ownership boundaries, and maintainable patterns.Guide integration patterns and operational practices for third‑party systems (clear contracts, versioning, monitoring, safe retries, and failure modes).Uphold code quality through reviews, pairing, and mentorship, avoiding bottlenecks by enabling the team to own decisions.Quality and Release Excellence (QA as a system):Establish lightweight, scalable quality practices (not a separate QA org):Clear Definition of Done and release readiness checksTest strategy and automation (unit/feature/integration/contract/E2E as appropriate)Risk‑based testing for patient‑ and clinician‑facing workflowsImprove CI/CD with practical quality gates (tests, linting, security checks, deploy safety) and a smooth developer workflow.Reliability, Resiliency, Security, and Cloud Operations:Strengthen observability (metrics/logging/tracing), alerting, and runbooks to reduce time‑to‑diagnosis and time‑to‑recovery.Lead incident practices and ensure follow‑through: incident response, postmortems, and durable corrective actions.Drive resiliency improvements: timeouts/retries, idempotency, rate limiting, queue robustness, graceful degradation, backups, and recovery readiness.Embed secure engineering practices: least privilege, secrets