An e-commerce company focused on audio solutions is looking for a Senior Full Stack Developer to produce scalable software solutions. The ideal candidate will manage the full software development life cycle from concepti…
Engineering & IT · Louisville, KY
Technical Writer jobs in Louisville, KY
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.
6
Open roles today
$24–$57/hr
Typical pay range
$80k
Median, full-time
3
Fresh in this list
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.
01
Open technical writer roles
5 shown of 6 · sorted by freshness
Full Stack lead Developer (Java, Angular, Scala) We are seeking a highly skilled Full Stack Engineer with 3+ years of experience in Angular and Java, along with hands‑on exposure to Scala and Apache Spark, to join our te…
Stack Developer Louisville, Kentucky or Dallas, Texas (on-site) market rate React Native Full Stack Developer Must Have Technical/ Functional Skills Hands on Experience in Mobile Development using React Native. (Must Hav…
enterprise software platforms, customer-facing applications, APIs, and healthcare technology solutions. This role serves as a senior technical contributor, partnering with internal stakeholders and external clients to de…
REACH Alert is seeking a self-directed part-time Web/App Developer with a passion for technology, collaboration, and creative problem-solving. The intern will actively contribute to meaningful projects and work closely w…
02
What technical writers earn in Louisville
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $24–$33 | $50k–$68k |
| Mid level | $33–$44 | $68k–$91k |
| Senior | $43–$57 | $89k–$118k |
Adjusted for the Louisville market from national ranges.
03
What employers ask for
The skills these listings keep naming
Clear, plain-language writingDocs-as-code (Markdown, Git)API documentation (OpenAPI)Information architectureInterviewing engineersStyle guides and consistencyBasic scripting or code readingDocs tooling (Docusaurus, etc.)Editing and review workflows
04
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.
05
Resume tips that move the needle
For technical writers specifically — generic advice costs you here
01
Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.
02
Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.
03
List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.
04
Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.
05
Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.
06
Where this role goes
Typical progression
01
Junior Technical Writer
02
Technical Writer
03
Senior Technical Writer
04
Documentation Manager
Ten quiet minutes a day
Applying for technical writer jobs in Louisville?
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.