Explaining a Technical Concept to a Non-Technical Stakeholder Ends With Their Decision

How you explain a technical concept to a non-technical stakeholder is judged mostly on one result. That result is what the person could decide afterward. Most answers stop at the analogy. The candidate describes a clever comparison and ends with “they finally got it.” The interviewer can’t score that. All they have is your report of a nod. A strong answer names the decision the listener faced before you spoke. It names the one technical limit that changed that decision. It gives the comparison you used. That comparison keeps the limit intact. Then it says how you checked they understood. Last, it says what they chose. Say a product manager picks a different option after your explanation. Now you have a result the interviewer can write down. This post follows one Android story through each step. It ends with a full answer of about ninety seconds.

Interviewers score this story on the listener’s decision

The Tech Interview Handbook rubric page for behavioral rounds lists eight focus areas. It was last updated in August 2026. Communication is one of the eight. The page says it overlaps with empathy. Empathy there means how well you see things from other people’s perspective. The same rubric appears in an interviewing.io post by Lior Neu-ner. He is a former Meta engineer and engineering manager. That page shows no publish date. Neither version mentions analogies or plain language. Both ask whether you saw the problem from the other person’s side.

In a story about a non-technical stakeholder, the other person’s side is usually a decision. A product manager might be deciding scope. A support lead might be deciding what to tell customers. Your explanation exists to make that decision possible. So the result of the story is the decision and what happened after it.

Ending on “they finally got it” leaves the interviewer nothing to score

The common answer runs like this. The engineer had a hard concept to explain. They found a comparison. The stakeholder nodded. The story ends there. The interviewer has to take the nod on trust. Expect the follow-up that tests it: “How did you know they understood?”

The other weak version explains too much. The candidate retells the protocol detail to prove they know it. That repeats the mistake the question asks about. Chip and Dan Heath called this the curse of knowledge in a 2006 Harvard Business Review article. Once you know a subject well, it’s hard to picture not knowing it. Our post on why “too detailed” gets engineers rejected covers the same habit inside the round itself.

A heater app that showed “on” for a heater that had shut off

Take Omar, an Android engineer at a company that makes heaters for camper vans. The app talks to the heater over Bluetooth Low Energy. Android’s BLE overview lists moving small amounts of data between nearby devices as a common use. So the phone learns the heater’s state only when it’s near the van. Out of range, the app kept showing the last state it had received. It gave no time with it.

Support started getting tickets. Users checked the app from a café and saw “Heater on.” They came back to a cold van, because the heater had shut off on low battery. The product manager asked Omar to make the status accurate. Omar could have replied that Bluetooth only works up close. That’s true. It also gives her nothing to act on. She had to decide what to build next.

To explain a technical concept to a non-technical stakeholder, start from their decision

Omar listed what the product manager could actually choose. First, the app could show when the status was last seen. The screen would read “On as of 2:10 pm.” That was about one sprint of app work. Second, the heater could get a cellular gateway, so the cloud always knew its state. That meant new hardware and a data plan. It would take months. Third, the team could leave the app alone and change the support script. Each option cost something different.

With the options listed, the explanation only had to make one fact clear. Away from the van, the phone can’t know the heater’s current state. Everything else about Bluetooth was irrelevant to her choice. In the interview, say the options out loud. They show you understood the stakeholder’s job before you explained yours. That’s the empathy signal the rubric describes.

A comparison that helps a non-technical stakeholder keeps the limitation inside it

A comparison helps only if it carries the constraint that drives the decision. “Bluetooth is like Wi-Fi for the heater” sounds friendly. It also suggests the app can reach the heater from anywhere. That is the exact misunderstanding behind the tickets. Omar used a walkie-talkie instead. In range, you hear the heater live. Out of range, you only remember the last thing you heard.

That comparison holds the one fact the product manager needed. It also made the second option easy to grasp, because the gateway gives the heater a phone line. In your answer, add one sentence on why you picked your comparison over the obvious one. It shows the choice was deliberate.

Check understanding by asking a question only understanding can answer

“Does that make sense?” invites a polite yes. Omar asked something else. “A user checks the app from a café a mile away. What should the screen say?” The product manager answered, “The last time we heard from it.” That reply is the evidence the interviewer wants. It also became the spec for the first option.

Then report what she chose and what changed. She picked the timestamp for the next release. The gateway went to the hardware team as a separate proposal. Heater-status tickets dropped in the month after release. Sometimes the stakeholder picks an option you wouldn’t have picked. Tell that version anyway. You still gave them what they needed to decide.

Omar’s heater-status answer, about ninety seconds long

Omar and the heater app are invented to show the structure. Keep the order and put your own project into it.

I worked on the Android app for a camper-van heater. The app talks to the heater over Bluetooth. Support started getting tickets from users who checked the app away from the van. It showed the heater as on. They came back to a cold van, because it had shut off on low battery.

Our product manager asked me to make the status accurate. Over Bluetooth, that wasn’t possible. The phone only hears the heater when it’s nearby. So I started with what she had to decide. I saw three options. We could show when the status was last seen. We could add a cellular gateway to the heater. Or we could leave the app and update the support script.

To explain the limit, I compared the connection to a walkie-talkie. In range, you hear the heater live. Out of range, you only remember the last thing you heard. I avoided a Wi-Fi comparison, because Wi-Fi suggests you can reach the heater from anywhere.

Then I asked her what the app should show a user in a café a mile away. Her answer was “the last time we heard from it.” That showed me she had it. It also became the spec.

She chose the timestamp for the next release. I shipped it in one sprint. The gateway went to the hardware team as a separate proposal. Heater-status tickets fell from about thirty a week to four in the month after release. Next time, I’d bring the three options written down. She asked me to send them afterward anyway.

Leave “I dumbed it down” out of the answer

Some phrasing costs points even inside a strong story. “I dumbed it down” and “she isn’t technical, so” both cast the listener as the problem. The empathy signal in the rubric points the other way. Say what you left out and why. Omar might say, “I dropped the connection details. She was choosing scope. Those details didn’t change that choice.” Treat the original request the same way. “Make the status accurate” was a fair ask from what the product manager knew. Describe it as a request you couldn’t meet as stated. Then move straight to the options you offered in its place.

Leave a Comment