Setting up Marketo and Salesforce inside RingCentral Events

Migrating the integrations page

• Led the migration of the organization integrations page from a standalone micro-frontend into the main dashboard application, with no change for customers.
• Moved it onto the application’s current UI, data-fetching and testing stack instead of copying the old code across.
• Planned the work, built the data layer and core screens, wrote most of the tests, ran the bug bash, and removed the old code once the new page was live.
• The old and new pages ran side by side behind a feature flag, so the switch could be staged and reversed.

Marketo setup in the product

• Built in-product setup with account connection, field mapping, validation and sync status.
• Rolled it out in phases behind a feature flag, with several bug-bash rounds and a one-step rollback.
• Checked that existing customers’ mappings carried over unchanged.

Salesforce setup and engagement sync

• Rebuilt setup as a guided, tabbed experience for campaigns, registrations and engagement.
• Built mapping for standard and custom objects, plus registration sync to leads, contacts or both.
• Replaced manual credential entry with an embedded sign-in flow and clear authentication-error messages.
• Shipped behind feature flags in two stages, kept the old experience available until the new one was proven, then removed the legacy code.

Decisions

1. Changing the foundation without changing the experience

   The migration replaced the page’s styling, data and state layers while keeping behavior the same, so staged rollout and parity checks mattered more than speed.

2. Large accounts and partner rate limits

   Choice

   I kept the setup screen responsive for very large accounts by loading data without blocking the page, and stayed within the partner API’s limits by throttling requests and retrying failures safely.

   Reason

   I chose throttling over caching because caching would have broken the retry behavior.

3. Shared foundations

   Some changes touched code that other teams depend on, so they went through cross-team review.

4. Race conditions in shared state

   Context

   Several data sources loaded at once through one shared loading flag, so the first to finish could hide the others’ progress.

   Choice

   Giving each source its own loading and error state fixed it.

5. Data integrity

   Context

   Temporary values used while editing a mapping could end up in the saved configuration.

   Choice

   I added a filter so only complete mappings are saved.

6. Doing less work per page load

   I cut unnecessary network calls and stopped stale data from appearing when switching accounts.

Results

• ✓The in-product Marketo setup was released in April 2025, with a public help article.
• ✓Later work kept it reliable for the largest accounts.
• ✓The refreshed Salesforce setup was released in October 2025 with a public help article, followed by a sync-options update later in 2025.

What this shows

• Frontend architecture
• Incremental migration
• Feature-flag rollout
• Third-party API integration
• Rate-limit handling
• Technical leadership
• Test strategy
• React
• State management
• CRM integration
• Embedded third-party sign-in
• Feature-flag migration
• Test refactoring