Freelance Web Engineer (Vue/Nuxt + Sanity)

About kaiko

Clinicians and nurses work under heavier pressure than ever. More patients, more data, more decisions to make. kaiko gives them back the focus, time, and headspace they need to give patients the best possible care.

kaiko is a European clinical AI lab, and one of the only companies working across the full stack. Our approach spans three layers: our own frontier models, a clinical AI workspace built for complex hospital needs and workflows ranging from preparation and decision support to diagnostics and interpretation.

Our product is in daily use at leading European hospitals, reducing preparation time and cognitive workload for clinical teams. The next decade of European healthcare will be shaped by AI. We're here to shape it in the best way possible. kaiko is a well-funded company with a growing international team, operating from Amsterdam and Zurich.

About the role

We are looking for a freelancer to own kaiko.ai end to end: the code, the CMS, the hosting, the tracking and the performance. The site runs on Nuxt, uses Sanity as its CMS and is hosted on Netlify.

You would be working directly with our Head of Marketing, our designer and our content team. There is no engineering manager between you and the work, which means you need to be comfortable turning a marketing goal into technical decisions on your own.

Some areas of responsibility

• New pages, components, campaign pages and event pages in Nuxt

• Sanity schema design, so our content team can publish independently

• Maintenance: dependency and framework upgrades, bugs, cross-browser and mobile issues

• Technical SEO and performance: Core Web Vitals, metadata, sitemaps, structured data, redirects

• Hosting and infrastructure: Netlify configuration, build pipeline, preview deploys, DNS, domains

• Embedding interactive figures that our research team builds as standalone HTML files, including lazy loading, style isolation and mobile behaviour

• A reusable CMS template so the content team can add new figures without a developer

• Forms, tracking and consent, including HubSpot

• Implementing our designer's work, including states, responsive behaviour and interaction detail

• Accessibility improvements

• Documentation, so the setup stays transferable

Not in scope

• Brand and visual design. Our designer owns this.

• Content strategy and copy. Our marketing team owns this.

• Building the interactive figures themselves. Our research team does this.

• Product engineering. Separate team and codebase.

About you

• Nuxt and Vue in production, including framework upgrades and long-term maintenance

• Strong JavaScript, TypeScript, HTML and CSS. You are comfortable integrating HTML and JavaScript written by other people, including embedding self-contained files into an SSR app without hurting performance.

• Sanity or a comparable headless CMS, including schema design for non-technical editors

• You handle your own deploys: Netlify or Vercel, DNS, redirects, preview environments, and you have migrated a live site between hosting accounts without downtime

• Marketing site fundamentals: SEO, performance, forms, tracking, consent

• You work with a marketing team rather than an engineering manager. You take a goal, turn it into technical work, say when something is a bad idea, and document what you did.

Helpful, not required: HubSpot, Figma to code design system workflows, WCAG 2.2 AA, multilingual sites, data visualisation libraries.

How we work

• A monthly retainer covers maintenance, infrastructure, tracking and small changes, with an agreed response time for urgent issues

• Larger builds are scoped and quoted separately at the same day rate

Our interview process

Our process is designed to assess mutual fit across craft, motivation and values. It typically includes the following steps:

1. Intro call, 30 minutes. Background, our setup, rate, availability.

1. Send us: two or three sites you built and still maintain, with one line on what you own in each

1. Technical call, 45 minutes. We walk through the codebase and a real problem from our backlog.

1. Two references from clients you worked with for longer than six months.