1

Api Technical Writer Jobs in Michigan (NOW HIRING)

... writing SQL queries, supporting API integrations, and assisting with Microsoft Entra ID (Azure AD ... Technical Business Analyst Minimum Qualifications and Job Requirements: * Bachelor's degree in ...

Demonstrated experience supporting or implementing API integrations, including diagnosing failures ... Excellent verbal and written communication skills, with the ability to translate technical concepts ...

... API development. * Write and maintain complex customizations, scripts, and integrations using EKL ... technical and leadership courses/books/seminars once you have 6+ months of tenure, and ...

Technical Product Manager

Dearborn, MI · On-site

$153K - $177K/yr

Prior hands-on experience with cloud infrastructure, scripting, or API development (e.g., Go ... Experience writing user docs, onboarding guides, or internal wikis * Strong instinct for **when to ...

Technical Lead - Portal

Novi, MI · On-site

$103K - $168K/yr

Excellent skill designing the interface between frontend and backend systems, including RESTful API ... German language fluency - verbally and written desired. Rolls-Royce is an Equal Opportunity ...

Technical Lead - Portal

Novi, MI · On-site

$103K - $168K/yr

Excellent skill designing the interface between frontend and backend systems, including RESTful API ... German language fluency - verbally and written desired. Rolls-Royce is an Equal Opportunity ...

next page

Showing results 1-20

Api Technical Writer information

See Michigan salary details

$11

$33

$57

How much do api technical writer jobs pay per hour?

As of Aug 23, 2026, the average hourly pay for api technical writer in Michigan is $33.94, according to ZipRecruiter salary data. Most workers in this role earn between $25.14 and $41.06 per hour, depending on experience, location, and employer.

What does an API technical writer do?

An API Technical Writer creates clear, concise, and user-friendly documentation for developers using an organization's APIs. They translate complex technical concepts into accessible guides, reference materials, and tutorials. This role requires collaboration with engineers, product managers, and other stakeholders to ensure accuracy and usability. API Technical Writers often have experience with programming languages, markup languages like Markdown or XML, and tools for generating API documentation. Their goal is to enhance developer experience and streamline API adoption.

What are the key skills and qualifications needed to thrive as an API technical writer?

To thrive as an API Technical Writer, you need strong technical writing abilities, a solid understanding of software development, and experience with API documentation standards. Familiarity with tools like Swagger/OpenAPI, Postman, Markdown, and version control systems such as Git is typically required, and certifications in technical communication can be beneficial. Excellent communication, attention to detail, and collaboration skills help you convey complex information clearly and work effectively with developers and stakeholders. These skills are vital to produce accurate, user-friendly documentation that enhances developer adoption and reduces support requests.

What are the typical day-to-day responsibilities of an API technical writer?

As an API Technical Writer, your daily tasks often include collaborating with software engineers to gather technical details, creating and updating API reference materials, writing tutorials and code samples, and reviewing documentation for accuracy and clarity. You'll frequently use tools for documentation, testing APIs, and managing version control, while also attending meetings to stay aligned with product developments. Additionally, you may solicit feedback from both internal teams and external users to continuously improve documentation quality. This role often involves balancing independent research with teamwork to ensure comprehensive and accessible API documentation.

What are the most commonly searched types of Api Technical Writer jobs in Michigan?

The most popular types of Api Technical Writer jobs in Michigan are:

Infographic showing various Api Technical Writer job openings in Michigan as of August 2026, with employment types broken down into 1% As Needed, 83% Full Time, 9% Part Time, 2% Temporary, 3% Contract, and 2% Nights. Highlights an 88% Physical, 4% Hybrid, and 8% Remote job distribution, with an average salary of $70,600 per year, or $33.9 per hour.

AI Software Engineer / Senior Technical Writer

ComResource

Detroit, MI • On-site

Full-time

Posted 22 days ago


Job description

ComResource is looking for a Senior Technical Writer.

Responsibilities:

  • Author knowledge entries, including service overviews, runbooks, decision records, schemas, specifications, and glossary terms drawn from workflows, policies, engineering standards, and technical documentation.
  • Write short descriptions and summaries that drive progressive disclosure, enabling AI agents to determine whether loading a full entry is worth the context cost.
  • Structure orientation paths so an agent onboarding to an unfamiliar domain encounters the mental model, entry points, and invariants first, and drills into detail only on demand.
  • Maintain hierarchy coherence across a growing catalog including cross-linking, indexing, reachability, and layered structure that keeps entries discoverable as the corpus scales.
  • Own the scoping metadata that routes entries to the right consumer in the right context.
  • Author and maintain prompt assets including reusable skills, agent instructions, and reference material consumed directly by production agents.
  • Codify engineering standards by turning review standards, security requirements, and platform conventions into structured, versioned rules that automated code review agents apply on every pull request.
  • Interview developers and engineers to capture the rationale behind decisions.
  • Advance entries through review and approval with engineering and governance partners to ensure only verified content reaches production consumers.
  • Govern vocabulary by maintaining the glossary and naming conventions and resolving terminology collisions before they propagate into schemas, tooling, and agent behavior.
  • Keep the catalog current by identifying and retiring stale entries as the systems they describe change.

Essentials:

  • 5–7 years of technical writing experience in software, platform, or infrastructure environments.
  • Demonstrated ability to produce accurate technical content from primary sources including code, configuration, specifications, and runbooks with limited handholding.
  • Strong information architecture instincts, including taxonomy, cross-linking, layered structure, and progressive disclosure.
  • Experience authoring reference material, standards, or specification documentation consumed by engineers.
  • Comfort working directly with developers and engineers, including the credibility to push back when source material is incomplete or contradictory.
  • Experience partnering with governance, risk, security, or compliance stakeholders.
  • Editorial discipline with consistency of terminology, voice, and structure maintained across many documents and contributors.
  • Familiarity with docs-as-code practices including Markdown, version control, and content that lives in a repository alongside the systems it describes.
  • Clear verbal communication skills with the ability to gather source material through conversation.
  • Writes with precision under hard length constraints.
  • Proficiency with Markdown, YAML, structured frontmatter, and schema validation.
  • Familiarity with Git and pull-request workflows including documentation validation and link-checking tooling.

Desired:

  • Hands-on experience writing prompts, agent instructions, or reusable skill definitions for LLM-based systems.
  • Understanding of context management techniques for AI agents including progressive disclosure, context window economics, and retrieval strategy.
  • Experience with structured content including YAML or JSON frontmatter validated against a schema, content models, or typed document formats.
  • Working comfort with Git and CLI-based authoring workflows.
  • Exposure to taxonomy design, ontologies, knowledge graphs, or controlled vocabularies.
  • Background in developer documentation, API documentation, or internal platform documentation.
  • Familiarity with AI agent concepts, including tool use, orchestration, retrieval, and agent context protocols such as MCP.
  • Reading-level familiarity with Python, TypeScript, Terraform, or YAML-based configuration.
  • Experience in banking, financial services, or another regulated industry.

Req ID: AM891999729