Senior Full-Stack Software EngineerBackend-Focused | Java & SaaS | Full-Time | Remote (United States)Compensation: $120,000-$150,000 annually, depending on experience.About the PositionOilfield Tracking Services (OTS) de…
Technical Writer jobs in Salt Lake City, UT
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
8 shown · sorted by freshness
performance reports at least 24 hours before scheduled calls Translate campaign data into clear, actionable recommendations for non- technical clients Build strong client relationships that support retention, renewals, a…
, and reporting. You'll work alongside our developers, content writers, and local SEO specialist, and mentor the SEO team members on your... ...for local service businesses; law firms strongly preferredDeep technical SEO…
Position Title: Full Stack Software EngineerLocation: Baltimore, MDIndustry: EducationFull Stack Software Engineer Summary:Our client is seeking a Full Stack Software Engineer who will participate in and/or guide the dev…
Remote Cultural Resources Technical Writer – Archaeology Location: Fully remote Duration: Anticipated 2–3 years About the Opportunity We are seeking a Cultural Resources Technical Writer with a strong background in appli…
Modern Enterprise Platforms and AI-Enabled Solutions Are you an experienced Full Stack Java Engineer who enjoys solving complex technical challenges and building scalable, enterprise-grade applications? Do you thrive in…
About Grace CompanyGrace Company is a leader in the quilting manufacturing market. Having been in business for over 40 years we connect quilters with their passions and use innovations to make the hobby easier and more a…
Cultural Resources Technical Writer We are seeking an experienced Cultural Resources Technical Writer to support a large federal infrastructure program. This role is suited to an archaeologist who can independently devel…
What technical writers earn in Salt Lake City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $27–$37 | $57k–$77k |
| Mid level | $37–$50 | $77k–$103k |
| Senior | $49–$64 | $101k–$134k |
Adjusted for the Salt Lake City 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 Salt Lake City?
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.