Use the Anchor-and-Twist method: connect what you do to something your listener already understands (the anchor), then add your specific twist. 'It's like Google Maps but for inside buildings' beats 'I work on indoor positioning systems using BLE beacons.' Focus on the problem you solve, not the technology you use. If their eyes glaze over, you went too deep.
"So, what do you do?"
Five words. Guaranteed to appear at every party, dinner, networking event, and awkward elevator encounter. And for most analytical people, it triggers an internal crisis: Do I give the simple version and feel like I'm dumbing it down? Do I give the real version and watch their eyes glaze over? Do I just say my job title and hope they don't ask follow-up questions?
None of these options feel great. But there's a better way — and it works whether you're talking to your neighbor, a date, or someone at a conference. (And if the conversation itself feels like a struggle, start with our guide on having better conversations.)
Why This Question Is So Hard for Analytical People
There's a cognitive trap called the Curse of Knowledge. Once you deeply understand something complex, it becomes nearly impossible to remember what it was like to not understand it. You forget which parts are jargon. You forget which concepts require background knowledge. You forget that "microservices architecture" means absolutely nothing to 99% of people.
The result: you either over-explain (losing your listener in technical details they didn't ask for) or under-explain (giving a vague job title that invites no further conversation).
The fix is learning to translate — not dumb down. You're not making your work less impressive. You're making it accessible.
If you feel like you're "dumbing it down," reframe it: you're translating. A French person explaining their work in English isn't dumbing it down — they're making it understandable. Same thing.
The Impact-First Approach
Instead of explaining what you do (process), explain what it accomplishes (impact). This single shift makes everything easier.
"I'm a backend engineer who works on distributed database systems" → "I make sure the app doesn't crash when millions of people use it at the same time."
"I'm a UX researcher" → "I figure out why people get frustrated using software, and then I help fix it."
"I do DevOps" → "I'm the person who makes sure the website stays online and loads fast."
Notice what's happening: you're describing the problem you solve, not the technology you use. Problems are universal. Technology is niche. Lead with the problem.
The Anchor-and-Twist Method
When you need to explain something genuinely complex, use the Anchor-and-Twist. It's the single best technique for making abstract concepts concrete.
Step 1 — The Anchor: Find something your listener already understands perfectly. Common anchors include popular apps, everyday objects, or universal experiences.
Step 2 — The Twist: Add the specific differentiator that makes your work unique.
"You know how Google Maps gives you directions on the street? I build the same kind of system, but for navigating inside large buildings." (indoor positioning engineer)
"It's like a spell-checker, but for security vulnerabilities in code." (static analysis developer)
"Think of it like a traffic cop for the internet — I make sure data goes where it's supposed to go without getting jammed up." (network engineer)
The anchor does 90% of the heavy lifting. It instantly uploads a massive amount of context into the listener's brain. The twist narrows it to your specific world.
Someone asks a machine learning engineer what they do. ❌ "I work on supervised learning models using gradient-boosted decision trees for predictive analytics." ✅ "You know how Netflix recommends shows you might like? I build systems like that, but for predicting which customers might cancel their subscription." Same job. Completely different level of engagement.
The Curiosity Test — Let Them Pull the Thread
Here's the golden rule: give one sentence. Then stop.
If your listener is genuinely interested, they'll ask a follow-up question: "Oh, how does that work?" or "That sounds cool — what does that look like day-to-day?" Now you have permission to go one level deeper.
If they nod politely and say "Oh, cool" — take the hint. They're not rude; they just don't need more detail. Change the subject or ask them about their work.
Think of it like a conversation elevator. Start at the lobby (impact). If they press the button, take them to the second floor (how it works, broadly). If they press again, go to the third floor (interesting details). Never take someone to the penthouse (full technical deep dive) unless they've been pressing buttons the whole way up.
Common Traps to Avoid
The jargon reflex: You say "API" or "containerization" or "sprint retrospective" without noticing. These words are invisible to you because you hear them daily. They're opaque to everyone else.
The disclaimer trap: "Well, it's kind of hard to explain, but basically..." This signals low confidence and makes the listener expect confusion. Just explain it simply and confidently.
The feature dump: Instead of saying one interesting thing about your work, you list twelve components of what you do. Your listener isn't building a mental model — they're drowning.
The modesty trap: "Oh, I just do [impressive thing], it's not that interesting." If you diminish your own work, people will take your word for it. Own what you do. It's genuinely interesting to someone who's never heard of it.
Your Action Step
Right now, write down what you do using this formula: "I help [who] [do what / solve what problem]." Keep it to one sentence. Then practice saying it out loud twice. The next time someone asks "What do you do?", use this version instead of your job title.
If you want to take it further, prepare one Anchor-and-Twist analogy for the most complex part of your work. When someone asks a follow-up, you'll be ready. These same translation skills work at the office too — check out speaking up at work for applying them in meetings. And if networking events are where you struggle most, check out our guide on how to network without draining your battery. Browse more conversation skills guides.
Frequently Asked Questions
How do I answer 'What do you do?' without boring people?
Focus on the problem you solve, not your tools or job title. 'I help companies figure out why their customers are leaving' beats 'I'm a data analyst specializing in churn prediction models.' If they want more detail, they'll ask.
What if what I do is genuinely hard to explain?
Use the Anchor-and-Twist: find something familiar to anchor to, then add your specific twist. 'You know how Netflix recommends shows? I build systems like that, but for [your industry].' The anchor does 90% of the explanation for you.
How much detail should I give when someone asks about my work?
Start with one sentence about the impact. If they lean in and ask questions, share more. If they nod politely, change the subject. Let their curiosity be your guide — never give the full technical breakdown unprompted.
Why do people's eyes glaze over when I talk about my job?
You're probably explaining how things work instead of what they accomplish. Nobody outside your field cares about the architecture or the tech stack. They care about the outcome. Swap process for impact and watch the difference.
Communication for Nerds
Practical communication guides for analytical minds. We help introverts, engineers, gamers, and deep thinkers build real social skills — with clear frameworks, honest advice, and zero manipulation.
