Engineering & IT · Albuquerque, NM

Technical Writer jobs in Albuquerque, NM

Technical writers turn complex products into documentation people can actually use — API references, user guides, and internal docs — working closely with engineers to get the details right.

3
Open roles today
$25–$58/hr
Typical pay range
$81k
Median, full-time
2
Fresh in this list

No email, no resume, no sign-up. Save any listing below and you start anonymously.

You're signed in. Saving a listing drops it straight into your pipeline.

01

Open technical writer roles

3 shown · sorted by freshness

Social Media Content Coordinator

Southwest Womens Oncology/Optimum · Albuquerque, NM

Job Description Job Description Social Media & Content CoordinatorOptimum Human + Southwest Women's Oncology | Albuquerque, New Mexico Why This Role MattersFor most people, social media is where they first encounter who…

Posted 4d ago
+ Save to tracker View listing

Technical Writer

Stellar Science · Albuquerque, NM · Full-time

develops custom software products and performs research and development in multiple high-tech domains. We are seeking a talented technical writer to write and edit technical reports, technical proposals, and software use…

Posted 6d ago
+ Save to tracker View listing

Part-Time Grant Writer

Catholic Charities Of Central New Mexico · Albuquerque, NM · Full-time

The Part-Time Grant Writer supports Catholic Charities' Development team by researching, writing, and submitting grant proposals to foundation and corporate funders. The position focuses primarily on smaller foundation g…

Posted 4w ago
+ Save to tracker View listing
02

What technical writers earn in Albuquerque

Hourly first — that's how the offer arrives

ExperienceHourlyAnnual, full-time
Entry level $25–$34 $51k–$70k
Mid level $34–$45 $70k–$93k
Senior $44–$58 $91k–$121k

Adjusted for the Albuquerque market from national ranges.

03

What employers ask for

The skills these listings keep naming

Clear, plain-language writingDocs-as-code (Markdown, Git)API documentation (OpenAPI)Information architectureInterviewing engineersStyle guides and consistencyBasic scripting or code readingDocs tooling (Docusaurus, etc.)Editing and review workflows
04

Interview questions worth rehearsing

With the thing the interviewer is actually listening for

Walk me through your process for documenting a feature you know nothing about.

Show the sequence: use the product yourself, interview the engineers, draft, and validate with real users or support tickets. Trying the product firsthand is the key beat.

How do you decide what not to include in documentation?

Anchor on audience and task: what does this reader need to succeed right now. Cutting is the craft — show you treat concision as a feature.

An engineer gives you inaccurate or incomplete information. How do you handle it?

Verify against the product, ask precise follow-ups, and build review loops into your process. Show persistence without friction.

How do you keep documentation from going stale?

Talk about docs-as-code tied to release workflows, ownership models, feedback channels, and auditing high-traffic pages. Staleness is the industry's chronic disease — show a system.

How do you measure whether documentation is working?

Page analytics, search terms, support-ticket deflection, and user feedback. Connecting docs to reduced support load is the strongest business case.

Tell me about a doc set you restructured. What drove the changes?

Describe the user problem — findability, task mismatch — and the information architecture you moved to. Evidence of user thinking beats aesthetic preference.

05

Resume tips that move the needle

For technical writers specifically — generic advice costs you here

01

Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.

02

Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.

03

List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.

04

Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.

05

Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.

06

Where this role goes

Typical progression

01 Junior Technical Writer
02 Technical Writer
03 Senior Technical Writer
04 Documentation Manager
Ten quiet minutes a day

Applying for technical writer jobs in Albuquerque?

Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.

Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.

Start with this search No email, no resume, no sign-up. Open your tracker Everything you saved is already there.
3 Technical Writer roles in Albuquerque Save them into one pipeline Save them into your pipeline
Start free My tracker