experience across front-end, back-end, and database technologies. We value the ability to design software that meets functional and technical needs and to communicate those designs clearly. We need someone who can think…
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
12 shown of 22 · sorted by freshness
Job Title: Full-Stack Developer Job Location: Wilmington DE Job Type: Full-Time Job Description: Must Have: Enterprise Java, Spring Boot, REST APIs, Kafka, Microservices, React, JavaScript, CSS, Git, Junit, SQL, PostgreS…
and Operations. Resolve production issues, perform root cause analysis, and drive continuous improvements in system stability and performance. Provide technical leadership, mentor developers, and ensure adherence to codi…
Core Responsibilities Execute creative software solutions, design, development, and technical troubleshooting while thinking beyond routine or conventional approaches to solve technical problems. Develop secure, high-qua…
Role: Advanced Planning Document Writer Location: NC DHHS, Raleigh NC Remote The Division of Health Benefits, NC Medicaid... ...business engagement, stakeholder management, project management, and technical liaison activ…
engineering technician capacity. Under general direction, supports engineering and design teams by developing and modifying technical deliverables. Applies foundational engineering principles and established design pract…
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…
team that enhances, builds, and delivers trusted market-leading technology products in a secure, stable, and scalable way. As a core technical contributor, you will drive critical technology solutions across multiple tec…
Particle Systems Industry: Video Game Development Executive Position Summary Eleventh Hour Games is seeking a visionary and technically proficient Lead VFX Artist to drive the visual identity of our breakout title, Last…
animation while remaining hands-on in production. This role focuses on bridging the gap between high-level creative direction and technical execution in a remote, agile indie environment. Key Responsibilities Creative Le…
Available Weekly Team Lunches Locally Owned and Operated Job Description Job Title: Automotive Service Advisor / Writer Location: 8555 Sancus Blvd, Columbus, OH 43240 Job Overview: As an Automotive Service Advisor / Writ…
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.