About

I have spent 10+ years in banking and payments as a technical analyst. Most of that work has been on payments delivery: ISO 20022 and SWIFT messaging, payments API integration, and the migrations and testing that keep money moving correctly.

What sets the role apart is range. I do not just write requirements and hand them off. I analyze the problem, code enough to prove or build it, test it against real scenarios, and support it when it hits production. Business analyst, functional analyst, QA analyst, developer analyst, systems analyst: on a delivery team, that is one person wearing five hats.

I built Analyst Engineering because almost everything written for analysts is aimed at beginners. There is very little for the practitioner who is already on a delivery team and wants to get sharper at the work that actually ships: writing test cases for a pacs.008 migration, validating a Kafka event flow, reading production logs, tracing a payment across microservices.

So that is what this site is. No-fluff playbooks, written from real delivery work, for people who do the job. If that is you, the articles and guides here are built for you.