Tell me something about yourself I won't find on your resume
Asked at:
Microsoft
Amazon
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This question tests judgment in self-presentation: can you choose something that is personal enough to feel real, but still professionally relevant? Interviewers are usually looking for self-awareness, communication skill, and clues about how you work with others that a resume cannot show. A strong answer adds useful signal about your character, motivations, or working style rather than offering a random fun fact or repeating your job history.
“What's something important about you that's not obvious from your resume?”
“If I asked your teammates to tell me something about you that isn't in your background, what would they say?”
“What's a part of how you work or who you are that your resume doesn't capture well?”
“Tell me one thing that would help me understand you better beyond your job history.”
“What is something you'd want the interview panel to know about you that we wouldn't learn from reading your resume?”
Key Insights
- You do not need to be deeply personal; you do need to be meaningfully revealing. Pick something that helps the interviewer understand how you operate, what you value, or why teammates like working with you.
- The best answers have a quiet professional payoff. Even if the topic is outside work, connect it to a trait like discipline, curiosity, empathy, teaching, or resilience without sounding rehearsed.
- Avoid treating this like a trivia prompt or a second resume walkthrough. The hidden test is whether you can read an open-ended situation and choose a story that is memorable, appropriate, and useful.
What interviewers probe atlevel
Top Priority
A simple, believable connection to school, internships, or teamwork is enough; do not staple on a fake leadership lesson.
Good examples
🟢I tutor first-year students sometimes, and it has made me better at checking whether I really understand something or just recognize the words. That habit has helped me ask clearer questions when I am learning on the job.
🟢I built a small budgeting tool for my family, and while it was not a formal project, it taught me to gather messy requirements from real people and keep the solution simple enough that they would actually use it.
Bad examples
🔴I do photography, and that proves I am detail-oriented, which is why I would be a great engineer here.
🔴I like running, so I know how to work hard and never give up, and that basically applies to every project I do.
Weak answers tack on generic traits; strong answers make a specific and believable connection between the story and day-to-day work.
Valuable
Be personable, but keep the answer interview-appropriate and easy for a stranger to engage with.
Good examples
🟢Something people do not always expect is that I enjoy teaching beginners, whether it is coding or even helping friends with basic tech issues. I like finding the version of an explanation that actually clicks for someone.
🟢One thing not on my resume is that I am usually quieter at first, but I am very consistent once I understand the problem. I tend to listen carefully, write things down, and then contribute in a structured way.
Bad examples
🔴I am a huge gamer and honestly spend most of my free time on that. It has taught me a lot about systems thinking, so I think it is pretty relevant.
🔴Something not on my resume is that my last team was kind of chaotic, so I had to be the organized one all the time. That probably says a lot about me.
Weak answers either overshare or introduce awkward signals; strong answers are personal enough to be memorable while staying professional and easy to discuss.
You are not expected to sound like a leader of an organization; sounding coachable and grounded is better than overselling.
Good examples
🟢One thing not on my resume is that I am pretty intentional about asking follow-up questions until I really understand a problem. I know I am still early in my career, so I try to learn fast without pretending I already know everything.
🟢Something people might not get from my resume is that I am reliable in unglamorous work. If a team needs someone to document what we learned or clean up a rough handoff, I am usually happy to do it.
Bad examples
🔴Something not on my resume is that I am basically the kind of person who naturally drives teams forward, even when I am new.
🔴I would say my biggest hidden strength is that I can usually see the big picture before everyone else, which is why I tend to take charge.
Weak answers oversell authority they have not earned; strong answers show maturity, humility, and useful habits for an early-career engineer.
Example answers atlevel
Great answers
One thing you would not find on my resume is that I really like being the person who makes confusing things easier to understand. In school, I often organized small study sessions before exams, and I noticed I learned best when I had to explain a topic clearly to someone else. That habit carried into my internship too, where I started writing short notes for the next intern when I figured something out. I think it says a lot about how I work: I am curious, I ask questions, and I like leaving things a little clearer than I found them.
Something you won't find on my resume is that I volunteer building and maintaining simple websites and phone apps for the local senior center. Because the users have varying levels of tech comfort, I learned to strip features down to the essentials, use very clear language, and make fixes that actually reduce confusion in one or two steps. On those projects I handled both the technical side and the user conversations, which taught me to translate real needs into practical changes and to prioritize reliability over cleverness. That experience has shaped how I approach even small work tasks: I focus on the smallest change that delivers obvious value and I validate it with the people who will use it.
Poor answers
Something you would not find on my resume is that I am very competitive. I played sports growing up and I hate losing, so I usually push hard and try to stand out in group settings. I think that helps a lot in engineering because it means I will work longer than other people if needed. It is probably one of the main reasons I do well.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid March, 2026
Junior
Late February, 2026
Microsoft
Mid-level
Early December, 2025
Microsoft
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.