Job Description Company Overview Our client is building a new class of modular power systems that deliver reliable, low-cost energy anywhere it's needed. The platform starts with a proprietary high-efficiency generator c…
Technical Writer jobs in Phoenix, AZ
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.
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.
Open technical writer roles
12 shown of 20 · sorted by freshness
newsletter lands in inboxes every week — and it needs to be the kind of email people actually look forward to opening. As our Newsletter Writer, you'll research, write, and produce a weekly newsletter that keeps our audi…
concepts, campaign themes, headlines, taglines, and messaging that bring the PrePass brand to life. Partner with designers and fellow writers to create integrated campaigns that combine visual storytelling and persuasive…
performance reports at least 24 hours before scheduled calls Translate campaign data into clear, actionable recommendations for non- technical clients Build strong client relationships that support retention, renewals, a…
\n Job Description: \n PURPOSE OF THE JOB \n Partners with subject matter experts to rapidly design, develop and deploy technical learning content for healthplan operations end-users and business partners. Ultilizes new…
existed, and we hire people who actually get it. THE ROLE Words drive traffic — and traffic drives everything. As an SEO Content Writer at NoGigiddy, you'll create articles, guides, and landing pages that rank on Google…
ABOUT NOGIGIDDY NoGigiddy is a digital platform built for gig workers, side hustlers, and anyone building an income outside the traditional 9-to-5. We connect our community with real earning opportunities — remote jobs,…
analytical, research, critical thinking, time management, and verbal and written communication skills. Experience mentoring others in technical matters. Interest in public service and improving State government. Benefits…
: Title: :Full Stack Developers: @ Phoenix, AZTerms of Hire: 12 months & Extendable :Hourly rate: Open /hr.:Detailed Requirements::Our client is the world's leading business partner for managed travel. Offers its custome…
Where Youll Work Join a Legacy of Healing at Saint Josephs Hospital and Medical Center (SJHMC) Ready to make a real difference Join SJHMC in Phoenix AZ. a 571-bed nonprofit founded by the Sisters of Mercy over 125 years…
as a member of a team and applying consensus decision making techniques; Making effective oral presentations clearly conveying technical information to non-technical audiences; Organizing tasks and working independently…
Description Copywriter (Midlevel) Phoenix AZ Full-Time Everyone creative The people we are looking for are curious and ambitious and they hold high standards for everything they make. Theyre comfortable being uncomfortab…
What technical writers earn in Phoenix
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $27–$37 | $56k–$76k |
| Mid level | $37–$49 | $76k–$102k |
| Senior | $48–$64 | $100k–$133k |
Adjusted for the Phoenix market from national ranges.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For technical writers specifically — generic advice costs you here
Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.
Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.
List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.
Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.
Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.
Where this role goes
Typical progression
Applying for technical writer jobs in Phoenix?
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.