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…
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 17 · sorted by freshness
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…
across Python, Java/Node.js, APIs, cloud and containerized environments while helping Defense and Intelligence customer solve complex technical problems. Esri has a Relocation Assistance Program and can provide support w…
Technical Document Writer Company: Tapestry - G0G Tapestry Solutions A Boeing Company brings over 30 years of industry experience designing implementing training and supporting high-quality cost-effective information tec…
Kubernetes/OpenShift or a major cloud provider) preferred ~ Excellent communication skills (written verbal and presentation) for both a technical and non-technical audience Certain states and localities require employers…
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 integrating software development with…
and testable code. Create and maintain unit, integration, API, and end-to-end automated tests. Participate in code reviews, technical design discussions, backlog refinement, sprint planning, retrospectives, and daily Agi…
Required Skills & Qualifications Education: Bachelors degree in Computer Science, Software Engineering, or a related technical field (or equivalent practical experience). Core Java Expertise: Extensive experience with Ja…
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…
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…
Data Entry Transcriber (NARA St. Louis)Location: 1 Archives Drive, St. Louis, MOStatus: Full-TimePosition Summary:The Data Entry Specialist provides accurate data entry and transcription support for federal personnel rec…
Creative Media & Brand Specialist We're seeking a Creative Media & Brand Specialist to help tell the story of Guarantee Electrical Company visually through photography, video, design, and creative content that showcases…
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.