Capabilities
Six domains, one boundary problem.
Most of what goes wrong sits between systems, not inside them. These are the six places I work, and what I actually do in each — written plainly, so you can tell quickly whether I'm the right person.
Systems architecture & integration
Contracts between systems, written before the code.
- Interface and data contracts, versioned and reviewable
- Event and message design — ordering, replay, idempotency
- Migration plans that run alongside the system they replace
- Architecture decision records the next architect can read
Typical engagement: discovery sprint, then a fixed-scope build.
Cloud & infrastructure
Environments that are reproducible, not remembered.
- Infrastructure as code, from nothing to running in one command
- CI/CD with rollback that has actually been tested
- Cost and capacity modelling before the invoice teaches you
- Secrets, identity and network boundaries that pass review
Typical engagement: fixed-scope build or fractional architect.
IoT & edge systems
Getting data off devices and onto a screen someone acts on.
- MQTT broker and topic design — QoS, retained state, access control
- Edge processing, buffering, store-and-forward when the link drops
- Bridging older devices and protocols onto MQTT without replacing them
- Telemetry dashboards — live data, history and alerts
Automation & RPA
Removing the manual step without hiding it.
- Process mapping first — most steps should die, not scale
- Attended and unattended automation with an audit trail
- Exception handling that escalates to a human on purpose
- Handover so the team owns it, not the consultant
Data pipelines & observability
Knowing a system is healthy before a client tells you.
- Ingestion, transformation and quality gates with lineage
- Metrics, traces and logs on one clock
- SLOs and alerts that wake someone only when it matters
- Dashboards for the people who run it, not the people who bought it
Business analysis & requirements
Turning what people say into what gets built.
- Stakeholder interviews and workshops that reach a decision
- Requirements traceable from need to test case
- Scope written so both sides can tell when it is done
- Vendor selection and RFP support with a scoring model
Next step