The engineer who sits between marketing, product, and AI.

AI-accelerated, not AI-dependent

Prototype in days. Ship MVPs in weeks.

I prototype with AI tooling fast, agents, dashboards, internal apps, then harden the code so the team can actually own and extend it. Speed-to-learning beats speed-to-shipping. The point is to test a hypothesis before competitors finish writing the spec.

"Someone who already operates in the AI-native paradigm you're building toward."

Switching is the skill

Model loyalty is a trap.

Claude, GPT, Gemini, DeepSeek, each is best at something different and the answer changes every month. I track real costs (Helicone) and route through OpenRouter, so the right model lands on the right task without lock-in. The edge is knowing what's new and knowing what already works.

"An engineer who keeps your AI stack current without rewriting it every quarter."

Marketing-engineering hybrid

I speak both languages without translation.

Most engineers don't want to think about funnels. Most marketers can't ship an agent. I sit in the middle, building the tooling marketing/product teams actually use, in the actual stack they live in. HubSpot CMS, AEO schema, internal dashboards, n8n workflows, agent prototypes.

"A technical partner who reduces the friction between marketing, product, and engineering."

Enterprise-grade defaults

Code review, security, accessibility from day one.

Working inside Cognigy and Regiondo taught me what enterprise actually expects: strict code review, security-first thinking, WCAG compliance, documentation that survives team turnover. I build to those defaults whether the project is enterprise or not.

"Work that passes review on the first pass and doesn't break at 3 AM."

Build in public

Receipts beat claims.

I ship small AI apps on weekends and write about what broke. CIA, Apsolut Cortex, Prompt Stash, Brand Intelligence, City Scene Generator, Santa's Video Workshop. All linked, all real. LinkedIn essays on memory hygiene, prompting as core skill, vendor architecture corrections. The portfolio is the proof.

"A hire whose work you can already read and try before the first interview."

Ownership, not tickets

I own problems end-to-end.

If a build fails, I fix it. If a requirement is unclear, I ask. I write code future teammates can read, raise blockers before they become emergencies, and document what I built so the team can run it without me. Zero micromanagement required.

"Trust that scales, the hire who raises the bar without making noise about it."