Strategy question
A regulated enterprise wants to expand beyond a pilot, but the security review fails on governance, data handling, and compliance concerns. How would you determine what is a true product gap versus something that can be handled through process, documentation, or roadmap commitments, and how would you align engineering, sales, and security on the response plan?
- Replit
- Strategy
- 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
Tests the ability to separate true product gaps from process or communication issues in a failed security review, and align three functions on the response.
How to approach it
- Get the specific security review findings in writing rather than a general sense of what failed, since vague objections are hard to resolve.
- Classify each finding as a true product gap, missing SSO or audit logging, or a process gap, missing documentation or unclear data handling policy.
- For true product gaps, scope the engineering effort and decide if it is fast enough to unblock this deal or needs a broader roadmap commitment.
- For process gaps, work with security and legal to produce documentation or contractual commitments that resolve the concern without new engineering work.
- Align sales, engineering, and security on a single response plan with owners and dates for each finding, rather than three separate answers to the customer.
- Communicate a unified, realistic timeline back to the customer, being explicit about what ships now versus what is a roadmap commitment.
What a strong answer includes
- Separates true product gaps from process and documentation gaps explicitly, since conflating them leads to unnecessary engineering work or false promises.
- Insists on a single aligned response plan across sales, engineering, and security instead of letting each function answer the customer separately.
- Distinguishes fast fixable product gaps from ones that require a genuine roadmap commitment, and communicates that distinction honestly to the customer.
Common mistakes
- Assuming every failed review item is a product gap requiring new engineering work, when some are really documentation or process issues.
- Letting sales promise a fix timeline to the customer before engineering and security have actually aligned on scope.
Likely follow-up questions
- How would you handle a finding that is genuinely a product gap but not on the near term roadmap?
- What would you do if sales already promised the customer a date before you were looped in?
More strategy questions
- How would you convert hobbyist users into paying enterprise customers?Replit · Strategy · Hard
- How should Replit compete with Lovable and v0 in the vibe-coding space?Replit · Strategy · Hard
- You have one year to make Replit enterprise-ready with a constrained engineering team. How would you sequence the roadmap across identity and access (SSO/SCIM, RBAC), governance/admin controls, deployment options (for example single-tenant or Cloud-Prem), and end-user Agent workflows for non-technical employees? Explain the tradeoffs you would use to decide what ships in the first 2 quarters versus later.Replit · Strategy · Hard
- Google Keep is a free product to save, share notes etc. How would you make it a subscription product & monetize it?Google · Strategy · Hard
- How would you launch (roll out) Amazon Go?Amazon · Strategy · Hard
- With an unlimited network bandwidth what would you build?Google · Strategy · Hard
More questions from Replit
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop