adhering to architectural best practices; considers scalability, reliability and performance of systems/contexts affected when defining technical designs Performs analysis on failures, propose design changes, and encoura…
Technical Writer jobs in Cincinnati, 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
10 shown of 20 · sorted by freshness
pays, banks and invests. This will involve developing core versions of software applications, identifying client requirements and technical specifications, interacting with engineering groups and training clients on appl…
What You’ll Do About This Role We're seeking a versatile Backend Software Engineer who thrives at the intersection of technical excellence and collaborative innovation. This intermediate-level position is designed for a…
Job Title: Frontend Web Developer II Location: HYBRID in Cincinnati, Charlotte, or Chicago TOP SKILLS: Must Have CCS and HTML hands on experience Knowledge of AEM and web pages development Mobile/Web Development What You…
Job Title: Senior Frontend Engineer (Angular) Location: Cincinnati, OH Job Description We are seeking a Senior Frontend Engineer with 8 10 years of experience in modern web development and expertise in Angular (v16+). Th…
Current UC employees must apply internally via SuccessFactors Faculty rank and compensation will be based on experience and academic credentials. Next Lives at the University of Cincinnati Founded in 1819, the University…
administrators. Participate in project planning process. May help prepare estimates and operational requirements. Assist with technical design specifications. Maintain appropriate documentation and code commenting. Assis…
structural engineering faculty teach courses to students in all three undergraduate programs. These faculty are actively engaged in technical committees within AISC, ACI, and PCI with strong ties to industry. UC’s Civil…
Service Writer We are seeking a motivated and organized person to join our team as a Service Writer. As the key link between customers and technicians, you’ll ensure a smooth service experience from start to finish. Prim…
If you are an affable and talented mid-level web engineer with excellent attention to detail who enjoys a flexible, fast-paced work environment then Ample is the right fit for you. Help us bring digital strategy to life…
What technical writers earn in Cincinnati
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$34 | $51k–$70k |
| Mid level | $34–$45 | $70k–$93k |
| Senior | $44–$58 | $91k–$121k |
Adjusted for the Cincinnati 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 Cincinnati?
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.