Welcome to Spectiv VR, We are a collective of young and entrepreneurial millennials setting out to build a dedicated virtual reality streaming platform out of Houston, Texas. We are looking to bring on driven developers…
Technical Writer jobs in Houston, 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 14 · sorted by freshness
DescriptionKforce has a client in Houston, TX that is seeking a Senior Full Stack Software Engineer to design, build, enhance, and support enterprise applications used across pricing, transaction management, supply opera…
Position Summary We are seeking a talented and detail-oriented Curriculum Writer to develop high-quality educational and training materials that align with organizational goals and learner needs. This role will collabora…
Location: Houston, TX Company: Aria Signs & Design Position Type: Full-Time, In-Office Aria Signs & Design is looking for an organized and creative Digital Media Specialist to join our marketing team. This role is ideal…
Dot Net Full Stack Developer Must have skills : Azure DevOps suite (Strong), Oracle (Capable), PL/SQL Good to have skills: Job Description : Understand requirements and discussion with Product owner Able to work in scrum…
that sit on top of them. This is a hands on senior role. You will own features from design through production support, set the technical bar for quality and testing, and mentor junior engineers on the team. You will work…
salary: $54 - 64 per hour work hours: 8am to 5pm education: High School responsibilities: Job Responsibilities Provide technical development, configuration, customization, and support for Oracle WebCenter Content 12c (UC…
Product Managers to establish objectives and design functional, cohesive codes to enhance the user experience. Keep abreast of novel technical concepts and markets. Provide technical leadership and documentation to devel…
At Houston Methodist, the Scientific Writer position is responsible for performing a variety of tasks including preparing laboratory... ...positive language principles Ability to write in a scientific or technical field…
About the Role We are seeking a hybrid technical expert to lead our digital workspace transformation. You will be responsible for the full lifecycle of migrating legacy file shares and classic SharePoint sites to SharePo…
visual effects that integrate seamlessly with live-action and digital environments. The ideal candidate has strong artistic ability, technical expertise, and experience working within professional production pipelines. K…
Requirements · 8 years of handson experience with MongoDB Express NestJS Angular and Nodejs · Proven expertise in implementing queuing systems with RabbitMQ, Kafka · Experience with identity management using Keycloak · P…
What technical writers earn in Houston
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $26–$36 | $54k–$74k |
| Mid level | $36–$47 | $74k–$98k |
| Senior | $46–$61 | $96k–$127k |
Adjusted for the Houston 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 Houston?
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.