About

I’m a Python engineer in Hull. Six years building Django and Django REST Framework applications, mostly internal systems that people rely on to do their jobs.

I work for a healthcare provider, where I own products from the first conversation about requirements through to supporting them in production. Most of what I build involves approval and escalation workflows, role-based access control, single sign-on, and integrations with third-party APIs.

Working in a regulated sector means access control and audit trails come first rather than last. You design the permission model before the feature, because it is much harder to add afterwards. And every action a user takes has to still be answerable months later, when someone asks who did what and when.

I led the migration of our codebases into a structured source-control organisation, and introduced the linting and documentation standards the team now works to, along with a Confluence knowledge base and a Jira board.

I started in technical support, and I wanted to be building the software rather than supporting it. So instead of asking, I wrote something in Python that solved a problem nobody had assigned me. It made the case better than a conversation would have, and I moved into the development team. The source-control migration, years later, started much the same way.

At work I use Azure — Entra ID, virtual machines, Data Factory, and function apps. I’m AWS certified, and AWS is where I build my own projects, with the infrastructure in Terraform.

Before this I spent four years in the Royal Navy, working on secure communications systems. The habit of treating access control and auditability as the first design question, rather than the last, started there.

What I’d like next is a similar problem with more room in it: backend work where correctness and access control matter, on a team I can learn from. If that sounds like yours, get in touch.