I like figuring out how the pieces fit together.

My background sits somewhere between software engineering, automation, AI, operations, data, infrastructure, and product thinking.

I enjoy problems where the answer isn't simply "install another tool."

Sometimes the answer is an automation.
Sometimes it's an API.
Sometimes it's an AI agent.
Sometimes it's an internal application.
And sometimes the process needs to be simplified before writing a single line of code.

That's the kind of work I enjoy.

What working with me is like

It starts with an email: Not a sales call. Tell me what's happening in plain language; you don't need to know what the solution is.
Remote, and fine with time zones: I work with teams in Australia, New Zealand, Canada, the UK, Europe and the US, so a lot of it happens in writing.
Sometimes the answer is less software: If the process needs simplifying before anyone writes code, I'll say so.
You can see what it's doing: Logging, alerts and monitoring are part of the build, so a broken step is noticed in minutes, not days.

Experience across the layers, which is why the technology follows the problem.

Bachelor of Science in Applied Physics

University of San Carlos, Cum Laude

Thesis work: development and implementation of an underwater recorder system and a sound-analysis tool involving machine learning.

Six steps, in order, every time. The last one loops back to the first.

01
Understand
Understand how the process actually works, from the people who do it.
02
Simplify
Remove unnecessary complexity before building anything.
03
Design
Determine which parts belong in automation, software, APIs, AI, databases, and infrastructure.
04
Build
Use the right technology for each part, not one platform for all of them.
05
Observe
Add analytics, logging, and monitoring so you know it's working.
06
Improve
Iterate as the business changes.