Jamie.
Full-stack engineer · UI focused
I build sharp web products that ship.
I'm Jamie - a software engineer who turns messy problems into clean systems and crisp interfaces. Fast iteration, strong UX, and details that hold up in production.
About
I'm a pragmatic full-stack engineer focused on turning messy, real-world constraints into clean systems and crisp interfaces. I care about fast feedback loops, maintainable code, and UI details that hold up in production.
Code and experiments live on GitHub.
How I build
- Feedback loops
I prefer small, production-shaped slices - measurable changes that can be rolled back cleanly.
- Maintainable systems
I keep the core boring: clear boundaries, predictable data flow, and fewer “clever” moving parts.
- Interface craft
I bias toward hierarchy and restraint: readable type, clear spacing, and interactions that don't shout.
- Reliability
I lean on guardrails over heroics: linting, targeted tests, and failure states that degrade gracefully.
Education
MSc in Software Engineering with a focus on AI and data-driven systems. My capstone applied ML and NLP to real-world text - sentiment and signals in clinical-adjacent data - so I could go deep on evaluation, ethics, and what the model was actually learning.
Master's project on AI-based sentiment analysis on textual data, with attention to mental-health-related signals and responsible interpretation.
First-class honours in Software Engineering. I cared most about systems thinking and shipping a final-year project that could justify its own complexity - computer vision for train autonomy and safety monitoring - which earned the top mark in the cohort.
Highest grade for Final Year Project: a computer vision system for train autonomy and safety monitoring.
Skills
I work in consultancy, so I ramp on client stacks and ship in their codebases - most of my day-to-day depth is in Laravel and Entity Framework, but I still reach for the rest of this list wherever an engagement needs it. The first panel is the technical stack - languages, frameworks, and tools from real projects - grouped by how often each one shows up (daily, regular, or occasional) so this reads as an honest snapshot, not a keyword list. A separate panel covers how I work with teammates and code: engineering habits and leadership. Anything I'm still mostly experimenting with is under Learning.
What I build with
Daily
- .NET
- Bootstrap
- C#
- CSS
- Docker
- Entity Framework
- Git
- HTML
- Jest
- Laravel
- MS SQL
- MySQL
- PHP
- React
- TypeScript
- XUnit
Regular
- AL (Business Central)
- CI/CD
- Digital Ocean
- Git Hooks
Occasional
- Adobe Illustrator
- AWS
- Figma
- PostgreSQL
- Ruby
- Ruby on Rails
- Tailwind
- Terraform
- WordPress
Practice & Leadership
Daily
- Code Reviews
- Leading & Supporting Engineers
- Mentoring & Onboarding
- Refactoring
- Systems Migration
Regular
- Accessibility (WCAG/ARIA)
- Agile / Scrum Delivery
- API Design
- Backlog, Tickets & Scoping
- Incident Leadership
- Stakeholder Alignment
Learning
- Azure
- Next.js
- React Native
Experience
Roles where I've shipped production features, tightened UX, and improved reliability. I gravitate toward work that pairs product judgment with solid engineering - not either one in isolation.
Software engineer at The Curve, a consultancy where I ship pragmatic solutions with clients and partners. I spend my time clarifying what actually needs building, owning features across the stack, and helping junior and offshore developers stay unblocked - without losing sight of quality, usability, or how work lands in production.
I partner with clients and external organisations on complex delivery - turning pain points into clear requirements and incremental releases.
I mentor junior and offshore teammates through pairing and reviews, and I keep handoffs explicit so scope doesn’t drift.
I own features end to end with a bias toward maintainable code, sensible UX, and releases that can be rolled back cleanly.
I bridge stakeholders and engineering: surfacing risks early and keeping expectations aligned with what we ship.
I help shape technical direction inside teams - approach, sequencing, and trade-offs that fit the business constraint.
I stay in refactors, code review, and continuous improvement alongside day-to-day feature work.
Freelance engagement where I owned technical direction and delivery for a bespoke mobile app for a small-business client. I translated day-to-day operations into a focused product, kept communication tight, and shipped on a timeline we could both trust.
Set technical direction and shipped end-to-end features for a startup-style mobile product.
Delivered bespoke web work for small businesses with clear boundaries and predictable milestones.
Ran requirements, client communication, and sequencing so releases stayed manageable.
Web developer with the Health Informatics Service, supporting Calderdale & Huddersfield NHS Foundation Trust and partner organisations. I replaced fragile paper and legacy surfaces with dependable web tools - always with an eye on what clinical and operational staff need at the point of use.
Designed and delivered a return-to-work system that replaced a paper accident-and-absence process; it became the Trust’s default channel for reporting.
Built and evolved the CHFT Patient Leaflet Repository so consultants can find accurate, governed leaflets in one place.
Led the overhaul of an end-of-life training system for an external partner, from discovery through cutover.
Other Roles
Volunteered as media and merchandise secretary - keeping social channels cohesive, working with brand partners on kit and promo, and making sure what we published actually looked like the same club.
Maintained a consistent visual identity across social channels.
Collaborated with sponsors on squad uniforms, club merchandise, and promotional drops.
Ran campaigns that lifted engagement and made the society easier to recognise on campus.
Before I moved into engineering full time, I led shifts in a high-volume pub: opening and closing, cash handling, and keeping service steady when the floor was full.
Led shifts and supported the team during busy service.
Accountable for opening and closing, cash procedures, and a consistent customer experience.
Projects
A short list of work I'm happy to stand behind - clear UX, maintainable systems, and delivery I owned end to end. Each card is a quick read on outcomes and the decisions that shaped them.
This portfolio
I reimagined my Laravel portfolio in Next.js - same intent, clearer architecture and craft, with an editorial design system and AI-assisted delivery kept under human direction, taste, and review.
I moved requirements, IA, and the front end together - not a reskin on old foundations.
Print/editorial brutalism lives in tokens and components so the look scales without one-offs.
Plan → build → test → refine, with guardrails so generated work stays shippable and maintainable.
Commercial WordPress site
I took a celebrant site from brief through Figma, custom WordPress theme, deployment, and handoff - responsive, production-ready, and owned end to end.
I turned the brief and constraints into IA and a visual system before writing theme code.
Responsive layouts and clear component boundaries - customisation only where it paid off.
Tight client loops through launch: predictable milestones, steady go-live, no last-minute surprises.
Patient Leaflet Repository
I helped build and evolve a Trust-wide platform to store, search, and maintain patient information leaflets. The hard part was a rebuild and migration: clearer architecture and a safer content lifecycle without losing day-to-day usability for clinicians or the public site.
I followed a migration path: inventory legacy content, normalise structure, and cut over with rollback in mind.
Single place for governed leaflets - upload, versioning, and discovery so departments stay aligned.
Dual audience: staff workflows for upkeep and a public-facing surface that stays readable and trustworthy.
Certifications
Formal credentials on the fundamentals - Azure services, cloud concepts, and the operational basics I lean on when shipping to real environments.
Foundational Azure: core services, pricing models, governance, and how the platform fits together - useful context when I design or deploy cloud-backed work.