Engineering & IT · Oklahoma City, OK

Technical Writer jobs in Oklahoma City, OK

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.

12
Open roles today
$24–$56/hr
Typical pay range
$78k
Median, full-time
10
Fresh in this list

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.

01

Open technical writer roles

12 shown · sorted by freshness

Director of Social Media

life · Edmond, OK · Full-time

The Director of Social Media is primarily responsible for leading the strategy, execution, and growth of YouVersion’s social media presence, representing the ministry and the YouVersion Family of Apps across multiple glo…

Posted today
+ Save to tracker View listing

Motion Designer

life · Edmond, OK · Full-time

The Motion Designer is primarily responsible for developing motion graphics based on the needs and requests of Central and campus teams. This role will also support graphics for the weekend experience, for ministry teams…

Posted yesterday
+ Save to tracker View listing

Newsletter Writer

NoGigiddy · Oklahoma City, OK · Full-time
$17 - $24 per hour

newsletter lands in inboxes every week — and it needs to be the kind of email people actually look forward to opening. As our Newsletter Writer, you'll research, write, and produce a weekly newsletter that keeps our audi…

Posted 2d ago
+ Save to tracker View listing

Senior Full-Stack Software Engineer

Oilfield Tracking Services · Oklahoma City, OK · Full-time
$120k

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…

Posted 2d ago
+ Save to tracker View listing

Social Media Ads Manager

NoGigiddy · Oklahoma City, OK · Full-time
$19 - $28 per hour

ABOUT NOGIGIDDY NoGigiddy is a digital platform built for gig workers, side hustlers, and anyone building an income outside the traditional 9-to-5. We connect our community with real earning opportunities - remote jobs,…

Posted 2d ago
+ Save to tracker View listing

SEO Content Writer

NoGigiddy · Oklahoma City, OK · Full-time
$17 - $24 per hour

existed, and we hire people who actually get it. THE ROLE Words drive traffic — and traffic drives everything. As an SEO Content Writer at NoGigiddy, you'll create articles, guides, and landing pages that rank on Google…

Posted 3d ago
+ Save to tracker View listing

Social Media Manager

NoGigiddy · Oklahoma City, OK · Full-time
$18 - $27 per hour

ABOUT NOGIGIDDY NoGigiddy is a digital platform built for gig workers, side hustlers, and anyone building an income outside the traditional 9-to-5. We connect our community with real earning opportunities — remote jobs,…

Posted 3d ago
+ Save to tracker View listing

Content Marketing Manager

Acrisure · Oklahoma City, OK · Full-time

Are We Looking for in this Role Qualifications ~6-10 years of B2B content experience ideally in SaaS or fintech. ~ Strong writer who can also think strategically. Complete understanding of difference between content that…

Posted 6d ago
+ Save to tracker View listing

Medical Writer CTO

University of Oklahoma · Oklahoma City, OK · Full-time
$54.7k - $72.5k

cancer care through innovative research groundbreaking clinical trials and scientific discovery. We are seeking a talented Medical Writer to join our Clinical Trials Office (CTO) and play a pivotal role in accelerating r…

Posted 6d ago
+ Save to tracker View listing
02

What technical writers earn in Oklahoma City

Hourly first — that's how the offer arrives

ExperienceHourlyAnnual, full-time
Entry level $24–$32 $49k–$67k
Mid level $32–$43 $67k–$89k
Senior $42–$56 $87k–$116k

Adjusted for the Oklahoma City market from national ranges.

03

What employers ask for

The skills these listings keep naming

Clear, plain-language writingDocs-as-code (Markdown, Git)API documentation (OpenAPI)Information architectureInterviewing engineersStyle guides and consistencyBasic scripting or code readingDocs tooling (Docusaurus, etc.)Editing and review workflows
04

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.

05

Resume tips that move the needle

For technical writers specifically — generic advice costs you here

01

Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.

02

Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.

03

List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.

04

Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.

05

Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.

06

Where this role goes

Typical progression

01 Junior Technical Writer
02 Technical Writer
03 Senior Technical Writer
04 Documentation Manager
Ten quiet minutes a day

Applying for technical writer jobs in Oklahoma 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.

Start with this search No email, no resume, no sign-up. Open your tracker Everything you saved is already there.
12 Technical Writer roles in Oklahoma City Save them into one pipeline Save them into your pipeline
Start free My tracker