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…
Technical Writer jobs in Tampa, 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
12 shown of 15 · sorted by freshness
business analysts, test engineers, interoperability teams, and DevSecOps engineers. The role requires close collaboration across technical and clinical teams to deliver production-ready healthcare applications that integ…
MongoDB. We require proficiency with version control tools such as Git. We require experience producing and maintaining detailed technical documentation to support system accreditation and security compliance. We prefer…
followed.Collaborate & Mentor: Serve as an advisor and coach to other developers, sharing your expertise and fostering a culture of technical excellence and continuous improvement.Own Your Work: Operate with a limited le…
the data shows - Work with product and design to vet the product roadmap for your team’s product area and turn requirements into a technical plan and shippable increments - Write unit and end-to-end tests for the flows c…
familiarity with CI/CD tools such as GitHub Actions. We require strong communication skills and the ability to collaborate with technical and non-technical stakeholders. We prefer FastAPI experience. We prefer experience…
end server management. Begins to influence department’s strategy. Makes decisions on moderately complex to complex issues regarding technical approach for project components, and work is performed without direction. Exer…
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…
AUTOMOTIVE SERVICE WRITER Location: Tampa / Brandon / Lakeland, FL Area Pay: $600/Week + Uncapped Commission Schedule: Full-Time | Occasional Saturdays Benefits: Full Comprehensive Benefits Experience: Automotive Service…
objectives. The Content Developer / Editor will review articles and other written materials, provide editorial guidance, coach writers on content requirements and brand alignment, and conduct quality assessments of copy-…
additionalduties as assigned. Job Requirements The ideal candidate is an organized, creative professional with strong instructional design, technical writing, and project management skills. You should be comfortable mana…
Job Title: Fire Mitigation / Contents Project Manager Company Overview A leading restoration and mitigation company specializing in fire, smoke, and water damage recovery for residential, commercial, and industrial prope…
What technical writers earn in Tampa
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 Tampa 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 Tampa?
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.