Xmind — Marketing-Site Engineering & Growth Tooling

Drove the migration of the global and China-region marketing sites onto a new platform while keeping the legacy stack running through the transition. Took ownership of reliability and performance across both regions, including the operational tooling and team-facing release flow that came with the move.

Led a company-wide migration of the event-tracking layer — unifying schemas so a single product event surfaces consistently across the analytics stack. Wired up cross-domain attribution between the marketing site and the editor, region-aware privacy compliance, A/B-experiment tracking, paid-search attribution, and a set of dashboards covering overview, trend and traffic-quality views. Wrote the tracking SOP the rest of the org now follows.

Designed and built the internal platform that lets the GTM team publish interactive content pages — the kind of small AI-assisted converters you see on a marketing site — without engineering involvement. The product surface integrates an admin UI, content management for the tool pages, an automation engine for the processing pipelines, and observability hooks for usage and quota.

Designed, built and shipped two Chrome extensions to the Web Store: a NotebookLM → Xmind exporter and a Baidu Mind Map → Xmind exporter for the China region. Both handle first-time-user hints, a clean editor handoff, attribution back into the marketing analytics, and the full store-review submission cycle.

Owns the technical-SEO surface for both regions — automated structured-data generation, multi-language sitemap reliability, canonical / robots / metadata audits, cross-region link-graph fixes, and search-console integration. Also reduced the legacy server's error noise floor and wired up the affiliate marketing flow across all three customer-facing domains.

Shipped the engineering side of every marketing campaign cycle since joining — Black Friday across both regions, Back-to-Work, Pro+ launches, the China-region Book Day campaign, the year-end Recap, and the team / business order pages. Each cycle typically meant new tracking events, pricing-page variants, order-page CTAs, and time-bounded UI changes shipped across the marketing site, the legacy stack and the editor, all without breaking attribution.