tools. We collaborate with architects, engineers, product partners, and operations teams to turn business needs into high-quality technical solutions. We develop, test, deploy, and support application features and servic…
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
10 shown of 27 · sorted by freshness
usage, scalability, and enterprise integration. Responsibilities: We will rely on you to expand team impact through hands-on technical leadership, mentorship, and high engineering standards. You will build trust, share o…
Oracle. Responsibilities: We consult with internal business groups to deliver advanced application development support and technical assistance. We provide senior-level technical guidance to IT leadership and experienced…
Salary: $30,000 - 55,000 per year Requirements: We require a degree in Computer Science, Mathematics, AI, Data Science, or another quantitative discipline. We require 2-5 years of software development experience, with fi…
Confluence. ~ Strong analytical, problem-solving, and communication abilities, with the capability to work effectively with both technical and non-technical stakeholders. ~ Experience in root-cause analysis and incident…
maintain CI/CD pipelines and automate release processes with rollback strategies. Maintain and modernize applications, reduce technical debt, and improve coverage. Collaborate with stakeholders, gather requirements, and…
is a hands-on role involving full stack application development, APIs, microservices, AWS deployment, AI-assisted development, and technical mentoring. Key Responsibilities Develop applications using Java/Spring Boot, Py…
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…
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'…
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…
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.