How to Explain Your Work in an Interview (What My Google Rejection Taught Me)

Communication is the one skill that can't be faked in an interview. Your resume can be polished by you, by a friend, even by AI. But when the interviewer looks up and asks "so what exactly did you do?", it's only you and the way you explain your work, in that moment.

Many times I got rejected because of how I spoke and explained my ideas and solutions. Here's the one I remember most.

The day my answer changed my job title

I still remember my interview for Google's project management apprenticeship.

They asked me about my current role, and I explained everything: every task, every responsibility, in full detail. I thought more detail meant more proof that I knew my work.

Then the interviewer paused and asked, a little confused: "Sorry, what is your role called?"

"Project management," I said. It was true. But by then my answer had already told a different story. I had described someone who does the tasks, not someone who manages them. I told them what I did, not what I made happen.

I didn't get the role.

My title was right. My story was wrong. And in an interview, the story is the only thing they hear.

Maybe something like this has happened to you too: you knew your work, but your answer said something else.

What I'd say today

"I managed the development of a custom web app for my company. The problem was visibility: every department tracked its part of the process in its own Excel sheets, so no one could see the whole picture. I worked with the user departments to understand what each of them needed, so that all the data could sit in one place and everyone could see where the process stands."

Same work. Same me. But this time the answer sounds like a project manager, because it talks about the problem, the people and the goal, not a list of tasks.

That day I learned that communication isn't about how much you say. It's about whether your words show who you really are.

Why employers care so much about this

This isn't only my experience. NACE, a US association that surveys employers hiring new graduates every year, found in its 2026 survey that employers look for people who can "work in a team, problem-solve, and communicate effectively". And it adds something important: employers "want to see examples" of those skills, not just a list of them (NACE, April 2026).

That's what went wrong for me: I gave a list of tasks, when what they needed to hear was how I managed the work.

And it's not only interviews. The clarity of thought while speaking gives you an edge in many conversations, professional or not: with your manager, with a client, even when you're asking someone for a referral.

How to explain your work so it lands

So how do you get better at this? You don't need perfect, memorised answers. You need a simple shape that you practise until it feels natural.

1. Start with the problem, not your task list. Before you say what you did, say what was wrong. "Every department kept its own Excel sheet, so nobody could see the whole process" tells the interviewer more than ten tasks.
2. Use the STAR shape for your stories. Career advisers at MIT describe it like this: the situation, so the interviewer understands the context; the task you took responsibility for; the actions you personally took; and the result your actions produced (MIT CAPD). They also suggest using "I" rather than "we", so it's clear what you did, and giving numbers where you can.
3. Say it out loud before the real interview. Record yourself answering "Tell me about your current role" on your phone, and listen back. You'll hear the moment you start listing tasks.
4. Think before you start. Before you answer, decide the one thing you want them to remember. Then build the answer around it.

Your list of five things from Part 2 is where your stories come from. Each one already has a problem and "what changed". Now you only need to practise telling them. If you haven't made that list yet, Part 2 shows you how.

After all this, it's you who has to work

No article can give the interview for you. After all this, it's you who has to do the work: the practice, the messages, the applications.

But you don't have to do it all today. Start with step 1. Pick one thing you did this year, and explain it out loud, in two minutes: the problem, the people, and what changed. Then do it again tomorrow, a little clearer.

That's how I'd start if I were looking again today. And when that call comes, walk in knowing the problem, the people and what changed.