Boolean search strings for technical writers: API docs, DITA, regulated content and the writer title problem

Technical writer titles split across "technical writer," "documentation specialist," "information developer," "technical author," "API writer" and "documentation engineer," and the same words pull in copywriters, content marketers, clinical documentation specialists and technical recruiters. What separates documentation writers is the kind of documentation and the toolchain: API reference and OpenAPI, docs as code with Markdown and Git, structured authoring in DITA, S1000D and Simplified Technical English in aerospace and defense, and regulatory or medical writing. As of November 2026, certifications are a weak filter for this role (AMWA is ending its Medical Writer Certified program after December 2026), so the strings search the work and the screen asks for samples.

Below are ten strings by kind of documentation, and what LinkedIn, Dice, Indeed and Google support as of November 2026. To pin down the documentation type with the client first, use the technical writer job description template.

Documentation types, standards and credentials that change what a technical writer search finds

• What the job is. The BLS page for technical writers says they prepare instruction manuals, how-to guides, journal articles and other supporting documents, that they typically need a bachelor's degree, and that some associations offer certification, as of November 2026. It lists professional, scientific and technical services as the largest employer, followed by manufacturing and information.
• DITA. OASIS's DITA technical committee page expands the name as Darwin Information Typing Architecture and lists DITA 1.3 as an OASIS Standard. DITA on a profile means topic-based XML authoring, usually in a component content management system (CCMS).
• S1000D and STE. The S1000D site calls it an international specification for the production of technical publications, free to download. The ASD-STE100 site describes Simplified Technical English as a controlled natural language and an international standard for writing technical documentation, owned by ASD, and lists Issue 9 dated January 15, 2025. Both point to aerospace and defense maintenance documentation.
• MadCap's certification. MadCap's certification page describes the MadCap Advanced Developer (MAD) certification for Flare as a 75-minute, 50-question test plus a sample project. Profiles write "MAD certified."
• Medical writing. AMWA's MWC page says the association will conclude the Medical Writer Certified program after a final exam window of December 1-21, 2026, that holders active on January 1, 2027 keep active status through December 31, 2031, and that employers verify the credential by contacting AMWA's certification office.
• Older credentials. Some profiles list the CPTC from the Society for Technical Communication. When we checked stc.org in November 2026 it showed only an under-update notice and no certification pages, so there is no official place to check that credential online; ask the candidate.

Ten Boolean strings by kind of documentation

Swap in the product, industry and metro from your own intake; these are examples. Search on the work and the tools, never on a term that stands in for age, sex, race, religion, national origin, disability or veteran status.

Software and API documentation

1. API technical writer — LinkedIn Recruiter, Job titles + Keywords filters
("technical writer" OR "api writer" OR "api technical writer" OR "documentation engineer" OR "developer documentation") AND ("api reference" OR openapi OR swagger OR sdk) AND ("code samples" OR python OR javascript OR curl) NOT (recruiter OR copywriter)

2. Docs-as-code writer — LinkedIn general search
("technical writer" OR "documentation engineer") AND ("docs as code" OR "docs-as-code" OR markdown) AND (git OR github OR sphinx OR mkdocs OR docusaurus)

3. Software user documentation writer — Dice resume search
("technical writer" OR "documentation specialist") AND ("user guides" OR "online help" OR "release notes") AND (saas OR software) AND (confluence OR "madcap flare")

Structured authoring and help tools

4. DITA information developer — LinkedIn general search
("information developer" OR "technical writer" OR "dita writer") AND dita AND (xml OR "oxygen xml" OR ccms OR "content reuse")

5. Help authoring writer — Dice resume search
("technical writer" OR "documentation specialist") AND ("madcap flare" OR framemaker OR robohelp) AND ("single sourcing" OR "conditional text" OR "topic-based")

Industry documentation and X-ray

6. Aerospace and defense technical writer — LinkedIn general search
("technical writer" OR "technical publications" OR "tech pubs" OR "technical author") AND (s1000d OR "simplified technical english" OR "asd-ste100" OR ietm) AND (aircraft OR aerospace OR defense OR maintenance)

