Senior Telephony/Cloud Engineer — NHS Patient Verification System (InCore)

Client: Manchester, UK healthtech startup
Engagement: 1 month initial contract, part-time or full-time (20–40 hrs/week), immediate start
Location: UK strongly preferred; other Europe considered
Extension potential: Strong — client plans Stages 2–4 (~1 year total) with the same engineer if Stage 1 delivers well

#### The Role
Hands-on build role. You're completing and hardening Stage 1 of InCore: the AI-driven patient verification layer that runs before callers enter the queue at NHS GP practices (name/DOB/address verification via the NHS PDS-FHIR API). ~80% of the architecture is already built — you're closing gaps, bringing it to production grade, and preparing it for NHS submission.

#### What you'll do
- Complete and harden the existing verification architecture (currently prototype-grade, not production-grade)
- Build/finalize the call verification flow on 3CX (NHS-compliant PBX) running on AWS
- Design for failure — this step gates the entire call flow and must be resilient
- Prepare and submit technical documentation to the NHS for PDS-FHIR API access approval, and manage any NHS pushback/review cycle
- Work in weekly sprints (2-sprint delivery cycle); submit weekly work reports for approval

#### Must-have
- Production-grade cloud architecture experience (AWS)
- NHS system experience, OR direct 999/emergency line telephony experience — via NHS directly, or through NHS-contracted firms (e.g., BT, or similar vendors building for the NHS)
- PBX/telephony systems experience, ideally with 3CX
- Track record shipping production systems, not just prototypes/POCs

#### Nice-to-have
- Prior direct work with 3CX
- Experience with NHS frameworks and compliance documentation submission