CI/CD tools such as Jenkins and GitLab CI. Responsibilities: We execute standard software solution design, development, and technical troubleshooting. We write secure, high-quality code in at least one programming langua…
Technical Writer jobs in Columbus, OH
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 29 · sorted by freshness
Responsibilities Research emerging threats and threat intelligence to develop new SIEM threat-detection use cases. Collaborate with stakeholders, cybersecurity tool SMEs, and Threat Detection Analysts to identify analyti…
agile practices, including CI/CD, application resiliency, and security. We are seeking knowledge of software applications and technical processes in a discipline such as cloud, artificial intelligence, machine learning,…
Java to contribute to continual, iterative improvements for product teams. ~Execute software solutions, design, development, and technical troubleshooting. ~Creates secure and high-quality production code and maintains a…
Full Stack Developer All IT Solutions United States · Columbus, Ohio Workplace Type — On-site Employment Type — Contract We are currently seeking a qualified Full Stack Developer to support this engagement. Please review…
agent frameworks. Partner with product, architecture, and engineering teams to deliver innovative AI capabilities. Drive technical excellence, scalability, security, and performance across solutions. Rapidly prototype an…
production scale. About the Role We're looking for a Senior Full Stack Developer to join our Engineering team as a hands-on technical leader. This person will own significant backend and frontend work, lead the system de…
SDET - Playwright Location: Columbus, OH (Onsite) Role Overview We are seeking a Software Development Engineer in Test (SDET) to design, build, and maintain reliable, scalable test automation for a ServiceNow Platform. T…
resource utilization. Implement testing, monitoring, logging, and CI/CD pipelines. Collaborate with engineering teams and maintain technical documentation. Required Qualifications ~5+ years of software engineering experi…
Job Description Join a team where your ideas shape how people learn, grow, and succeed. You’ll build modern, practical training that helps employees perform at their best from day one. As an Instructional Designer in Cha…
Responsibilities: Works closely with key personnel and participates in technical training to develop expert level understanding of assays,... ...using analytical skills and judgement, conferring with other writers and SM…
What technical writers earn in Columbus
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$34 | $52k–$71k |
| Mid level | $34–$46 | $71k–$95k |
| Senior | $45–$60 | $93k–$124k |
Adjusted for the Columbus 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 Columbus?
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.