across all client accounts with high-quality standards and volume requirements. This role specializes in one primary area of SEO ( technical, local, on-page, or auditing) and contributes to elevating this specialty acros…
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.
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 42 · sorted by freshness
An innovative AI startup is seeking a backend or backend leaning fullstack engineer for a 100% remote role. The position requires 4-8 years of experience, with a strong preference for candidates proficient in Golang. Exp…
development teams to implement secure coding practices and resolve application security vulnerabilities. Create, maintain, and update technical documentation, operational procedures, architecture diagrams, and security s…
Job Description Job Description Position: Digital Content CoordinatorStatus: Part-Time, 20-25 hours per weekReports To: Director of CommunicationsSalary: $20-$25 per hourAnticipated Start: August 2026ABOUT ARTS+Founded i…
job summary: We are seeking a Frontend-Focused Full Stack Engineer with deep expertise in modern JavaScript frameworks. While this position involves backend and cloud integration using Node.js and AWS, your primary focus…
Title: Senior Full Stack Developer Location: Charlotte, NC(Onsite) Fulltime Job Description Must Have Technical/ Functional Skills Experience in full stack development with TypeScript and Go Strong on React + TypeScript…
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…
Job Description Job Description Front-End GraphQL Developer Location: Charlotte, NC (Hybrid schedule with 3 days in office and 2 days WFH) Interview Process: Phone screen, Teams meeting and final is an In-person intervie…
performance is essential. The ideal candidate can translate macro-level business and platform requirements into clear, actionable technical designs and deliverables, producing robust and maintainable solutions. qualifica…
Developer is responsible for creating deliverables (such as video, podcasts, graphics, etc.). Responsibilities include the design and technical aspect of creating the deliverables. To be successful as a Digital Content D…
Job Description Job Description Benefits: ~ Health insurance ~ Vision insurance ~401(k) ~ Company car ~ Competitive salary ~ Dental insurance Who We Are: We are SERVPRO of Northwest Charlotte. We are part of a team that…
Job Description Job Description Job Summary We are seeking an experienced Full Stack MERN Developer to design, develop, and support scalable web applications and microservices. The ideal candidate will have strong expert…
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.
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 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.