Cera Care Ltd
You'll be embedded in our engineering team, building the surfaces that clinical operators, carers, and clients rely on every day. Cera is the UK's largest home-care provider; what you ship directly affects care delivery at scale. We are rebuilding the technology platform to be event-based, multi-tenant, and agent-ready using .NET on Kafka and Postgres for the new estate. The legacy platform remains active while domains migrate. Our small, senior team works closely with the business. We ship on a modern stack and use Claude Code by default. We seek a pragmatic engineer who takes ownership across new and legacy platforms and delivers reliably. Responsibilities Work in a domain on the new platform. Scheduler, finance, care planning, operator surfaces, or whichever needs the next push. The architectural choices in your domain have been in place for years. Ship. NET/C # across the event-sourced estate. Typed contracts, gateways, projections, the lot. Build agents as ordinary services. Bounded remit, defined role, audit trail, recall procedure. The same standards we apply to human operators. Migrate domains from the legacy platform. A bridge runs in parallel, so old and new live alongside until the evidence says it is safe to switch. Strong legacy-stack instincts matter here (as does experience implementing the Strangler Fig pattern successfully). Push agentic coding. Claude Code, Copilot, Cursor, or whatever ships fastest. Contribute back to our shared foundational framework. Communicate with the business. Operations, clinical, finance, commercial. Understand how the work happens, then build from there. Keep CQC and clinical audit baked in. Audit by default is the architecture, not a feature. Own the platform. CI/CD, observability, deployment, AWS or GCP. Small team, you will touch everything. Qualifications and Skills We're looking for a Senior Backend Engineer who simplifies, ships, and owns their work. Someone who is equally comfortable navigating new platforms and legacy systems within an organisation. From a technology perspective, we are looking for someone who has experience with: .NET/C # at a senior level. Real command of the language and the runtime. Domain modelling / DDD experience. You know how to slice complex systems into the right boundaries, reducing complexity and increasing maintainability and business collaboration. Event sourcing, CQRS, and event streaming in production. Akka.NET, EventStore, Marten, Kafka, or similar. You understand event-sourced systems beyond the marketing, where you apply and where you don't. Postgres at scale. Schema design, performance, multi-tenant patterns. Real legacy-migration instinct. You have lifted production systems off old foundations onto new ones, with a bridge running in parallel, without breaking the business. Multi-tenant architecture. You know what makes tenant isolation real and what makes it leaky. Beyond the technical skills, we are looking for: AI-native by default. Claude Code, Copilot, Cursor - these are already how you work, not tools you're evaluating. You can point to what they've unlocked for you. Ownership instinct. You see a problem and take it. You don't wait to be assigned. Prioritise issues yourself and move them forward without needing handholding. Pragmatism. You ship the smallest thing that works, then iterate. Done beats perfect. Prioritise the work that delivers value fastest, then improve it from there. Business curiosity. You go find out how the work actually happens, not just how the spec describes it. Learning speed. The stack changes. You don't get attached to what you learned last year. Low ego. You can be wrong, change course, and give credit where it's due. These aren't required, but they'll make you stand out: Regulated industry experience (health tech, social care, fintech, defence). Compliance and audit-aware engineering shortens ramp time. Building LLM-powered features in production, evals, drift monitoring, observability. Scheduling, matching, or constraint-solving algorithms at production scale. Tele-ICU-like, command-centre, or supervised-automation systems from any domain.
You'll be embedded in our engineering team, building the surfaces that clinical operators, carers, and clients rely on every day. Cera is the UK's largest home-care provider; what you ship directly affects care delivery at scale. We are rebuilding the technology platform to be event-based, multi-tenant, and agent-ready using .NET on Kafka and Postgres for the new estate. The legacy platform remains active while domains migrate. Our small, senior team works closely with the business. We ship on a modern stack and use Claude Code by default. We seek a pragmatic engineer who takes ownership across new and legacy platforms and delivers reliably. Responsibilities Work in a domain on the new platform. Scheduler, finance, care planning, operator surfaces, or whichever needs the next push. The architectural choices in your domain have been in place for years. Ship. NET/C # across the event-sourced estate. Typed contracts, gateways, projections, the lot. Build agents as ordinary services. Bounded remit, defined role, audit trail, recall procedure. The same standards we apply to human operators. Migrate domains from the legacy platform. A bridge runs in parallel, so old and new live alongside until the evidence says it is safe to switch. Strong legacy-stack instincts matter here (as does experience implementing the Strangler Fig pattern successfully). Push agentic coding. Claude Code, Copilot, Cursor, or whatever ships fastest. Contribute back to our shared foundational framework. Communicate with the business. Operations, clinical, finance, commercial. Understand how the work happens, then build from there. Keep CQC and clinical audit baked in. Audit by default is the architecture, not a feature. Own the platform. CI/CD, observability, deployment, AWS or GCP. Small team, you will touch everything. Qualifications and Skills We're looking for a Senior Backend Engineer who simplifies, ships, and owns their work. Someone who is equally comfortable navigating new platforms and legacy systems within an organisation. From a technology perspective, we are looking for someone who has experience with: .NET/C # at a senior level. Real command of the language and the runtime. Domain modelling / DDD experience. You know how to slice complex systems into the right boundaries, reducing complexity and increasing maintainability and business collaboration. Event sourcing, CQRS, and event streaming in production. Akka.NET, EventStore, Marten, Kafka, or similar. You understand event-sourced systems beyond the marketing, where you apply and where you don't. Postgres at scale. Schema design, performance, multi-tenant patterns. Real legacy-migration instinct. You have lifted production systems off old foundations onto new ones, with a bridge running in parallel, without breaking the business. Multi-tenant architecture. You know what makes tenant isolation real and what makes it leaky. Beyond the technical skills, we are looking for: AI-native by default. Claude Code, Copilot, Cursor - these are already how you work, not tools you're evaluating. You can point to what they've unlocked for you. Ownership instinct. You see a problem and take it. You don't wait to be assigned. Prioritise issues yourself and move them forward without needing handholding. Pragmatism. You ship the smallest thing that works, then iterate. Done beats perfect. Prioritise the work that delivers value fastest, then improve it from there. Business curiosity. You go find out how the work actually happens, not just how the spec describes it. Learning speed. The stack changes. You don't get attached to what you learned last year. Low ego. You can be wrong, change course, and give credit where it's due. These aren't required, but they'll make you stand out: Regulated industry experience (health tech, social care, fintech, defence). Compliance and audit-aware engineering shortens ramp time. Building LLM-powered features in production, evals, drift monitoring, observability. Scheduling, matching, or constraint-solving algorithms at production scale. Tele-ICU-like, command-centre, or supervised-automation systems from any domain.