CV / 2026Valencia, Spain (remote)Available for senior IC roles

Oliver Kaikane Gate

Seven years as a full stack developer, specialising in all things front end. Right now I'm focused on agentic engineering: working out the practices and workflows that are safe, efficient, and don't produce spaghetti.

Open to relocation to Amsterdam and The Hague · Highly Skilled Migrant sponsorship

01

Personal

Came to engineering from Philosophy of Technology. That training taught me to question the framing of a problem before answering it. Junior full stack to leading a five-person frontend team along the way.

I'm a tested full stack developer and I love coding. Right now that means agentic engineering. My passion is crafting user experiences.

02

Experience overview

Most of my bandwidth now goes to agentic engineering, built to a production standard. TeacherHub is the clearest proof: a language-learning platform whose homework-generation pipeline runs under a CEFR-aligned LLM-as-judge eval suite I built, so shipping an AI feature meant measuring whether it actually holds up. That sits on seven years of production engineering: three years at Redington leading a five-person frontend team on a multi-tenant fintech platform, then four years at OpenSC owning the supply chain analytics dashboard end to end for customers like Nespresso and Austral Fisheries. React/TypeScript on the frontend; Python, Node, C#, Kotlin on the backend.

03

Experience

Senior Full Stack DeveloperOpenSC

Jul 2022 – Apr 2026

Sustainability impact venture co-founded by WWF and BCG, providing supply chain traceability for global brands. Standardised messy 'first three miles' farm data into EPCIS, then surfaced it through dashboards used by Nespresso, Austral Fisheries, and internal teams to validate ethical sourcing claims and farmer payments.

  • Sole engineer on the main analytics dashboard. Built and maintained the whole thing. Plotly Dash for the analytical core, React and Next.js for the consumer-facing pages.
  • Built the traceability and payments validation system used by Nespresso to verify coffee sourcing across Rainforest Alliance and their internal AAA premium-farmer program, including checks that base prices tracked the London robusta price index and that farmer payments matched contracted standards.
  • Modelled supply-chain relationships so infiltration, exfiltration, capacity breaches, and untraced origin coffee became queryable patterns rather than per-supply-chain spot checks.
  • Worked with Austral Fisheries to validate the legal provenance of toothfish and prawn catches.
  • Replaced bespoke per-cluster orchestrations in Dagster with a YAML-configured, data-contract-driven ingestion layer. New supply chains can be added by config now.
  • Built a data entry flow that made it hard to put bad data in: input checks, guardrails, and reviews at the point of capture. Plus monitoring for ingestion accuracy and frequency across all supply chain feeds.
Stack /React, Next.js, TypeScript, Python, Plotly Dash, Dagster, Kuzu, Kotlin, AWS, Kubernetes, Postgres, Ethereum, Airflow

Associate Full Stack DeveloperRedington

Feb 2019 – Jun 2022

UK pensions consultancy. Core contributor on the frontend of a multi-tenant research platform used by several thousand consultants across 7 tenants to track investments and maintain observability across portfolios. Joined as a junior; promoted to leading a frontend team within two years as the company scaled from 10 engineers to 8 teams.

  • Key contributor through my junior years, then led frontend architectural decisions on a React and TypeScript multi-tenant dashboard. Sensitive financial data; tenant isolation was the design constraint everything else worked around.
  • Led a five-person frontend team focused on feature delivery, consistently the highest-performing team on UI work.
  • Introduced Cypress E2E testing across the platform, which raised deployment confidence and cut human error at release time.
  • Chaired the Bristol charity committee. Helped a charity left dry by multiple high-cost agencies. We ran a one-day workshop to surface issues, then migrated their database and supporting infrastructure onto Airtable. Pushed for more company-sponsored charity days and helped colleagues find their own.
