How to Explain Your Job to Your Family at Thanksgiving (Without Glazing Anyone Over)
Your aunt asked what you do for a living. Your usual answer is too vague or too technical. Here's how to land a version that actually means something.
It's the third time this year you've been asked. Your aunt leans across the green beans: 'so what is it you do again?' You try the short version — 'product manager' or 'data engineer' or 'senior solutions architect' — and watch her smile politely while clearly not knowing what that means. You try the long version, get four sentences in, and lose her. By the end of the conversation, the family consensus is something vague involving computers.
Explaining your job at a family dinner is a different problem from explaining it at a job interview. The audience doesn't care about your skills or your impact metrics. They want to know what you actually do all day, and whether they'd recognize it if they saw it. Here's how to land a version that does the work in two sentences.
Skip the title and lead with the verb
'I'm a product manager' tells your aunt nothing. 'I'm the person who decides which features get built next' tells her something. Drop the title and replace it with a single verb-phrase that names what you do. Build, fix, decide, write, sell, design, teach. The title was always shorthand; for non-industry audiences the shorthand is just opaque.
Anchor it to something they can picture
Pick something they already use or have used. 'You know that little box on Amazon that suggests other things to buy? Someone like me decides what goes in it.' 'You know how Netflix shows you a different home page than Dad does? My team builds the part that figures out what to show you.' The anchor turns the abstraction into something they've literally seen with their own eyes.
Pick the part of the job they'd actually find interesting
You probably do twenty things. Pick the one that has a story attached. The time the system went down at 3 a.m. The argument you won about the redesign. The reason your industry uses a weird word for something normal. Family conversations are powered by stories, not job descriptions. The story is what they'll repeat to someone else next week.
Name one thing that's harder than they think
Every job has a part that looks easy from outside and is hard inside. Naming it earns respect without bragging. 'Most people think the hard part is writing the code. The hard part is actually figuring out what code to write.' 'Everyone assumes you just send the email. The hard part is figuring out which 200 people on the list actually shouldn't get it.' This is where the conversation gets interesting.
End with a question, not a monologue
After two minutes of you, hand the conversation back. 'What about you — do you ever talk to a chatbot when you call customer service? That's the kind of thing my team works on.' 'You're a teacher — do you guys actually use any of this AI stuff in the classroom yet?' The exit move turns it into a real conversation instead of a presentation, which is what they wanted in the first place.
Get the right way to describe your job, for any audience
Analogy Engine takes your actual work and the person you're talking to — and writes the version that lands. Family dinners, dating profiles, elevator pitches.