7. Equipment and manufacturing manuals — Indeed Smart Sourcing
("technical writer" OR "technical author") AND skill: ("service manuals" OR "work instructions" OR "maintenance manuals") AND (machinery OR equipment OR manufacturing)

8. Regulatory or medical writer — LinkedIn general search
("regulatory writer" OR "medical writer" OR "technical writer") AND ("clinical study reports" OR "regulatory submissions" OR sops OR ifu) AND (fda OR "medical device" OR pharmaceutical) NOT ("medical scribe" OR "clinical documentation specialist")

9. UX writer or content designer — LinkedIn general search
("ux writer" OR "content designer" OR "product content") AND (microcopy OR "content design" OR "in-product") AND (figma OR "design system") NOT ("content marketing" OR copywriter)

10. Public writing portfolios — Google X-ray
"technical writer" "writing samples" "api documentation" -jobs -hiring -course

Technical writers often keep a public portfolio of samples, which makes string 10 more useful here than for most roles. It reaches only public, indexed pages, and a portfolio shows what the writer chose to publish, not what an editor changed.

What LinkedIn, Dice, Indeed and Google actually support

As of November 2026, LinkedIn's Boolean help page requires AND, OR and NOT in capitals, supports quotes and parentheses, evaluates quoted phrases first, then parentheses, NOT, AND and OR, and does not support wildcards, so "writer," "writing" and "documentation" each need writing out, and so do "docs as code" and "docs-as-code." LinkedIn Recruiter's Boolean page lists stop words ignored in search, including "and," "of" and "for," which loosens phrases such as "operation and maintenance manuals"; keep those in general searches or use shorter phrases. The same page warns that too many facets in one query can cause a search result issue.

Dice's Boolean guide supports parentheses, quotes, AND, OR and NOT, fills in word endings automatically, and warns to use NOT sparingly. Indeed's Boolean guide documents the skill: field that string 7 uses. Google's search operators page documents quotes, site:, the minus sign and filetype:, but not OR, so string 10 uses none.

Narrowing by audience, toolchain and regulation

The audience is the must-have. Writing for developers, for end users, for field technicians and for regulators are four different skills, and a writer strong in one can struggle in the first month of another. Ask the client who reads the documentation, then match the toolchain: a docs-as-code team will want Git and Markdown, an enterprise documentation group a DITA CCMS, an equipment maker FrameMaker or Flare, an aerospace supplier S1000D. Regulated industries add document control and review cycles, which strings 6 and 8 search for.

Seniority shows in ownership: "owned the docs site," "built the information architecture," "wrote the style guide," "set up docs as code" and "led the migration to DITA," against "updated" and "edited." Contract work is common in this field, so a list of six-month projects is normal and says little about performance. LinkedIn's premium search filters page lists Years of Experience and Seniority Level only in Recruiter and Sales Navigator.

False positives worth excluding with NOT

• Copywriters and content marketers. They write "writer," "content" and "SEO." Exclude copywriter, "content marketing" and SEO, and require a documentation word.
• Clinical documentation specialists and scribes. Hospital documentation integrity staff and medical scribes write "documentation specialist." Exclude them for technical roles.
• Other "documentation specialists." Mortgage, legal and logistics document specialists prepare paperwork rather than write it. Exclude loan, mortgage and closing when they appear.
• Proposal and grant writers. They write technical volumes for bids. Exclude "proposal writer" and "grant writer" unless the client accepts them.
• Engineers who mention documentation. Software engineers write "wrote documentation" as one bullet among many. Require a writer or documentation title in every string; when an engineer is the actual hire, use Boolean search strings for software engineers.
• Technical recruiters. "Technical" plus "writer" sometimes matches recruiters who write job posts. Exclude recruiter.

A worked example: three passes on a medical device manuals search

An invented search, shown as it actually gets narrowed.

The documentation and tool blocks removed the marketing writers; the regulation block found the writers who work inside a quality system. Add it once the title and tool blocks are in place.

What a search cannot verify

A string can find someone who lists the right documentation type and tools. It cannot show whether they write clearly, whether a sample was heavily edited, or whether they can get engineers to review on time. Ask for two or three samples and who edited them, then use the documentation skills interview questions and the written communication questions on the call, and share the 30-60-90 day plan for technical writers with the hiring manager to agree what the first 90 days should produce.