Empowering Teams to Innovate - Without the Traditional Dev Bottlenecks

Founder and Director

David Foreman

David has been writing code since he was fourteen and running businesses for most of his adult life. Operations is the thread through it: he has run businesses where friction costs you money the same day it happens, and built the systems that took it out. He is also the other half of the design conversation at NCS, with strong views on how a tool should feel to the person using it every day. He founded NCS to close the gap between the people who understand the business and the people who build the tools, and he is the firmest voice here on how AI-native delivery has to be done: checks on everything, and a named person accountable for what ships.

Principal Engineer

Devonte Emokpae

Devonte has been writing code since about the time he could type, and it shows: he has strong opinions about how a thing should be built and the track record to back them. He has spent over a decade leading engineering teams while still shipping code himself, which is rarer than it sounds and the reason he can size a piece of work realistically rather than optimistically. He is the person who decides whether an architecture will still be maintainable in two years, and who sets the standard everyone else builds to. He still writes code every week.

Senior Engineer

Gareth Daine

Gareth has thirty years of production systems behind him, which means he has already seen the failure mode you are about to hit. He has worked through enterprise systems, regulated environments, SaaS and gaming, and, unusually for that much experience, he never stopped moving with the field. He now works at the front of it, on AI agent orchestration and language-model integration, with three decades of hard-won infrastructure judgement underneath. Give him an inherited codebase nobody wants to touch and he will get it into a state where it can finally be tested, deployed and trusted.

Associate Engineer

George Allan

George reasons from first principles and leaves no stone unturned. He came into software from engineering geology, learning to build because he needed a tool that did not exist, and he has never lost the habit of solving the actual problem rather than the one he was handed. Give him something nobody has fully understood yet and he will take it apart until he does. He works across React, Node.js, PostgreSQL, language-model integrations and computer vision, and has built interactive 3D visualisation for people who need to see a thing before they can decide about it. He holds a BSc (Hons) in Geology from the University of Southampton.

Senior Engineer

Abiola Fatunla

Abiola builds enterprise AI systems and the applications on top of them: multi-agent architectures, autonomous delivery, and the verification that decides whether AI-written code is fit to put in front of real users. His background is cyber security, which mostly shows as a habit. He assumes a system will be attacked and designs on that assumption, which is a useful thing to have in the room when there is a language model inside the product. He has worked on partnerships with OWASP and the UK Cyber Security Council, and holds AWS, Terraform, CompTIA Security+ and CSCP certifications.

Senior Engineer

Olumide Akinremi

Olumide has taken products from nothing to live at startups, scale-ups and unicorns, and knows which decisions are cheap to change and which are expensive to reverse. He builds systems that have to survive real load, and he carries a feature the whole way from the cloud to the front end. Give him a product that has outgrown the way it was built and he will find the seams before they become the outage. Much of his recent work is AI-powered features, where the hard part is deciding what the model can be trusted to do. He is endorsed as a UK Global Talent, a recognition you cannot self-award.

Senior Engineer

Dan Tinsley

Dan builds the part clients touch, and it's why it looks the way it does. He designs interfaces properly: considered, finished, accessible by default rather than by retrofit. He also holds the quality line for what ships, his own work included. That second part is the harder skill in AI-native delivery: he directs AI coding agents through implementation and interrogates what they produce, which is how work ships fast without quietly degrading. Twelve years in, he knows where speed is free and where it gets paid for later.

Automation Engineer

Archie Nash

Archie keeps every repository we run to the same standard. He stays on top of the dependencies across all of them, lets the safe updates through once every check has passed, and pulls out the ones that need a decision: a major version jump, or a security fix that has just landed. He keeps the shared setup in step too, so a change to how we work reaches every project rather than the one somebody remembered. The quieter half of the job is documentation that has drifted from what shipped, and duplicated code nobody meant to write twice.