About
Twelve years onrecruitment desks.Engineer since 2019.
I spent twelve years as a recruiter building engineering teams for global businesses, in a 360 role across contract and perm. I started a company, sold it, and went through General Assembly in 2019 to write code full-time.
Now I’m a senior frontend engineer at a venture-backed startup, and I run aspinall.ai: AI consultancy, automation and product builds from someone who has lived the admin he now automates.
What I do
Four services. One engineer on all of them.
AI that takes a step out of the work, wired into the systems you already run. Not a chatbot in a blazer.
Experience
Where the time went.
The engineering years, newest first. The recruitment years are the reason the automation work is any good.
- PresentEngineering
disi digital.
Developing full-stack applications and SEO-tuned marketing sites for international clients.
Next.js · TypeScript · Tailwind CSS · PostgreSQL · Vercel
- PresentEngineering
A venture-backed EdTech startup
Working on a virtual work-experience platform used by students globally. Frontend & full-stack with TypeScript, Next.js, Tailwind and tRPC.
TypeScript · Next.js · Tailwind CSS · tRPC · Prisma
- 2022 - 2023Engineering
An Australian HealthTech startup
Built healthtech web applications in TypeScript with Next.js, interfacing with the backend through GraphQL.
TypeScript · Next.js · GraphQL · Apollo · Styled Components
- 2022 - 2022Engineering
An enterprise CMS platform
Frontend engineering on an enterprise content-management platform using React, Redux and GraphQL.
React · Redux · GraphQL · Jest · Webpack
- 2019 - 2022Engineering
An AgTech commodity-management platform
Cloud-based commodity-management platform for web & mobile using React and React Native.
React · React Native · TypeScript · Node.js · AWS
- 2019 - 2019Education
General Assembly
Full-time Web Development Immersive course. The career switch from recruitment into engineering.
JavaScript · React · Node.js · MongoDB · Express
How I work
Four rules I hold the work to.
- 01
Show the system, not the deck.
Every claim on this site points at something running in production. If I can't show it working, it doesn't go on the page.
- 02
Say less, measure more.
I'd rather report hours saved per consultant than describe the model. The number goes in the handover, not the pitch.
- 03
Specifics beat names.
I don't name clients. You get the integration, the edge case and the rate maths instead, which is more useful anyway.
- 04
Performance is part of the job.
A slow site from an engineer is a bad sign. This one is static where it can be and light where it can't.
Next
Tell me what’s slow. I’ll tell you if it’s worth fixing.
A plan, a build, or a straight “you don’t need this.”