I reverse-engineer, modernize and operate complex SFMC environments — connecting marketing automation, data architecture, platform migration and production reliability.
Sanitized case studies focused on technical ownership and scope, without exposing client identities.
Inherited a live, undocumented SFMC environment with no formal handover and rebuilt its technical map while keeping Always-On operations running. Current migration scope: ~200 Data Extensions, 30+ automations, 20 CloudPages, ~10 journeys and ~2M customer records.
Automated platform inventory covering Data Extensions, fields, folders, automations, full SQL, imports, exports, CloudPages, Content Builder metadata, send/test relationships and business rules — removing roughly 90% of manual discovery work.
Implemented a pragmatic customer consolidation model inside SFMC for one brand, now evolving toward multi-brand identity, permissions, engagement and governance.
A local-first engineering operating system for the stack I use: public knowledge graph, SQL/Data Views, deployment and incident tooling, executable recipes, private environment snapshots, drift detection and bounded AI context packs.
The knowledge base grows with real responsibility. Every item is labeled as Production, Project, Lab or Study so learning is never presented as experience.
Platform engineering, data views, journeys, automations, personalization, messaging and migration.
PRODUCTIONSQL patterns, modeling, identity, quality, deduplication and analytical data flows.
PROJECTAPIs, webhooks, orchestration, n8n patterns and integration reliability.
PROJECTLinux, Docker, networking, reverse proxies, Git and operational reliability.
STUDYSecrets, authentication, application hardening and secure integration patterns.
STUDYPython, analytics, LLM engineering and future data science notes.
The form can route into my n8n workflow. Until the webhook is configured, it falls back to direct contact instead of pretending the message was sent.