Contract C++ Developer – Embedded Medical Device

About the role

AND Digital is recruiting four Embedded C++ Developers for an in-house backend engineering team building a highly regulated, safety-critical medical technology product. The role is based in London with 2 days onsite in Kings Cross, starts immediately and runs for 6 months. You will own a self-contained part of the application, taking work from initial design through to merged, tested and documented code, and work closely with the Software Architect and surrounding engineers.

Key responsibilities

• Alarms: develop alarm conditions from hardware and OS telemetry, implement patient sensor and signal quality alarms, and build fault handling and recovery mechanisms.
• Start-up, self-test and supervision: power-on checks, fail-safe states, watchdogs, session interruption detection, logging and audit logging.
• Patient data persistence: storage interfaces with atomic and checksummed writes, session listing, data packaging, queueing, flushing, retention and retrieval, and versioned interfaces to the GUI.
• Session lifecycle, power-down and service: session metadata, recovery, graceful shutdown, power-button handling, USB data export, software update support and log extraction.

Required profile

• Experienced Embedded C++ Engineer who has worked on Linux-based safety-critical, mission-critical or highly regulated products.
• Comfortable with formal quality processes, static analysis, code coverage and rigorous testing.
• Desirable: experience with medical devices, regulated environments or lifesciences, knowledge of IEC 62304, ISO 13485 or IEC 60601-1-8, and experience with state-machine supervisors and fault management.

Required skills

• C++17 on embedded Linux, RAII, std::atomic, multithreading, lock-free or bounded queues.
• Allocation-free runtimes, ports-and-adapters / hexagonal architecture and dependency injection.
• Linux services, watchdogs, IPC and serialization (FlatBuffers, Unix-domain sockets, named pipes).
• CMake, automated testing, CI/CD, cross-compilation (ideally aarch64), unit testing and code coverage.
• Formal engineering processes such as peer review and traceable changes.