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
Contract engineering · 1, 3 or 6 months
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
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.
Marks are shown where a licensed file exists; everything else is named in plain type. Names identify technologies, not partnerships.
Career
Every role on the way up is one I can still do for you. Startups and well-established SMEs, newest first.
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.
feat(director): more output from the same budget
Teams, process and tooling shaped so the money you spend shows up as shipped work.
feat(tech-lead): architecture decided, written down, reviewed
Code review, technical direction and unblocking, so the team never waits on one person.
feat(delivery): goals met, sprint after sprint
Plans you can rely on, honest status and a rhythm stakeholders can follow.
init: learn the craft by shipping it
Still hands-on: I write production code in every engagement.
Engagements
Pick the length; we agree scope, cadence and outcomes in writing before the start date. Full-time or part-time, remote-first.
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
I teach what I know and learn your business as fast as I can. Education runs both ways, and so does accountability.
Written updates every day, calls when they save time. You always know what moved and what is blocked.
Short decision records: the options, the trade-offs, what we chose and when to revisit it.
Every change reviewed, with the reason in the comment. Your team learns the codebase; I learn your domain.
Tests and CI on the paths that make or lose money first, so a release stops being an event.
Docs, runbooks and pairing as we go, so the last day of the contract is a quiet one.
AI engineering
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.
Retrieval (RAG) over your documents and data, with sources shown and gaps admitted.
Triage, drafting, data entry and follow-ups, with a person approving anything that sends, spends or deletes.
Assistants that speak and listen, and extraction from PDFs and forms straight into your systems.
AI coding assistants used well: faster delivery, reviewed like any other code, and your team taught to do the same.
all checks passed · ready for review
Before we start
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.
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.
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.
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.
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.
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.
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
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.