# 018: Tech Writing Interview Traps: How You Nail Them
¡Hola, Tech Writing Friends!
Tech writing interviews can be a trap door because the question they ask isn’t the one you actually need to answer.
If that sounds confusing to you, it's because it is.
If you think that’s ridiculous, it's because it really is.
I don't make the rules, folks, I just try to explain them to ya.
So today, I’m breaking down two common tech writing interview questions.
What they ACTUALLY mean + how to craft the perfect response.
(And if you like this, let me know—I’d be happy to cover more interview questions in a future issue!)
Question 1: "Tell me about yourself."
What they ACTUALLY mean…
Can you highlight your expertise for this role without rambling?
Are you genuinely excited about this specific role?
What have you owned or led that directly relates to this role?
How To Answer It
Think of your answer as a three-part story:
Your relevant background in one sentence (what you do, how long, and where)
Your key skills and passion (how they align with the job)
Why you’re a great fit (specific achievements owning projects in this area)
Sample answer:
"I'm a technical writer with a decade of experience in API documentation and developer education. My current role at Cool Tech Co. involves creating event-driven API docs, troubleshooting guides, and developer onboarding materials.
"I love making technical concepts easier to grasp, and I thrive in cross-functional collaboration with engineers and product teams. At AsyncAPI, I overhauled the entire documentation structure, making it more accessible to users. At AWS, I helped improve the onboarding experience for new cloud users."
"I’m excited about this opportunity because it aligns perfectly with my experience in API documentation and my passion for developer success."
Why This Works
It’s concise.
You don’t bore them with your entire work history.
It’s structured.
They get a specific picture of your skills and value.
It’s relevant.
You focus on what matters to them.
Question 2: "What are you building?"
What they ACTUALLY mean…
Are you someone who takes initiative?
Do you create value beyond your job description?
Are you growing your skills?
How To Answer It
Redefine "building"
It doesn’t have to be code! Writing documentation, creating style guides, or improving workflows all count.
Pick a relevant project
Talk about something that showcases your skills and problem-solving mindset.
Highlight value
How does this project solve a problem?
Sample answer:
"When people think of ‘building,’ they often picture software, but building also means creating resources that help others. Right now, I’m building the '6-Figure Tech Writer Resource Hub'—a collection of templates, guides, and code examples to help tech writers level up their careers."
"I started this because I noticed a lack of structured learning resources for tech writers. It’s helped many writers improve their documentation skills and job search strategies. This directly connects to this role, where I'd be responsible for creating resources that empower customers and developers."
Why this works
It shows initiative.
You’re actively growing your expertise.
It proves impact.
You’re not just building for yourself—you’re solving a real problem in your niche and creating value for others.
It aligns with the job.
You’re already doing work similar to what they need.
Want More Tech Writing Interview Answers?
If you found this helpful, let me know!
I’ll cover more interview questions (like "How do you handle feedback?" and "How do you align with stakeholders who disagree?") in a future issue.
Hasta luego,
Quetzalli
