integration patterns to support business requirements. Gather requirements from business stakeholders and translate them into scalable technical solutions. Maintain technical documentation and provide user training and o…
Technical Writer jobs in Pittsburgh, PA
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 30 · sorted by freshness
financial services, healthcare, or other regulated industries Understanding of: Information governance Records management Compliance requirements Strong communication skills and ability to work with both technical and no…
Senior Angular UI Developer to design, develop, maintain, and support enterprise web applications. The candidate will work with technical leads, business analysts, QA teams, architects, and other developers to deliver hi…
deploy applications on Microsoft Azure using modern DevOps practices . Participate in architecture reviews, code reviews, and technical design discussions Required qualifications to be successful in this role . Bachelor'…
making an impact with visionary brands. We help clients see the possibilities in their challenges and deliver the right creative and technical solutions to realize them. What Are We Looking For? We’re looking for an expe…
UPMC is hiring a Casual Scribe/Ophthalmic Writer to join their Department of Pediatric Ophthalmology at UPMC Children's Hospital! The Division of Pediatric Ophthalmology, Strabismus, and Adult Motility at UPMC Children’s…
the end-to-end development and maintenance of critical applications that power our client’s businesses. This role combines hands-on technical leadership with delivery execution, platform resiliency, team development, and…
(Beginning August 3, 2026) Overview We are seeking a detail-oriented Specification Writer to support the Engineering Department by assisting with a backlog of technical specification work. This temporary assignment plays…
Job Description Job Description Description: Hybrid 4 days onsite in Pittsburgh, PA Our client seeks a high-impact senior full-stack engineer to drive stability, quality, and delivery in a risk-sensitive environment. You…
migrations, and production troubleshooting . Collaborate with architects and business analysts to translate requirements into technical solutions . Mentor junior developers and contribute to development standards and bes…
Passing on relevant information to those responsible for the project Reporting of document management status Assembling technical data for customer operations manual Collaborating with Project management, Engineering, an…
oriented Senior Backend Engineer who thrives in complex environments and can deliver immediate impact. This individual blends deep technical expertise with strong business acumen, operates autonomously, and partners effe…
What technical writers earn in Pittsburgh
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$35 | $53k–$73k |
| Mid level | $35–$47 | $73k–$97k |
| Senior | $46–$61 | $95k–$126k |
Adjusted for the Pittsburgh 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 Pittsburgh?
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.