bring intelligence wherever it's needed and help shape the next generation of computing. Efficient Computer is seeking a Technical Content Writer who enjoys figuring out how things work and helping other people understan…
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
9 shown of 29 · sorted by freshness
Job Description Skill: UI Developer Technical Stack: Proficiency in HTML5, CSS3/SASS/LESS, and modern JavaScript (ES6+). Frameworks: Experience with front-end frameworks like ReactJS, Angular, or VueJS, along with TypeSc…
About Us: Based in San Francisco California Turing is the worlds leading research accelerator for frontier AI labs and a trusted partner for global enterprises deploying advanced AI systems. Turing supports customers in…
Dallas TX; or Birmingham AL. CGI is seeking an experienced Full Stack Java Software Developer at the Expert level to provide technical leadership in the design development modernization and delivery of complex enterprise…
integrated with enterprise systems Collaborate with developers across teams to deliver full-stack solutions Participate in technical design discussions, code reviews, and architecture planning Create technical designs an…
transportation design. We're looking for a Marketing and Communications Writer to join our Pittsburgh, PA team-someone who loves finding the... ...Working HereWe are an employee-owned, purpose-driven team of technical ex…
is growing, and we are looking to hire a full-time R&D, Medical Writer working from our Pittsburgh, PA @ Nova Place office location,... ...for other purposes, such as following up on an application or technical issues no…
and LLM capabilities. Develop automated tests and follow TDD practices. Troubleshoot cloud and application issues. Lead technical initiatives and mentor junior engineers. Must-Have Skills ~5+ years developing/supporting…
environment automation. . Identify and remediate application vulnerabilities, outdated dependencies, code quality issues, and technical debt. . Develop automated unit, integration, API, and UI tests using tools such as J…
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.