Describe one thing you have learned recently
Asked at:
Microsoft
Meta
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess whether you are actively learning, how you choose what is worth learning, and whether that learning changed how you work. It is less about the topic itself and more about your curiosity, self-awareness, and ability to turn new knowledge into better judgment or behavior. At higher levels, interviewers also look for whether your learning compounds beyond you and improves a team or organization.
“What's something new you've picked up in the last few months, and how has it changed how you work?”
“Tell me about a recent learning that stuck with you.”
“Have you changed your mind about anything important at work recently? What led to that?”
“What's a lesson you've learned lately from your work experience?”
“What have you gotten better at recently, and what drove that change?”
Key Insights
- You do not need an impressive or trendy topic; a strong answer shows why the learning mattered, how you pursued it, and what changed afterward.
- You should connect the learning to a real problem, decision, or gap. Answers that sound like passive consumption of content usually feel weak unless you explain how you applied it.
- For senior and above, make sure the learning affected more than your personal productivity. Interviewers often want to hear how your new understanding influenced other engineers, team practices, or direction.
What interviewers probe atlevel
Top Priority
Do not stop at what you learned; explain what you did differently afterward and how you know it helped.
Good examples
🟢After learning that, I changed how I wrote tests on my next two tasks and the reviews went much more smoothly because I was catching isolation issues earlier.
🟢I started using logs and metrics before asking for help on production bugs, and I was able to narrow down the next issue much faster.
Bad examples
🔴Now that I understand it better, I feel more confident working in that area.
🔴Since learning that concept, I just try to keep it in mind when coding.
Strong answers make the learning visible in changed behavior and results, while weak answers leave the learning as a feeling or intention.
Pick something recent that genuinely improved how you build, debug, collaborate, or understand systems; it does not need big scope, but it should matter to your day-to-day work.
Good examples
🟢I recently learned how to trace a production issue through logs instead of only reproducing it locally, which helped me debug a bug that had been confusing me for a while.
🟢I learned why our test suite was flaky in one area and how test isolation works, so I changed how I wrote tests and started catching issues earlier.
Bad examples
🔴I recently learned a shortcut in my editor that helps me move faster, and that was useful because I save a few clicks every day.
🔴I learned about a new framework from videos online, and it seemed better than what my team uses so now I want to use that instead.
Strong answers choose learning that improves engineering judgment or effectiveness, while weak answers choose something trivial, disconnected from real work, or fashionable without relevance.
Valuable
Be honest about what you did not know and what changed in your understanding; that reads as coachable, not weak.
Good examples
🟢I realized I had been treating the symptom instead of understanding the root cause, and that changed how I approached similar bugs.
🟢I was initially focused on getting unstuck quickly, but I learned I needed to understand the underlying behavior so I would not repeat the same mistake.
Bad examples
🔴I already understood most of it, but this helped confirm that my original instinct was right.
🔴The main lesson was that I need clearer explanations from others when things are confusing.
Strong answers show self-awareness and genuine updating, while weak answers protect the ego or shift responsibility outward.
Example answers atlevel
Great answers
One thing I learned recently was how to debug issues in production-like environments using logs instead of only trying to reproduce everything locally. I had a bug where I kept changing code without really understanding why a request was failing, and a teammate pointed out that the logs already showed the bad input path. After that, I spent some time learning how our logging was structured, asked a few questions about what fields were most useful, and tried the approach on the next issue myself. It changed how I work because now I start by narrowing the problem down from logs and request traces before guessing. On my most recent ticket, that helped me find the root cause much faster and my reviewer even commented that my investigation notes were much clearer.
Recently I learned the basics of web accessibility and why small changes can make a big difference for users. While implementing a simple marketing page for a client, a designer asked whether keyboard users and screen readers could navigate the signup form — I realized I didn't really know. I spent an afternoon reading a few accessible patterns, added proper labels and focus styles, fixed color contrast, and tested the form with a screen reader and keyboard-only navigation. My changes were small but eliminated several usability issues, and I started including a short accessibility checklist in my pull requests so reviewers and designers can confirm those things quickly.
Poor answers
One thing I learned recently was a bunch of keyboard shortcuts in my editor. It has actually been really helpful because I can move around files a lot faster and look more productive during coding sessions. I try to keep up with those kinds of tricks because they save time. I think learning small things like that regularly is important.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid June, 2026
Staff
Late February, 2026
Microsoft
Senior
Late September, 2024
Meta
Staff
Describe one thing you have learned recently
Hello Interview Premium
Your account is free and you can post anonymously if you choose.