About Me
Full-Stack Developer based in Manchester, UK
Full-Stack Developer
I'm a Full-Stack Developer currently working at RNID, where I build and contribute to digital products serving people across the UK — including public-sector web applications, accessibility-focused platforms, and internal development tooling.
My work spans frontend architecture with React and Next.js, backend integration, cloud infrastructure on Azure, and accessibility-focused development to WCAG 2.2 standards. I care about building systems that are reliable, maintainable, and genuinely useful for real users.
Outside of RNID, I've built and shipped my own products, worked across agency environments on client websites, and maintained a strong interest in developer experience, clean architecture, and practical product thinking.
Current Role
Full Stack Developer
RNID — Remote
Application Development & Infrastructure
- Built and maintained Docker-based local development pipelines with automated Azure Blob Storage syncing across multiple sites
- Contributed to Hearing Check V3 — working on resilience, architecture decisions, and secure handling of sensitive medical data
- Built the RNID Insights Library — a research platform with advanced filtering, Storybook component library, and custom WordPress build
Accessibility & Performance
- Contributed to accessibility improvements and WCAG 2.2 compliance work across RNID's website
- Worked on performance improvements and codebase modernisation on a high-traffic website serving over 1 million monthly visitors
- Contributed to load testing workflows using Azure Load Testing and JMeter
Skills & Technologies
Tools and practices I use day to day, from frontend through to infrastructure.
Frontend Development
Backend & Cloud
DevOps & Tooling
Core Competencies
How I Work
I move fast and iterate. I care about building things that actually work for real users, not just things that look good in demos.
Accessibility is built in from the start. Working in public-sector and healthcare-adjacent environments has shaped a genuine commitment to inclusive, reliable software.
I think in terms of maintainability as much as features. Writing code that the next developer can understand and build on is as important as shipping the feature itself.
I am comfortable owning implementation details across the stack — from component design through to infrastructure and deployment workflows.