A note for clients

Please check messages claiming to be from me

Someone is using a different email address to impersonate me and contact clients about supposed website updates and payments. Those messages are not from me.

Genuine emails from me only come from hello@derrick.dk. If you receive a request from another address, please do not act on it or make a payment. Contact me directly through this website to check first.

Contact me to verify

What I mean by “marketing engineer”

The work I do between product marketing and engineering: building the page or flow, connecting the systems and checking what happens.

7 min read By Derrick Kityo
A rendered funnel and blue gear on lime green, labelled Marketing engineering, WHAT I ACTUALLY DO

When I say “marketing engineer”, I mean the work I do between product marketing and engineering. That might involve shaping the message, building the page or product experience, connecting the systems and measuring what happens next.

The point is to reduce the handovers that slow an idea down before it reaches customers. I'm not taking the place of a product marketer, designer or software engineer.

Understand

The audience, product, search demand and job the page needs to do.

Ship

The website, app journey, integration or experiment that customers can actually use.

Learn

The events, feedback and business results that help decide the next release.

The work starts before the build

A request like “we need a new landing page” sounds straightforward until you start asking who it's for and what brought them there. What do they need to understand? Which action matters, and what needs to happen in the CRM afterwards?

Product marketing does much of that thinking, while engineering makes the experience work reliably. I help turn the thinking into a page, app flow or system without losing the reason for it. Sometimes that's a customer-facing page; sometimes it's an internal tool that removes the manual handoffs behind it.

What the work produces

Problem Output What makes it useful
A product is hard to understand Positioning, page structure and working website The message and the interface are tested as one experience
Leads disappear after a form Form, CRM mapping, routing and booking flow Ownership and failure states are part of the build
Teams cannot see where conversion drops A small event model and funnel Events describe customer progress, not every possible click
Search content brings traffic but no customers Intent review, original asset and service path The page answers the query and helps the right reader continue
Marketing requests wait in an engineering queue A scoped web backlog and small releases Routine work moves without hiding technical risk

The tools I use

The tools change with the job. For marketing sites, I use Webflow, Astro or Framer; for app experiences, tools such as Expo. Figma and Relume help shape the interface, while Vercel and Cloudflare handle delivery and edge work. I use PostHog to measure the journeys, and HubSpot, Chili Piper and Resend for enquiries, booking and communication.

Slack and ClickUp keep the work visible. Codex, Claude, Grok and MCP servers can help with research, implementation and repeated tasks, but I still need to review the output. Someone has to judge it and own the result.

A realistic week

  • Review search, product and conversion evidence before changing a page.
  • Turn a launch brief into messages, components and a release plan.
  • Build the page or flow and connect forms, CRM and analytics.
  • Check mobile behaviour, accessibility, metadata and failure states.
  • Release the work, verify events and document what changed.
  • Use the result to reorder the backlog rather than defend the original idea.

Where the role stops

I'd want the role to have a clear boundary. Deep brand strategy, large application architecture, paid media and specialist data engineering still need the right people. The work I'm describing is customer-facing web work that needs both business and technical understanding.

When this role helps

It can help when marketing and engineering are both capable, but work keeps falling between them. There are pages to build, a product journey to explain and tools that need to pass reliable information between them. Bringing in another specialist supplier can add a handover. One owner across that work can often move it faster.

Frequently asked questions

What does a marketing engineer do?

A marketing engineer turns a marketing goal into website, app, data or automation changes that work. That means understanding the journey, building the connections and checking you can measure the result.

How is marketing engineering different from campaign management?

Campaign management plans and runs marketing activity. Marketing engineering builds and improves the systems behind it: lead handoffs, experiments, content workflows and reliable conversion tracking.

What should a marketing engineering project deliver?

Agree what will work, who owns it and how you'll check it. That might be a tracked journey, a tested integration, a runbook or a small tool that removes a specific blockage in the workflow.

Turn the useful parts into shipped work.

Tell me what you are trying to improve and where it is getting stuck. I can help with the website, app, measurement and systems around it.

I build websites and apps

I work across product marketing and engineering, turning ideas into useful digital products and improving how they perform after launch.

Webflow developerWebflow LondonWebflow product workshop