meet client specifications and business objectives. Collaborate with stakeholders to gather requirements and translate them into technical designs and development tasks. Develop custom SharePoint components, including we…
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
12 shown of 19 · sorted by freshness
us on LinkedIn! JOB DESCRIPTION GENERAL FUNCTION The Senior Production Technician is responsible for performing advanced technical work within their assigned production area (e.g., Surfacing, Finishing, or Coating) while…
extensive web development experience will also be considered. Strong skills in HTML, CSS, and Bootstrap are preferred, along with knowledge of ITIL processes. This role emphasizes technical leadership and code quality wh…
Position Description The Social Media Manager serves as the primary content creator, messaging strategist, and data analyst across OTSL’s public-facing social media channels, playing a vital role in the discovery and eng…
The Archdiocese of St. Louis strives to teach and share our faith, serve others, and foster unity throughout the St. Louis area. Once a part of Kenrick-Glennon Seminary's campus, the Cardinal Rigali Center in Shrewsbury,…
Job Detail Organization: GeoAcuity Title: FRONT-END DEVELOPER Location: On-site - St. Louis, MO | DC Metro | Springfield, VA | Redlands, CAPosted: 2026-07-10 Application Deadline: Position Description: FRONT-END DEVELOPE…
Job Detail Organization: GeoAcuity Title: Back-End Developer Location: On-site — St. Louis, MO | DC Metro | Springfield, VA | Redlands, CAPosted: 2026-07-07 Application Deadline: Position Description: Back-End Developer…
Job Description Job Description Job Summary The Technical Writer/ Technical Content Manager is responsible for developing Mark Andy technical manuals and supporting product communication. This role researches and develop…
Job Description Job Description Reinventing Geospatial (RGi) is a leading expert in geospatial solutions for Defense, Intelligence, and Federal clients. We enhance situational awareness for soldiers and analysts by integ…
The Archdiocese of St. Louis strives to teach and share our faith, serve others, and foster unity throughout the St. Louis area. Once a part of Kenrick-Glennon Seminary's campus, the Cardinal Rigali Center in Shrewsbury,…
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…
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.