Engineer for the systems marketing runs on

How I work

Most of my work starts the same way: something already exists, it is important, and it is not behaving. A portal that grew past its data model. A dashboard the sales team stopped believing. An integration that drops records quietly enough that nobody notices for a week.

I like that work. It rewards reading code carefully before changing it, and it forces you to be honest about what you actually know versus what you assume. Before I propose an architecture I want to see the data, the traffic pattern and the failure log — the shape of the problem usually decides the design.

In practice that means I build in slices that ship. A migration that reaches production every two weeks with a fallback path beats a rewrite that lands in one terrifying evening. Integrations get idempotency, retries and a replay path before they get features, because the second call is the one that hurts. And anything a non-engineer has to operate — routing rules, field mappings, content — belongs in configuration, not in a deployment.

I have worked remotely for 6 years across agency, product and consulting teams. I write English fluently, document decisions as I go, and would rather ask an uncomfortable question in week one than discover the answer in week ten.