Product design question
Suno is considering a new mobile editing workflow that lets users revise an AI-generated song after creation. How would you scope the v1, decide what to ship now versus later, and make tradeoffs between launch speed, experience polish, and investing in foundations that can support future editing features at scale?
- Suno
- Product design
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Scoping judgment for a v1 feature: balancing launch speed, user experience, and technical foundations.
How to approach it
- Define what editing means for v1, such as regenerating a section or adjusting lyrics, versus full re-mixing, which is likely out of scope initially.
- Identify the core mobile interaction, like selecting a song segment and issuing a text-based revision request, and prototype that first.
- Decide what to cut for v1 versus defer, such as advanced waveform editing, based on what most users actually need to feel in control.
- Evaluate tradeoffs between shipping fast with a narrow edit surface versus investing now in an architecture that supports finer-grained future editing.
- Define a success metric for v1, such as percentage of generated songs that get at least one edit, to validate demand before expanding scope.
- Plan the foundation work, like a versioned song state, so v1's fast path does not block later features.
What a strong answer includes
- Picks a narrow, well-defined v1 edit action instead of trying to cover every possible revision type.
- Explicitly names what is deferred and why, showing a deliberate tradeoff rather than an accidental gap.
- Invests selectively in one foundational piece, like versioned song state, that unlocks future editing without slowing v1 down.
- Ties the launch decision to a concrete usage metric instead of a subjective sense of polish.
Common mistakes
- Trying to ship a fully flexible editor in v1 and missing the launch window.
- Ignoring foundational architecture entirely and creating rework for every future editing feature.
Likely follow-up questions
- What would you cut first if the timeline slipped by three weeks?
- How would you validate demand for editing before building it?
- What foundational investment would you protect even under time pressure?
More product design questions
- Suno wants mobile to become the default place people make music for fun. Design the mobile creation experience for two segments: a first-time user with no music background and a repeat creator who wants more control. Walk through the core flow, what you would simplify or hide for beginners, where you would add depth for advanced users, and the key product decisions that make the experience feel effortless and expressive on a small screen.Suno · Product design · Hard
- Suno wants to open a new revenue line for professional creatives, small teams, and larger companies. How would you define the first team product, choose the minimum collaboration/admin/security capabilities for an MVP, and prove there is a path from pilot demand to repeatable revenue?Suno · Product design · Hard
- Design a TV for a car.Google · Product design · Hard
- Design a refrigerator for the blind.Google · Product design · Hard
- Redesign Twitter for eCommerce.Shopify · Product design · Hard
- You are a PM at Flipkart. The company has decided to increase the userbase of age >60 years on the platform. What will you do?Flipkart · Product design · Hard
More questions from Suno
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovering and Sizing AI Opportunities
- Chapter 7: Designing AI UX and Oversight
- Chapter 14: Interviewing for AI PM Roles