Experience using Git, pull requests, and collaborative code review. Ability to turn business requirements into maintainable technical solutions and identify when clarification is needed. Clear communication, systematic p…
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 13 · sorted by freshness
Social Media & Community Manager Root Causes Medicine | San Antonio or Austin, TX | Fractional, ~20 hrs/week | On-Site About Root Causes Root Causes Oncology is the integrative oncology program of Root Causes Medicine, a…
Required:Ability to Obtain Public TrustWhat You Will Do:Collaborate closely with clients, digital leaders, solution architects, and technical and functional leads across Guidehouse digital teams and market segments to su…
closely with business, solution engineers, team members and leadership to understand business requirements and deliver high quality technical solutions Analyzing, implementing user requirements/business needs as new and/…
```html Spotless Auto LLC is seeking a dedicated FULL-TIME JANITOR/Sanitation Engineer to join our team in San Antonio, TX. This role is essential to maintaining a clean, safe, and sanitary environment across our facilit…
Section Details Job Title Frontend Developer Job Type Contract Client Location San Antonio TX Work Arrangement Onsite Duration 6 Months Job Summary Seeking an experienced Frontend...
Location: San Antonio, TX (Onsite from first day of joining) Job Type: Fulltime Job Description: Must Have Technical/ Functional Skills Technical Java Spring Kafka REST API Functional Payments Knowledge...
Hi All, Full Time Oppurtunity with one of our customer//NO C2C Location SantAntonio,TX Designed and developed scalable web applications using Java, Spring Boot, Hibernate, REST APIs, Angular/React, HTML5, CSS3, and JavaS…
readiness in demanding environments. Why This Role Matters: This role is designed for an early-career developer who wants meaningful technical work and structured growth. You will contribute across the application stack…
Compensation: $100,000 - $120,000 annually Position Summary: Stratitia is seeking a Senior Full Stack Developer to provide hands-on technical leadership for the Defense Health Agency's operational medicine and blood-mana…
integration tests, participate in peer reviews, and improve automated regression coverage. • Estimate work, identify dependencies and technical risks, and communicate progress within Agile planning and delivery ceremonie…
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.