← All services

Contract engineering · 1, 3 or 6 months

Contract full-stack developer, tech lead and AI engineer.

A freelance senior software engineer who has been a junior engineer, scrum master, tech lead, Director of Engineering and CTO. I join your team for one, three or six months, full-time or part-time, go deep on the hard parts and leave the team stronger than I found it.

whoami

Nick Taylor

Senior engineer · tech lead · AI engineer

Junior engineer → CTO, in startups and established SMEs

availability

1 · 3 · 6 months · remote-first · day rate on request

Full-time or part-time · RO · UK · EU · start date on request

The stack

The tools, in the file where engineers keep them.

Languages, frameworks and platforms I use in production, most-used first. Your goals and the systems you already run decide what I use; the list never does.

Choose an area of the stack

Languages

  • TypeScript
  • JavaScript
  • PHP
  • Python
  • C# (.NET)
  • Java
  • Rust
  • SQL

Frontend

  • React
  • Next.js
  • Vue
  • Nuxt
  • Angular
  • Svelte / SvelteKit
  • Astro
  • Remix
  • Tailwind CSS
  • GraphQL clients (Apollo Client)

Mobile

  • Capacitor
  • React Native
  • Expo
  • Ionic
  • Flutter
  • iOS
  • Android

Backend

  • Node.js
  • Express
  • NestJS
  • Fastify
  • Hono
  • Laravel
  • Symfony
  • Django
  • FastAPI
  • Flask
  • ASP.NET Core
  • Spring Boot
  • GraphQL (Apollo)
  • REST / OpenAPI
  • tRPC
  • WebSockets

Data

  • PostgreSQL
  • MySQL
  • Redis
  • MongoDB
  • DynamoDB
  • Firestore
  • Databricks
  • Prisma
  • Drizzle
  • TypeORM
  • Eloquent
  • Entity Framework

AI

  • OpenAI
  • Anthropic Claude
  • Google Gemini
  • LangChain
  • LlamaIndex
  • Vercel AI SDK
  • OpenAI and Anthropic SDKs
  • pgvector
  • Pinecone
  • ElevenLabs
  • Stack AI
  • RAG pipelines
  • Agents
  • Evaluation
  • Guardrails

Commerce

  • Magento 2
  • Shopify
  • WooCommerce
  • WordPress
  • Odoo

Payments

  • Stripe
  • Checkout.com
  • Adyen
  • PayPal / Braintree
  • Netopia
  • Klarna

Testing

  • Jest
  • Vitest
  • Playwright
  • Cypress
  • PHPUnit
  • pytest

Cloud & ops

  • Docker
  • Kubernetes
  • Terraform
  • Cloudflare
  • Google Cloud
  • AWS
  • Render
  • GitHub Actions
  • Turborepo

Tools

  • JetBrains WebStorm
  • VS Code
  • Terminal-first
  • AI coding assistants

Marks are shown where a licensed file exists; everything else is named in plain type. Names identify technologies, not partnerships.

Career

From the first commit to the boardroom.

Every role on the way up is one I can still do for you. Startups and well-established SMEs, newest first.

  1. CTO

    feat(cto): turn the vision into goals a team can meet

    Strategy, budget and build-or-buy calls, explained so the board and the engineers agree.

  2. Director of Engineering

    feat(director): more output from the same budget

    Teams, process and tooling shaped so the money you spend shows up as shipped work.

  3. Tech lead

    feat(tech-lead): architecture decided, written down, reviewed

    Code review, technical direction and unblocking, so the team never waits on one person.

  4. Scrum master

    feat(delivery): goals met, sprint after sprint

    Plans you can rely on, honest status and a rhythm stakeholders can follow.

  5. Junior engineer

    init: learn the craft by shipping it

    Still hands-on: I write production code in every engagement.

Engagements

Three shapes. One clear goal each.

Pick the length; we agree scope, cadence and outcomes in writing before the start date. Full-time or part-time, remote-first.

1 month

Scope
One clear goal: an audit, a rescue or a feature shipped
Cadence
Daily async notes, a weekly demo
Outcomes
  • A shipped release or a prioritised plan
  • Decisions written down
  • A handover your team can run with

3 months

