How to Correctly Respond to "What Do You Do?" as a Software Engineer
As a software engineer, getting asked, “What do you do?” at social gatherings is almost inevitable. While it might seem like an easy question, the reality is more complicated. The wrong answer can lead to endless tech support requests or awkward silences when people don’t understand what you’re talking about. Over time, I’ve found a few strategies that help me navigate this question depending on my mood and the audience.
Strategy 1: Keep It Simple
Sometimes, you just don’t want to explain your job in detail. Maybe you’re tired or simply don’t want to risk becoming the group’s IT person. In these cases, I keep my answer vague and noncommittal:
- “I work with computers.”
- “I build websites.”
These responses are simple and unlikely to spark follow-up questions. They let you move on without being rude or dismissive.
Strategy 2: Using Humor to Deflect
Humor is my favorite go-to when I want to avoid a serious discussion but still keep the tone light. Some of my favorite lines include:
- “I smash my face into a keyboard, and magic happens.”
- “I make computers go brrrr.”
- “I write beep-boop code.”
These answers are short, funny, and signal that I’m not looking for a deep dive into the specifics of my work. Plus, they often get a laugh, which is a nice bonus.
Strategy 3: When You’re in the Mood to Engage
If I feel like having a real conversation, I try to focus on the outcome of my work rather than the technical details. Instead of saying, “I’m a software engineer,” I’ll frame it in a way that connects to something people understand:
- “I build tools that help companies ship products faster.”
- “I work on software that powers logistics systems.”
- “I solve problems for [specific industry].”
People are much more interested in what you accomplish than how you accomplish it. This approach makes your job feel relevant and relatable, which can lead to a meaningful discussion.
Why It’s Not Always Worth Explaining
At the end of the day, how you respond depends entirely on your mood and the context of the gathering. If I’m not feeling it, I give a vague or funny answer and move on. If I’m in the mood to share, I focus on making my work relatable.
What I’ve learned is this: You don’t owe anyone a detailed explanation of your job, especially if it feels draining. A lighthearted or simple response is usually all it takes to navigate the question without turning into the tech support guy or boring the room. Social gatherings are for fun and connection—not for explaining APIs or debugging someone’s laptop!
What’s your go-to response when someone asks what you do? Share your thoughts!