Product design question

Design an onboarding flow to convert VS Code users to Cursor.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Basic onboarding design principles applied to a migration scenario with an entrenched competitor habit.

Clarify the user: a VS Code user with existing extensions, settings, and keybindings who fears losing their familiar setup by switching.
State the core pain point: rebuilding a personalized editor setup from scratch is the biggest friction in switching editors.
Propose an automatic import step: detect and migrate VS Code extensions, themes, and keybindings on first launch, so Cursor feels familiar immediately.
Introduce AI features progressively after the familiar environment is restored, rather than overwhelming the user with new capabilities before they feel at home.
Define success: percentage of new users who complete the import and keep using Cursor daily after one week, versus reverting to VS Code.

Leads with automatic settings and extension import, directly removing the single biggest friction point in an editor migration.
Sequences AI feature introduction after familiarity is established, avoiding overwhelming a user who just wants their old setup back first.
Names a concrete retention metric, one-week active usage after import, as the real signal of successful migration rather than just install count.
Recognizes the emotional stakes of a developer's personalized setup, which is why the import step matters more than any AI capability at first.

Leading onboarding with AI feature demos before addressing the practical friction of rebuilding a familiar environment.
Measuring only installs instead of sustained daily usage after the switch.

How would you handle extensions that are not compatible with Cursor's architecture?
What would you do if import succeeded but users still reverted to VS Code within a week?