This is a role guide, not an installed employee. It explains what the role owns and how Tycoon runs it. Nothing is hired or activated until you choose it.
What your AI Growth Engineer does
Workflows on autopilot
Weekly experiment cycle
Reads the backlog Monday, picks the highest-expected-lift test, ships the build by Wednesday, instruments tracking Thursday, launches Friday, measures through the following week.
Landing page drop
Takes a new campaign brief from the AI CMO, ships a focused landing page in 24 hours, wires conversion events, and queues it for paid traffic.
Tracking audit
Monthly sweep: verifies every critical event fires, checks for duplicate tracking, confirms attribution chains aren't broken, rewrites flaky event names.
Funnel diagnostics
When a core metric drops, queries PostHog and Stripe to isolate which funnel step regressed, and reports the root cause in a single chart.
Experiment readout
Every Friday produces a 1-page readout: what shipped this week, what we learned, what's next. Sent to the Manager and founder in chat.
Without vs With a AI Growth Engineer
- Experiments get designed but never shipped because landing pages are a two-week backlog item
- Analytics are 'mostly working' and you don't trust the funnel numbers
- You run 1 test a quarter and each one is inconclusive
- You hire a $200K growth engineer and wait 3 months for them to understand the stack
- 'We should test that' dies in Slack
- New landing page every week, ready for paid or organic push
- Monthly audit keeps tracking tight; you actually make decisions from the data
- One test a week with pre-registered hypothesis and proper stats
- AI growth engineer reads your stack in a day and ships the first experiment in the first week
- Ideas hit the Linear backlog, get prioritized, and ship on cadence
A day in the life of your AI Growth Engineer
07:15Pulls overnight experiment data from PostHog. Checks for significance on the pricing-page test that launched last Friday.09:00Ships a new lead magnet landing page — form, Stripe checkout, event wiring. 3 hours from brief to live.12:30Debugs why Stripe subscription_created events stopped mapping to user_id in PostHog. Finds a missing identify() call, ships the fix.14:30Designs next week's onboarding CTA test: 2 variants, pre-registered hypothesis, 14-day measurement window, 8% MDE.16:00Reviews last week's experiment log. Writes a 1-page readout: 2 wins, 1 loss, 1 inconclusive. Sends to Manager.18:00Stands up a referral widget prototype using Zapier + a simple React component. Queues for a paid traffic smoke test tomorrow.22:30Runs nightly tracking audit. Finds 3 duplicate events from a recent deploy, flags them for morning cleanup.