effects style and system designs across the game. This is a hands-on leadership role. Bringing both strong artistic instincts and a technical, process-driven mindset to this role you'll collaborate closely with art leade…
Engineering & IT · Raleigh, NC
Technical Writer jobs in Raleigh, NC
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.
28
Open roles today
$26–$62/hr
Typical pay range
$87k
Median, full-time
8
Fresh in this list
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.
01
Open technical writer roles
12 shown of 28 · sorted by freshness
About the Company: Founded in 2017 by Anthony and Joe Russo, AGBO is an artist-led independent studio shaping the future of film and television. The Russo Brothers and AGBO have generated more than $7 billion at the glob…
-class environment, character and concept artists who strive to innovate and inspire. What You'll Do Psyonix is searching for a Technical Animator with a passion for expressive character movement to work on Rocket League…
$140k - $165k
Salary: $140,000 - 165,000 per year Requirements: We need 6+ years of experience building and operating production backend services, with strong recent TypeScript/Node expertise. We expect solid API design judgment, incl…
need a hands-on Full Stack Engineer who loves building scalable systems , shipping high-quality product , and solving complex technical challenges that directly impact customers. You'll work across the full stack — from…
stay connected and serve as a true extension of our clients' teams. About the Role We're seeking a Senior or Principal Medical Writer to join our collaborative, high-performing team. In this role, you will serve as a lea…
requirements, in line with guidance provided Facilitate software application design discussions, and document design decisions to guide the technical team towards building software solutions Participate in coding and int…
$171.6k - $338.3k
closely with business, solution engineers, team members and leadership to understand business requirements and deliver high quality technical solutions Analyzing, implementing user requirements/business needs as new and/…
Develop, test, debug, and document software solutions across the full stack. - Translate business requirements into effective technical solutions. - Collaborate with project managers, team members, and stakeholders throu…
Job Summary (Senior UI/UX Developer NCDHHS Child Support Services) - Lead the transformation of a legacy mainframe Child Support system to a modern, web-based platform. - Design and implement responsive, accessible, and…
career. Visit or follow MMS on LinkedIn . This person will participate in the development, writing, and management of highly technical nonclinical documents. This is a full-time, remote position. Roles and Responsibiliti…
enhance user experience and collaboration. ~Work closely with cross-functional teams to gather requirements and translate them into technical specifications. ~Create project plan, and assign tasks from the requirement ga…
02
What technical writers earn in Raleigh
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $26–$36 | $54k–$74k |
| Mid level | $36–$48 | $74k–$99k |
| Senior | $47–$62 | $97k–$129k |
Adjusted for the Raleigh market from national ranges.
03
What employers ask for
The skills these listings keep naming
Clear, plain-language writingDocs-as-code (Markdown, Git)API documentation (OpenAPI)Information architectureInterviewing engineersStyle guides and consistencyBasic scripting or code readingDocs tooling (Docusaurus, etc.)Editing and review workflows
04
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.
05
Resume tips that move the needle
For technical writers specifically — generic advice costs you here
01
Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.
02
Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.
03
List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.
04
Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.
05
Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.
06
Where this role goes
Typical progression
01
Junior Technical Writer
02
Technical Writer
03
Senior Technical Writer
04
Documentation Manager
Ten quiet minutes a day
Applying for technical writer jobs in Raleigh?
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.