I’m a software engineering manager and backend specialist. Most of my work sits
where financial systems meet hard technical constraints - high volumes, strict
regulation, and data that has to be right the first time.
Financial crime & compliance
AML, sanctions and PEP screening, KYC, and transaction monitoring. Systems that
have to satisfy regulators as well as engineers, where a false negative is a
legal problem and a false positive is an operational one. Working familiarity
with fraud detection.
Payments & transaction processing
Payment systems, card payments, wallets, invoicing and BNPL. Real-time flows
handling millions of transactions a day, where staying correct under load is
the whole requirement.
Credit, collections & decision support
Credit scoring, loan management, debt collection, and budgeting and forecasting
tools. Decision support systems where the output drives a financial decision,
so the reasoning has to be explainable as well as correct.
Backend & distributed architecture
APIs and data-intensive services in C# and .NET, on SQL Server, with Kafka,
RabbitMQ and Redis where the shape of the problem calls for them. Transaction
processing at volume, designed to stay correct under load.
Cloud & delivery
Azure and AWS, containerised with Docker and Kubernetes, deployed through
CI/CD pipelines. Infrastructure that a team can actually operate, rather than
a diagram that only works on the day it was drawn.
Legacy modernization
Taking systems that still earn their keep but have stopped being safe to change,
and getting them moving again - incrementally, in production, without a
rewrite that never lands.
Engineering leadership
Leading teams, running 1:1s, performance reviews and hiring, owning delivery
planning, and sitting on architecture committees. Technical direction across
teams, not just within one.