newsletter lands in inboxes every week — and it needs to be the kind of email people actually look forward to opening. As our Newsletter Writer, you'll research, write, and produce a weekly newsletter that keeps our audi…
Technical Writer jobs in Jacksonville, FL
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
11 shown of 14 · sorted by freshness
ABOUT NOGIGIDDY NoGigiddy is a digital platform built for gig workers, side hustlers, and anyone building an income outside the traditional 9-to-5. We connect our community with real earning opportunities - remote jobs,…
existed, and we hire people who actually get it. THE ROLE Words drive traffic — and traffic drives everything. As an SEO Content Writer at NoGigiddy, you'll create articles, guides, and landing pages that rank on Google…
and AI providers.We’re looking for an exceptional backend engineer who wants substantial ownership of that system: someone with the technical depth to solve difficult problems, the drive to move quickly, and the discipli…
in the Southeast! We are currently seeking a Specifications Writer to join one of our 12 offices. The Specifications Writer is responsible... ...for developing, coordinating, and maintaining the written technical require…
product managers, designers, and developers to translate complex requirements into intuitive web solutions. Additionally, a robust technical foundation in JavaScript, HTML, CSS, and contemporary frameworks like React, co…
assistance Collaborate with cross-functional teams to understand requirements and deliver solutions Troubleshoot, debug, and resolve technical issues in both backend and frontend systems, using AI-assisted tools to diagn…
Position: Senior Technical Writer / Editor (FEMA PA) Position Code : TECH-WR Employment Type: Non-Exempt Hourly Temporary Project-Funded W-2 (contingent on task-order award) Location Nationwide (remote). Reports To PSCG…
content, email copy, and other campaign content that reflects our brand and connects with our audiences. Partnering with our staff writer and video team to develop and optimize content for traditional search and AI-drive…
keyword research, and content analysis. They will work closely with website production teams and key stakeholders to communicate technical details and explain tactics and execution as well as clarify, interpret, and impl…
stability, security, and ongoing operation of enterprise web hosting and application infrastructure environments. This is a hands-on technical role focused on web hosting platforms, vulnerability remediation, application…
What technical writers earn in Jacksonville
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$34 | $52k–$70k |
| Mid level | $34–$45 | $70k–$94k |
| Senior | $44–$59 | $92k–$122k |
Adjusted for the Jacksonville 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 Jacksonville?
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.