---
title: What's something complex you've had to explain to someone non-technical?
description: Interview · Problem-Solving · Question 17
section: mind
tags: [interview, problem-solving]
genre: reference
stability: stable
lastUpdated: 2026-04-17
url: https://fardiniqbal.com/docs/mind/interview/problem-solving/whats-something-complex-youve-had-to-explain-to-someone-non-technical
---


Every day for the last several months.

My entire user base is non-technical. Therapists, BCBAs, agency administrators. They don't know what a database is. They don't care about my architecture. They care about whether the software makes their day harder or easier.

The most important translation I do is turning their frustrations into requirements without making them feel like they're being interrogated. When a therapist tells me "this screen is confusing," that's not a bug report. That's the beginning of a conversation. I ask what they were trying to do. I watch where their eyes go. I notice what they reach for that isn't there. Then I redesign the flow and show it to them and ask "is this what you meant?" Usually they say "yes, but also..." and the "but also" is where the real requirement lives.

When I had to explain the mastery detection engine to the clinical director, I didn't talk about TypeScript kernels or property-based testing. I said: "The system watches the trial data the same way you do, and when it sees the same pattern you'd see, it flags the child as ready to move forward. You set the rules. It does the watching." She understood immediately because I described the system in terms of her work, not mine.

The skill isn't simplification. It's translation. Respecting that the other person's expertise is as deep as yours, just in a different domain.