How You Can Always Be Ready for an App Critique in Interviews
- Tianyu Koenig
- 2 days ago
- 3 min read
Recently, several candidates told me the same story during their interview debriefs.
The interviewer casually asked, “What’s your favorite app?”
And before they realized it, the conversation turned into a 10-minute deep dive.
No one told them there would be an app critique.
Not HR. Not the interview prep materials.
But here is the truth.
Most companies will not explicitly label a round as “App Critique.”
And many interviewers will not frame it that way either.
Instead, they ask something simple like,
“What’s your favorite app and why?”
And within five to ten minutes, they can already tell everything they need to know.
They are evaluating how you think about products.
Whether you rely on intuition or structured reasoning.
Whether you understand both users and business, not just UI.
And whether you can clearly explain your thinking.
This Is Not a Question. It Is an Evaluation
What looks like a casual question is actually one of the most efficient ways to assess product sense.
You are not being judged on whether you pick the “right” app.
You are being evaluated on how you break it down.
Do you jump straight into opinions, or do you structure your thinking?
Do you talk only about features, or do you connect them to user goals?
Do you stay surface-level, or go deep into one meaningful flow?
Most candidates fail not because they lack insight, but because they lack structure.
Here is a simple 5-min template that can help you succeed next time.
A Simple Five-Minute Template
10-Second Opening
“I’ll use [App] since I actively use it. I’ll focus on one core flow and how well it supports the primary user goal.”
No need for too much background. Get straight to the point.
One-Minute Background (Only Key Information)
You can include:
Core user: Define the primary user.
Core value: The key problem the app helps users solve.
Your perspective: Briefly explain how you use it, what problem or pain point it solves for you, and why you chose this product over its competitors.
This could be due to performance advantages, or alignment with the company’s mission.
2–3 Minutes Deep Dive into One Flow (Core)
Choose one key user flow.
Highlight analysis: Specifically explain what is done well, from the overall user flow to individual pages and interaction design, going from shallow to deep.
The key is to clearly explain why you think it works well: tightly connect it to user needs and business goals, and articulate your design thinking from different angles. You can also incorporate your own insights about users and the market to support your reasoning.
Avoid only stating opinions like “I like this,” “I think this is better,” or “Based on my own experience…” without evidence or explanation.
60–90 Second Conclusion: Provide One Improvement
Only suggest one improvement. Do not be greedy. Focus on showing logical thinking.
Clearly specify what you want to change.
Example: “Add a quick ‘View Order’ button on the payment success page.”
Core value: Explain the benefits for both users and the business.
Example: “Users can quickly check logistics, improving satisfaction; reduce drop-off, indirectly increasing repurchase.”
Risk and trade-offs: Proactively mention potential issues and trade-offs.
Example: “It may take up ad space; need to test the balance between button click-through rate and ad revenue.”
Final Thought
The most effective way to improve is not reading more frameworks.
It is practice.
Practice breaking down different products.
Practice explaining your thinking out loud.
Practice handling follow-up questions.
Even better, do mock interviews with someone who can challenge your thinking.
Because in the real interview, structure gets you in.
But clarity and adaptability are what make you stand out.
If you are preparing for product or product-adjacent roles,
assume every interview includes an app critique.
Even if no one tells you.
Need help practicing this framework? Book a free 15-minute session with me below.
Comments