This role requires the ability to work lawfully in the U.S. without employment-based immigration sponsorship, now or in the future.Step into a role where you design, develop and elevate employee training programs at Spec…
Engineering & IT · Charlotte, NC
Technical Writer jobs in Charlotte, 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.
31
Open roles today
$26–$61/hr
Typical pay range
$86k
Median, full-time
11
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 31 · sorted by freshness
Canopy Service Partners is seeking a creative and strategic Brand Reputation & Content Manager to elevate the presence of our company and its Partner brands across digital channels and local markets. In this pivotal role…
$96.8k - $145.2k
Explore and apply AI/GenAI capabilities to improve application development, testing, documentation, and developer productivity.Create technical documentation and support deployment and production activities.Basic Qualifi…
Job Title: Web Application Firewall Engineer (Akamai/F5) Location: Charlotte, NC Hire Type: Full time Must Have Technical/ Functional Skills: Minimum 8 years knowledge and experience with deployment and maintenance of en…
$100k - $120k
to $120K Plus Client Benefits Location:- Stamford, CT Onsite Job Type:- Full Time Hiring Must Have Technical/ Functional Skills 5+ years of professional experience in UX/UI design, front-end engineering, or full-stack ap…
Playwright Tester Employment Type: Full Time (Onsite) Experience: 6 - 8 years Location: Charlotte, NC Must Have Technical/ Functional Skills Java; JavaScript ,Selenium; Cucumber; Jmeter, playwright Roles & Responsibiliti…
$65 per hour
*For this role you MUST interview oniste*SkillsJava, Angular, Microservices, Spring, Rest, J2EEJob Type & LocationThis is a Contract position based out of Charlotte, NC.Pay and BenefitsThe pay range for this position is…
$159k - $254k
operational efficiency, and delivering technology solutions that help our clients and businesses navigate dynamic market environments. As a technical leader, you'll influence architecture, mentor engineers, and contribut…
$98k - $102k
Job Type : Fulltime Salary Range : $98,000-$102,000 a year + fulltime benefits Job Summary Must Have Technical/ Functional Skills 5+ years of professional experience in UX/UI design, front-end engineering, or full-stack…
$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/…
tested code (unit tests), and help define and raise the team's engineering standards Produce clear documentation and communicate technical decisions effectively Collaborate effectively, take ownership, and work independe…
Job Title: Frontend Web Developer II Location: HYBRID in Cincinnati, Charlotte, or Chicago TOP SKILLS: Must Have CCS and HTML hands on experience Knowledge of AEM and web pages development Mobile/Web Development What You…
02
What technical writers earn in Charlotte
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $26–$36 | $54k–$74k |
| Mid level | $36–$47 | $74k–$98k |
| Senior | $46–$61 | $96k–$127k |
Adjusted for the Charlotte 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 Charlotte?
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.