configuration, design, and troubleshooting. The successful candidate will consult with support teams, help desks, customers, and other technical staff to resolve problems, coordinate and operate maintenance activities fo…
Technical Writer jobs in San Antonio, TX
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 22 · sorted by freshness
Job Description Job Description The Social Media and Digital Content Coordinator is responsible for creating and managing multimedia content for the St. Mary's website and social media accounts. The Social Media and Digi…
Kforce has a client in San Antonio, TX that is seeking a Junior Project Manager/Instructional Designer. Summary: The Junior Project Manager/Instructional Designer will be leading meetings for two managers with their team…
instructional design Develop written and performance assessments; determine reliability and validity of evaluation instruments Produce technical writing and course documentation, and manage scheduling processes Partner w…
from 1 to 7 days, depending on complexity. Technologies: Mobile UX UI Design AI LESS More: We are hiring a UX Writer for our client in San Antonio, TX. We offer eligible employees comprehensive benefits, including medica…
Kforce has a client in San Antonio, TX that is seeking a Senior Full Stack Developer to lead our technical direction and architect scalable digital platforms. This person will make high-level decisions regarding system d…
inside the platforms: Google Ads, Meta, and Microsoft Ads, managing and maintaining campaigns across a portfolio of clients. This is a technical execution role. You won't be presenting to clients or setting high-level st…
: POSITION SUMMARY/RESPONSIBILITIES In coordination with members of the Foundation team, develops effective communication materials for various internal and external constituencies. Responsible for researching, writing a…
metrics, identifying performance opportunities, and optimizing recruitment marketing strategies through data-driven decision-making. Technical proficiency with social media platforms, content management systems, SEO tool…
Job ID R0119004 Date posted 07/22/2026 Why USAA? At USAA, our mission is to empower our members to achieve financial security through highly competitive products, exceptional service and trusted advice. We seek to be the…
Technology (IT) to include basic business applications and relational database concepts Requires at least 2-4 years of experience with technical writing, technical documentation and/or training end users of software syst…
themselves on their robust end to end solutions they offer, as well as reputation for excellence in the market, is seeking an Entry Writer for their team! This position is a rewarding opportunity, for the professional se…
What technical writers earn in San Antonio
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 San Antonio 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 San Antonio?
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.