Persado — AI Marketing Language Platform

Persado is an AI platform that generates and optimizes marketing language for enterprise brands. The product analyzes emotional and linguistic patterns to produce copy that outperforms human-written alternatives across email, web, SMS, and ad channels.

I joined the platform team as one of two frontend engineers, working alongside 3 backend engineers and a team lead (fullstack + manager). The core mission was migrating the legacy AngularJS application to React while continuing to ship new features on the existing codebase.

The challenge: a large, production AngularJS app serving enterprise clients needed to be modernized to React without disrupting active users or slowing down feature delivery. The team had to run both frameworks in parallel during the transition.

Drove the incremental migration from AngularJS to React. This wasn't a rewrite-from-scratch; it was a surgical, component-by-component transition inside a running production app. New features shipped in React, existing surfaces were migrated as they were touched, and both frameworks coexisted through the transition period.

In my second year, the other frontend engineer left. From that point I was the sole frontend engineer on the team, responsible for continuing the migration, maintaining the existing AngularJS surfaces, and delivering new features in React, all at the same time.

Steered the direction for the team's first end-to-end testing approach using WebdriverIO. This meant defining the test architecture, writing the initial test suites, and establishing patterns the team could follow. Before this, the product had no automated browser-level testing, which was a real risk for an enterprise platform where regressions hit paying clients directly.

Shipped features across the full product surface throughout the 2+ year engagement: campaign builders, content generation workflows, analytics dashboards, and admin tooling. The GraphQL API layer was the primary data interface between frontend and backend.

Started as part of a 6-person product team with a clear division between frontend and backend. After the other frontend engineer's departure, I operated as the single point of ownership for everything in the browser: migration decisions, new feature architecture, test strategy, and code review standards. Collaborated daily with the backend engineers and team lead on API contracts and release planning.