Stack /React, TypeScript, MUI, Cypress, Jest, AWS, .NET (C#), PostgreSQL, DDD, Event sourcing paradigm
04

Education

BA Philosophy 2:1Leeds University

Sep 2014Jun 2017
  • Specialised in Philosophy of Technology
  • Rhetoric and structured argument: built the habit of restating a question before answering it
  • The skills I learnt at university shaped how I approach design conversations, whether UX or technical. Getting the most out of each person is what makes those conversations succeed
05

Skills

Primary stack

ReactNext.jsTypeScriptNode.jsPythonPostgreSQLAWS

AI / LLM (currently focused)

  • Eval testing
  • LLM pipelines across OpenAI and Anthropic APIs (GPT-4, Whisper, Claude)
  • Agent orchestration
  • Agentic harness
  • Skills, agents, hooks and strategy for agentic engineering
  • MCP servers with OAuth 2.1
  • OWASP LLM Top 10
  • Prompt injection and jailbreak patterns

Frontend

ReactNext.jsTypeScriptCypressJestMUIChakraTailwindCSSAnt DesignMantineReduxReact QueryReact Hook FormKotlin (Android)

Backend

Python (FastAPI, Dagster, pandas, Plotly Dash)Node.jsC# / .NETKotlin (Spring Boot)PostgreSQLMartenDBKuzu (graph DB)Airflow

Infrastructure & DevOps

AWS (S3, EKS, EC2, SNS, SQS, Lambda, IAM, RDS, CloudWatch)TerraformAzure (some)VercelSupabaseGitHub ActionsOctopus Deploy / TeamCityCircleCI

Leadership

  • Led a five-person frontend team at Redington
  • Completed external senior IC / principal-engineer soft-skills training (2024)
  • Ran external consulting engagement (LifeCycle) end-to-end
06

Projects

07

Outside work

  • Food and cooking
  • Travelling
  • Reading
  • Chess
  • Running
JD-01

Score this CV against a job

Paste a JD. The chips below highlight which requirements I’d land cleanly, where I’d stretch, and where I’d be honest about a gap. Click a Hit chip to jump to the cited bullet up-page in the CV. The slider tunes the matching threshold; if you’re reading conservatively, drag it left.

Sample JDs /
↳ pasted JDs are sent to a server route to score against the CV; not stored, not shared, not logged1,773 / 10,000
StrictbalancedGenerous

Reading the JD as written, this CV lands 7 hits, 4 stretches, and 1 honest gap.

Conservative matching: when uncertain, defaults to stretch over hit.

Tone manifesto6 pledges

Voice & values

Six positions on how I work. These are commitments — what I aim for, not what I always pull off.

TN-01

Manifesto

6 pledges
01 / 06

Culture is king

Inclusive teams produce better work than uniform ones. The ideas a monoculture misses only show up in rooms where it's safe to disagree. A leader's job is building that room.

02 / 06

Framing is first

I push on definitions before estimates. Most of the engineering disasters I've watched were technically clean — written well, shipped on time — and answering the wrong question. A week spent on the framing is usually worth a quarter of misdirected building.

03 / 06

Documentation and clear decisions

I keep an ADR log on every project of meaningful size. This site has thirty-one so far, including the ones that document deviations and reversals. The point is being able to argue with a past decision when context shifts. Retros are the same habit at session-scale: write down what surprised me, see what comes up more than once.

04 / 06

Right-aligned development

Before picking up new work, I scan the board right-to-left. Looking for: someone who needs a review, someone stuck on something I have context on, someone working in an area I'm about to touch. Usually one of those is a cheaper unblock than starting on my own next thing. I've been calling it right-aligned development.

05 / 06

Honesty over polish

I'd rather a CV bullet or an ADR read truthfully than impressively. The JD matcher on this site is tuned to flag my own gaps as honest gaps rather than stretch them into matches. The ADR log includes one where I had to darken a cream against the original design system to clear WCAG AA — uncomfortable to admit, worth admitting.

06 / 06

No absolutism in technological choices

My default criteria for tech choices: SOLID, maintainability, and agentic readiness — tools and structures an LLM can reason about. I'll break any of them deliberately when the product needs a different balance, provided I write down why. ADR-0001 picks Next.js over the design's recommended Astro. ADR-0007 darkens a cream to clear WCAG AA, against the design system as written.

Oliver Kaikane Gate — Valencia, May 2026

LabUpdated weekly

Things I'm building with LLMs

A working space. One live demo at the top, the side projects below. None of it is finished.

Featured / 01Personal Claude Code Setup

Session retrospective generator

Paste a Claude Code transcript and the demo synthesises a retro: what went well, what slowed things down, learnings catalogue entries, and suggested skills to add. The same format my real retros take after every working session.

Live demo
Sample sessions /
1,025 chars · sample = Refactoring auth flow
Pick a sample, edit if you like, then run a retro to see the output.
02

Side projects

linkouts, not demos