software engineering lifecycle and support continuous integration, delivery, and deployment of safety-critical software. We provide technical oversight across systems and guide teams in designing and operating production…
Technical Writer jobs in St. Louis, MO
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 14 · sorted by freshness
Salary: $69,550 - 125,725 per year Requirements: Bachelors degree in Information Systems, Information Technology, Computer Science, or a closely related field, plus 4 or more years of relevant experience; or a masters de…
Salary: $69,550 - 125,725 per year Requirements: Bachelors degree in Information Systems, Information Technology, Computer Science, or a closely related field, plus 4 or more years of relevant experience; alternatively,…
for eligible internal candidates. CodeVue Coding Challenge:To be considered for this position you will be required to complete a technical assessment as part of the selection process. Failure to complete the assessment w…
interested in this position, please send over your updated resume. We look forward to hearing from you! Job Description: Technical Documentation Specialist Location: Remote Duration: 12+ months Rate: $50-55/hr. On W2 We…
stronger. For more information, visit or follow MMS on LinkedIn . Responsibilities Under minimal supervision, the Medical Writer will critically evaluate, analyze, and interpret the medical literature to select primary r…
THIS POSITION IS NOT REMOTE. PLEASE READ CAREFULLY BEFORE APPLYING Opportunity Blayzer Digital in St. Louis, MO is hiring a full-time SEO & Copywriting Specialist for our growing team. This person will be responsible for…
Exciting Opportunity: Join Blayzer Digital as a Social Media Manager! Are you ready to elevate your career and make your mark on the digital landscape? Blayzer Digital is on the hunt for a dynamic Social Media Manager to…
: A strong portfolio or social handle showcasing automotive photography, fast-paced video editing, and short-form content. * Technical Expertise: Proficiency with mirrorless/DSLR cameras, gimbals, audio gear, and lightin…
enjoys solving challenging business problems, building scalable applications, and translating complex requirements into practical technical solutions. This position is best suited for an experienced engineer who is comfo…
At Unbridled, people matter. While we embrace AI as a tool to help us work smarter, we don’t use it to screen resumes or to conduct interviews on our behalf. Applications are reviewed by a real person on our team, and ev…
What technical writers earn in St. Louis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$33 | $51k–$69k |
| Mid level | $33–$44 | $69k–$92k |
| Senior | $43–$58 | $90k–$120k |
Adjusted for the St. Louis 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 St. Louis?
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.