Join the team.
We're looking for people who want to digitise care with us — pragmatic, ambitious, with heart.
Solve our challenge — and every application gets read.
We're not advertising specific roles right now, but good people are always welcome. If one of the topic areas below sparks something for you, solve the challenge and send it along with your speculative application. Doing that earns you our full attention.
- Software · Frontend
Care UI nobody has to explain.
You build accessible, fast web interfaces — with non-tech-savvy family carers in mind.
Your challengeSend your solutionBuild a Care-Level Quick-Check mini web app in at most one day: at least five questions with real scoring logic (e.g. MDK-style module weighting), plus a dedicated result screen with the recommended care level. Stack of your choice — show us your favourite setup (Astro, React, Solid, Vue). Equal weight on four criteria: visual quality — this thing has to look really good (typography, spacing, micro-animation, considered result page); accessibility (tab order, screen reader, contrast); performance (LCP under 1.5 s in Lighthouse); and code quality. Send us the repo link plus a live demo.
- Software · Backend
Predict stock instead of reordering.
You build APIs and services that handle millions of order and approval records — cleanly and fast.
Your challengeSend your solutionBuild a production-ready service — no sketch: HTTP API + database + tests + Dockerfile + `docker-compose`. We provide a JSON sample of ~100 000 historic orders across 24 months including seasonal patterns, gaps from supply outages and three care insurers with different approval rates. Implement a `POST /forecast` endpoint returning a 7-day demand forecast per product SKU — with a confidence interval (so not “will run short” but “92 % probability of < 50 units by day 5”) and p99 < 200 ms at 50 req/s warm. We grade: clean domain modelling, ≥ 70 % test coverage (unit + integration), structured logs plus at least three meaningful metrics, idempotency and graceful handling of broken input, and a README with your architecture decisions plus two or three sentences on why your forecasting approach fits this dataset. Bonus: a paragraph on how you'd monitor model drift in production. Language and database of your choice. Repo link plus a `docker-compose up`-able stack.
- Marketing · Brand & Performance
Care content people don't scroll past.
You translate complex care topics into messages that land — with family carers as well as with insurers.
Your challengeSend your solutionWrite a LinkedIn post (max 800 characters) that convinces family carers to claim sanus+ for free for their loved ones. We grade clarity, empathy and a concrete call-to-action. Bonus: sketch a 30-second video storyboard you'd publish alongside the post.
- Customer support · Care hotline
Win back trust — in one email.
You are the voice of sanus+ on the phone and in email — empathetic, solution-driven, no canned phrases.
Your challengeSend your solutionA customer writes, frustrated: “My box was late again — the third delay in a row. I'm cancelling.” Reply to her in an email. We grade tone, a concrete fix and whether you manage to rebuild her trust — without boilerplate. Max one A4 page.