Describe your approach to solving new and unfamiliar problems, including any strategies or methodologies you use.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you operate when there is no obvious playbook: how you reduce ambiguity, choose a path forward, and keep learning as new information appears. They are usually less interested in a specific methodology name than in whether your approach is structured, adaptable, and appropriate to your level. Strong answers show not just analysis, but ownership, judgment, and evidence that you can make progress without waiting for perfect clarity.
Key Insights
- You do not need to sound like you always know the answer quickly. A strong answer often starts with how you frame the unknowns, decide what to learn first, and avoid thrashing.
- Don't stop at 'I researched and asked for help.' Explain how you decided what to try, how you validated assumptions, and how you knew you were making progress.
- At higher levels, unfamiliar problems should affect more than just your own task. Show how you created clarity for others, reduced repeated confusion, or set direction under uncertainty.
What interviewers probe atlevel
Top Priority
Even at the junior level, a strong answer should end with what happened, what you learned, and how that changed your next approach.
Good examples
🟢After solving it, I checked that the fix actually addressed the original problem and wrote down the key lesson so I could reuse it later.
🟢I finished the work, got feedback on whether my approach made sense, and used that learning the next time I hit a similar problem.
Bad examples
🔴Eventually I found a solution and finished the task, so overall I think my approach worked well.
🔴Once I got it working, I moved on to the next thing because the main goal was just to complete the assignment.
Weak answers stop at task completion; strong answers show verification and evidence of a learning loop.
Valuable
Example answers atlevel
Great answers
When I run into a problem that's new to me, I try to avoid jumping straight into a full solution. On a recent project, I had to add a background job and I hadn't worked with that kind of processing before. I first clarified what success meant with my mentor, then wrote down the parts I understood and the parts I didn't, and built a very small test version just to confirm the basic flow. After that, I read the relevant docs and asked a few specific questions about error handling instead of asking someone to explain everything. Once it was working, I tested it against the original requirements and added notes to our team page so I could reuse the same approach later.
I tackle unfamiliar problems by making the unknown concrete — first I reproduce the issue or write a tiny, runnable example so I can see what actually breaks. For example, when I had to add client-side offline caching at my startup (something I hadn’t done before) I mapped the essential user flows that needed to work offline, built a minimal prototype to observe failures, and used browser logs and a couple of unit tests to pinpoint wrong assumptions. I read one or two well-regarded articles and skimmed a few open-source implementations to pick sensible patterns rather than following a long tutorial. Once the prototype covered the critical flows, I turned it into a focused pull request with tests and a short demo for the team so we could get feedback and iterate quickly.
Poor answers
Usually with new problems I just get hands-on right away because that's how I learn best. In my last internship I had to work with a tool I hadn't seen before, so I tried different examples from the internet until something worked and then I adapted that to our code. If I get stuck for a while, I ask whoever is nearby because it's faster than spending too much time thinking about it. That approach has worked pretty well for me so far.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late March, 2026
Late January, 2025
Hello Interview Premium
Your account is free and you can post anonymously if you choose.