Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer Limited Information Interview Questions
Transcript
- Lucas: So you're in an interview, and the hiring manager asks: Tell me about a time you had to make a decision with limited information. That's a classic behavioral question, and it's one that a lot of candidates find tricky because it feels like a trap. But actually, it's one of the most valuable signals an interviewer can get. Luna: I can see why. On the surface, they're asking about a situation where you didn't have all the facts. But what are they really looking for? How you handle uncertainty? Your judgment under pressure? Lucas: Exactly. They want to see that you can move forward without perfect data, that you can weigh risks and trade-offs, and that you're not paralyzed by ambiguity. In a lot of roles—especially product management, consulting, and leadership—you'll rarely have complete information. So this question is a proxy for whether you can function in the real world. Luna: Right. So the worst answer would be one where you had perfect information and just made a straightforward choice. That doesn't demonstrate anything. Lucas: Exactly. You need a story where there was genuine uncertainty. Let me walk through an example. Let's say you're interviewing for a product manager role at a mid-stage SaaS company. A good story might be: You were responsible for deciding whether to build an integration with Slack or with Microsoft Teams, and you only had limited user feedback—maybe survey data from a small sample and some anecdotal requests from your top accounts. You didn't have usage analytics, you didn't have a clear revenue model for either integration, and you needed to make a call within two weeks to hit the next product release. Luna: That's a perfect scenario. So how would you structure the answer? Lucas: I teach a slight variation on STAR. I call it star li. Situation, Task, Action, Result, Learning, and Impact. The 'Learning and Impact' part is where you really show your growth. Let me apply it. Situation: Your company's product roadmap had an integration gap, and engineering had capacity for exactly one integration in the next quarter. Task: Decide which integration to build—Slack or Teams—to drive user adoption and revenue. Action: You didn't just flip a coin. You talked to five of your largest customers, looked at competitor integrations, and ran a quick survey that got 40 responses. You also estimated development cost and maintenance for each. Luna: So you're building a structured approach even with limited data. That's key. Lucas: Yes. You might also mention that you explicitly identified what you didn't know and treated those as unknowns. That shows self-awareness. Then the result: You chose Slack because your top three accounts all used it heavily, and development was 20% faster. The integration launched on time and led to a 15% increase in daily active users within two months. Learning: You learned to prioritize direct stakeholder input over general market trends when data is scarce. Impact: That decision informed how your team handled future build-vs-buy decisions, and you now have a lightweight framework for quick decisions. Luna: I like that the learning is specific. You're not just saying 'I learned to trust my gut.' You're showing a concrete takeaway. Lucas: Exactly. And the interviewer will note that you articulated both the upside and the downside. You could also mention what you would have done differently if you had more time. For example, you might say: 'If I had another week, I would have run an A/B test on the landing page to measure interest. But given the deadline, I felt this was the best course of action.' Luna: That shows you still have a hypothesis about what better data looks like. You're not just accepting the limitation, you're actively thinking about how to overcome it next time. Lucas: One trap to avoid: don't frame your decision as a gamble. Don't say 'I took a leap of faith.' That undermines your credibility. Instead, say 'I weighed the available evidence and made the best call with the time I had.' Luna: And what about if the outcome wasn't great? Should you still use that story? Lucas: You can, as long as you owned it and learned something. The interviewer doesn't always need a happy ending. In fact, a story where you made the wrong call but recovered or adjusted is often more powerful. It shows resilience. Just be careful: the failure should be a learning opportunity, not a career-limiting mistake. Don't pick a story where you cost your company millions. Luna: Right. So the key takeaway: prepare a story from your own experience that involves genuine uncertainty, use the star li framework, and be honest about what you didn't know. Lucas: And practice it out loud. Get comfortable with the structure so it sounds natural. Let me give one more tip: when you hear the question, take a breath and say 'Sure, I have a good example.' That gives you a moment to collect your thoughts. Luna: Yeah, that pause is better than jumping in with 'um' and then rambling. Lucas: Exactly. One more thing: you can also pre-emptively mention a specific piece of information you wish you'd had. That shows you're thinking about data quality, not just data quantity. Luna: Alright, so if today was actually useful to you, the way these episodes stay ad-free is through listener support. If you've gotten value from the show, consider buying us a coffee at buy me a coffee dot com slash fexingo. Lucas: Yeah, and we really appreciate it. Every contribution helps us keep making this for you. No pressure, just if it's something you want to do. Luna: So to sum up: when you face that limited-information question, don't freeze. Use star li, be transparent about your process, and show that you can act decisively without perfect data. Lucas: And remember, the interviewer wants to see that you can think on your feet. So a strong answer here will set you apart from candidates who can only operate with a full deck.