Growth Engineer

About The Role If you'd rather build the system that runs growth than run growth campaigns by hand, keep reading. We are looking for an engineer who wants to sit inside a marketing team and build the infrastructure that lets a small group move at the speed of a much bigger one. You will design and ship the tooling, automation, and AI agent workflows that power acquisition, content, and experimentation across Tiugo's brands. This is a build role reporting into Growth Marketing, on a team that owns pipeline and ACV as its scoreboard. You are the technical counterpart to that mandate: the person who turns "we should be able to do this in days, not quarters" into something that is actually true. About Tiugo Tiugo is the company behind CKEditor, TinyMCE, and Uploadcare, developer tools that power rich content creation inside thousands of applications worldwide. Our editors carry decades of hard-won trust with developers, and that trust is our moat. We are at an inflection point. We are embedding AI deep into how content gets created, governed, and scaled, and we are moving up-market into the enterprise without letting go of the developer base everything is built on. We run a self-serve / product-led motion and a sales-assisted enterprise motion side by side. The Opportunity in Front of You Growth Marketing at Tiugo is being built from the ground up: one team, one number, spanning PLG, campaigns, and BDR across all of our brands. Part of standing that up is building the engineering layer underneath it, and that part needs a lot of work. You would be the first dedicated engineer on the team, working directly with the Head of Growth Marketing to decide what gets built, in what order, and how. Greenfield scope. There is no legacy growth stack to untangle. You get to choose the tools, the architecture, and the standards. A real system, not a request queue. This is not a role where marketing files tickets and you build what's asked. You are a co-owner of how the funnel works, from instrumentation to agentic execution. What You Will Build An AI-Native Growth Infrastructure The team's mandate is to design growth assuming AI is everywhere: in how buyers discover us, in how we create and test at volume, and in how the team itself operates. Your job is to build the plumbing that makes that real. Answer-engine visibility: Build and maintain the tooling that tracks how Tiugo shows up when developers and buyers research through ChatGPT, Claude, Perplexity, and AI-powered search, and feed that signal back into content and campaign decisions. Agentic workflows: Design and ship AI agents and automations that handle research, drafting, QA, and reporting work that used to take a person days, so idea-to-live-asset happens in days, not quarters. Experimentation systems: Build the infrastructure for the team to launch, track, and read out tests fast, without every experiment needing a one-off build. Learning loop: How does what Product and Sales are learning about AI get absorbed into sales conversations fast? Product is iterating weekly. Customers are asking questions AEs have not been asked before. If the sales team is six months behind the product, we lose deals we should win. You own turning information into insights and learnings. Who You Are You have built marketing or growth engineering systems before: automation, instrumentation, experimentation infrastructure, or AI agent tooling, ideally inside a B2B software or developer tools company. You are genuinely fluent in AI tooling and agentic workflows, not just aware of them. You can talk specifically about agents or automations you've built, what broke, and what you'd do differently. You are comfortable owning ambiguous, undefined scope. Nobody will hand you a finished spec; you help write it. You think in systems: how data flows between tools, where the manual steps are, and how to remove them without losing accuracy. You want to be measured by whether the funnel got faster and cleaner, not by how much code you shipped. Why This Might Be Your Dream Job Scope: First dedicated engineer on Growth Marketing, with real say in the architecture and tooling from day one. Leverage: Real products, real revenue, and a portfolio of developer-trusted brands. You are building infrastructure for growth that already has proof it works, not manufacturing demand from nothing. Timing: You arrive as the team and the operating model are being built. Your early decisions will shape how growth engineering works here long after this first year.