# 017: Dear Tech Writers, Your Resume Sucks
¡Hola, Tech Writing Friends!
You can’t get a tech writing job without a GOOD resume.
But what the heck is a “GOOD” resume?
I’m glad you asked!
Let me show you how to write a tech writer resume that actually gets you that recruiter callback.
What’s the Big Resume Problem?
Most resumes for tech writers fail because they…
List responsibilities, not impact.
Saying “Wrote tutorials and guides” tells hiring managers nada about your value.
Are too vague.
“Created technical content” doesn’t tell us what you wrote, who it was for, or why it mattered (Did it, btw? Do you have the data to prove its impact?).
Miss important keywords.
If recruiters don’t see tools, methodologies, and programming languages in your resume, you won’t even show up in LinkedIn search results.
How Most Tech Writers Fruit It Up
Most tech writers default to pretty generic bullet points that do not quantify their contributions nor accurately portray their value/impact:
🔹 “Wrote API documentation, guides, and tutorials for COOL PRODUCT NAME.”
🔹 “ Owned release notes and partnered with product management.”
🔹 “Teamed with engineers and product managers in delivering documentation.”
Sure, these are true.
But do they stand out?
You think the recruiter or anyone on the hiring team will be impressed?
Nope. 🍉🍌🍍
How to Fix It: Your Top Secret Resume Formula
The best resumes use a simple 3-part formula:
[Action] + [Impact] + [Tools/Methods Used]
Compare these weak vs. strong bullet points:
🚫 “Wrote API documentation.”
✅ “Designed API documentation strategy for Spec 3.0, reducing onboarding time by 20% by creating detailed migration guides and tutorials.”
🚫 “Worked with engineers.”
✅ “Collaborated with 5 engineers and 1 product manager to rewrite developer docs, aligning content with user needs and reducing support tickets.”
🚫 “Maintained documentation.”
✅ “Led a docs revamp for a cloud-based SaaS platform, implementing Docs-as-Code workflows to streamline versioning and collaboration.”
See the difference?
Numbers, impact, and tools matter.
MUST-HAVE Sections in Your Resume
Contact Info & Online Presence
Your name, email, location, GitHub, LinkedIn—make sure they’re at the top!
Technical Skills
Tech Writing hiring managers look for:
Languages & Frameworks: (Ex: JavaScript, REST, Markdown)
Tools & Platforms: (Ex: GitHub, Postman, Swagger, AWS, Kubernetes)
Methodologies: (Ex: Docs-as-Code, API documentation, DevRel content)
Experience
Reverse chronological order (most recent job first).
Each role should include:
Company + location + dates
Your title (Make sure it matches what’s on LinkedIn!)
3 bullet points using the [Action] + [Impact] + [Tools] formula
I know keeping it to 3 bullet points sounds impossible, but it forces you to highlight your best accomplishments.
Plus, recruiters don’t have time to read a 100+ items list—keeping it SHOOOOORT works in your favor.
That said… I may have broken my own rule in my latest resume that landed me an amazing job. One of my job experiences has 4 bullet points.
But guess what? You didn’t catch me—I told you first! 😈
Projects (Optional, but Highly Recommended)
Have an open-source contribution, blog, or personal project? List it!
Certifications & Languages (If Relevant)
List certifications (AWS, Google Cloud, etc.) and any languages spoken (English, Spanish, etc.).
🎯 Your Next Action Steps
1️⃣ Rewrite 3 bullet points on your resume using the [Action] + [Impact] + [Tools] formula.
2️⃣ Add a “Tech Stack” section that includes the tools, frameworks, and methodologies you know.
3️⃣ Optimize for recruiter searches—ensure your resume includes keywords relevant to your target job.
📢 Bonus: My Own Badass Resume for Inspiration
I rewrote my own resume using this approach, and it helped me land a six-figure role with a super cool Swiss startup just this year.
Happy resume rewriting! You got this. 😎
Hasta luego,
Quetzalli