Scope
A product slice or platform upgrade, end to end
Cadence
Weekly planning, a fortnightly review with stakeholders
Outcomes
  • Features live in production
  • Tests and CI the team trusts
  • Running costs cut where I find waste

6 months

Scope
Tech lead or interim head of engineering
Cadence
A weekly leadership sync, a monthly roadmap review
Outcomes
  • A team that delivers without me
  • Architecture and roadmap owned in-house
  • A clean handover to a permanent lead
Mode
full-time or part-time
Location
remote-first
Rate
on request

Day rate on requestIt depends on the length, full-time or part-time, and the role. You get it in writing with the scope, before anything is signed.

Need direction more than another pair of hands? Technical direction

How I work

Goals must be met. Vision is the mountain to climb.

I teach what I know and learn your business as fast as I can. Education runs both ways, and so does accountability.

  1. Async by default

    Written updates every day, calls when they save time. You always know what moved and what is blocked.

  2. Decisions written down

    Short decision records: the options, the trade-offs, what we chose and when to revisit it.

  3. Code review that teaches

    Every change reviewed, with the reason in the comment. Your team learns the codebase; I learn your domain.

  4. Tests before trust

    Tests and CI on the paths that make or lose money first, so a release stops being an event.

  5. Handover from day one

    Docs, runbooks and pairing as we go, so the last day of the contract is a quiet one.

AI engineering

AI that ships, measured before it goes live.

I use AI every day, in the product and in the way the team builds it. The discipline is what makes it safe to rely on.

What I ship with AI

  1. Assistants on your own knowledge

    Retrieval (RAG) over your documents and data, with sources shown and gaps admitted.

  2. Agents that do real work

    Triage, drafting, data entry and follow-ups, with a person approving anything that sends, spends or deletes.

  3. Voice and documents

    Assistants that speak and listen, and extraction from PDFs and forms straight into your systems.

  4. AI in the engineering workflow

    AI coding assistants used well: faster delivery, reviewed like any other code, and your team taught to do the same.

  • Answers cite your sources
  • Says “I don’t know” outside its scope
  • Personal data minimised or redacted before it reaches a model
  • Actions that send, spend or delete wait for a person
  • Cost per task inside the agreed budget
  • The same eval set runs before every release

all checks passed · ready for review

Before we start

What teams ask first.

What kinds of contract do you take on?

One, three or six months, full-time or part-time, as a hands-on full-stack engineer, a tech lead or an AI engineer. We agree the goal, the cadence and the outcomes in writing before the start date, and each engagement’s contract sets out its own terms.

Can you join our existing team and process?

Yes. I work inside your tools and rituals: your repository, tracker, chat, code review and release process. Having worked as a scrum master, tech lead, Director of Engineering and CTO, I can also run delivery, mentor and report to leadership while still shipping production code.

Do you work remotely with UK companies?

Yes. I work remote-first with companies in the UK, the EU and Romania, overlapping your working hours where it matters. On-site days can be arranged for a kick-off, workshops or the handover. I work online with teams across Romania, in Bucharest, Cluj, Iași or Timișoara, and in the UK.

How is a contract engagement priced?

In a written proposal, before anything is signed. The rate depends on the length, full-time or part-time, and the role: hands-on engineer, tech lead or AI engineer. I do not publish a day rate, because the scope decides it; you get the figure in writing with the scope.

How does this differ from the fractional CTO service?

Contract engineering puts me inside your team to deliver: writing code, leading a squad or shipping AI features for one to six months. The fractional CTO service is direction a few days a month: architecture, roadmap, hiring and technical decisions. Many companies start with one and later need the other.

Can you join as a contract AI engineer?

Yes. I build RAG pipelines, agents and voice or document workflows with OpenAI, Anthropic Claude and Google Gemini, with evaluation, guardrails and cost limits built in from the start.

What happens when the contract ends?

A handover: documented decisions, runbooks, a walkthrough with your team and a clean backlog. The aim is that your team runs it without me.

Contact

Tell me the goal. I’ll tell you if I’m the right engineer.

Share the goal, the team and the timeline. I reply with fit, availability and the day rate.

An enquiry starts a conversation. Nothing is agreed until the scope and rate are in writing.