Software Engineer to help us roll out the next generation of our graphic design editing platform. You will be working directly with our technical co-founder to help solve a wide variety of complex problems. You will also…
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
11 shown of 14 · sorted by freshness
preferred Bachelors degree in Computer Science, Computer Engineering, Technology, Information Systems, Engineering, or a related technical discipline, or equivalent experience or training At least 7 years of full softwar…
Salary: $60,000 - 90,000 per year Requirements: ~4+ years of software engineering experience, or equivalent experience gained through work, training, military service, or education ~4+ years of Java experience, with prof…
Job Description: In this contingent resource assignment, candidates may: ~Consult on complex initiatives with broad impact and large-scale planning for Software Engineering. ~Review and analyze complex multi-faceted, lar…
day-to-day job duties listed. Job Duties: The .NET C# Full Stack Web developer will perform the duties below: 1. Complete technical specifications and change documentation; 2. Develop and test Case Management System (CMS…
Experian is a global data and technology company, powering opportunities for people and businesses around the world. We operate across a range of markets, from financial services to healthcare, automotive, agribusiness,…
Have Skills (TOP 3 SKILLS) ReactJS (Lead role), AngularJS, HTML/HTML5, XML, DHTML CSS/CSS3 JD: We are seeking a highly technical Lead UI Developer with 10+ years of experience to drive the architecture, development, and…
stronger. For more information, visit or follow MMS on LinkedIn . Responsibilities Under minimal supervision, the Medical Writer will critically evaluate, analyze, and interpret the medical literature to select primary r…
The Graphic Designer & Digital Content Developer is responsible for creating compelling visual content and marketing assets that support brand awareness, demand generation, sales enablement, guest engagement, and busines…
About Us: We are a US-based real estate technology company offering AI-powered property intelligence, CRM tools, and marketing automation for real estate entrepreneurs. We are growing fast and building a brand that stand…
Motorsports Service Writer / Parts Associate Location: North Phoenix, AZ Job Type: Full-Time Compensation: Competitive (Based on... ...will act as the crucial bridge between our customers and our technical team. This dua…
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.