Product design question

Design a marketplace for pre-built Lindy agent templates.

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

Tests product design for a two sided marketplace, balancing template creators, template users, and platform quality.

Define the two sides: creators who build and publish reusable agent templates, and users who want a fast starting point instead of building from scratch.
Design the creator experience: a simple way to package an existing agent as a template, strip out private data and credentials, and describe what it does.
Design the discovery experience for users: browsable by use case and industry, with clear information on what integrations and setup a template needs before installing.
Address quality and safety: review or verification before a template is listed, since a bad or malicious template could misuse a user's connected accounts.
Consider incentives: whether creators are rewarded through recognition, revenue share, or simply exposure, since that drives supply of good templates.
Confirm with the interviewer whether this marketplace is free, paid, or a mix, since that changes both the review bar and the incentive design.

Explicitly addresses stripping private credentials and data before a template is published, since agent templates are unusually risky to share compared to static content.
Proposes a review or verification step before listing, given a malicious template could be used to phish or misuse connected accounts like Gmail or HubSpot.
Designs discovery around use case and industry rather than a flat list, since template value depends heavily on matching the right business context.
Considers creator incentives explicitly, noting recognition or revenue share affects whether high quality creators keep contributing over time.

Ignoring the security risk of sharing agent templates, which can carry logic that touches sensitive connected accounts.
Designing discovery as a plain search bar without categorization by use case, making it hard for non technical users to find a fit.
No plan for creator incentives, risking a marketplace with few or low quality templates over time.

How would you vet a template for safety before publishing it?
What would motivate someone to spend time creating and sharing a template?
How would you handle a popular template that breaks after an integration changes?