Company OverviewQuality Roots is a licensed cannabis dispensary based in Metro Detroit, known for our curated product selection and community-first vibe. We strive to provide quality service and products throughout 9 loc…
Technical Writer jobs in Detroit, MI
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 15 · sorted by freshness
Web Developer Detroit, MI Hybrid (2 days onsite) 6 months extension / conversion potential Full-time, EST hours $40 - $50 Hourly Overview We’re seeking a mid to senior level Web Developer with 3 years of experience lever…
possess staying power: the ability to keep digging in the well for ideas and solutions to any ever-changing directions. The Retail Writer must have the fortitude to remain committed to the project for the long haul...to…
Looking for W-2 CANDIDATES ONLY who are authorized to work in the United States without the need for sponsorship. H-1B Transfers AND CORP-TO-CORP Candidates WILL NOT BE CONSIDERED for this position Title Role: Front-end…
Job Title: Service Advisor Department : Service Supervisor: Service Manager Summary Description Intake of customer vehicles, diagnose problems and service needs; sell service and/or parts and communicate job status to cu…
Identifies exciting opportunities for adopting new technologies to solve existing needs and predict future challenges. Grows technical capabilities and expertise and provide guidance to other members on the team. Skills…
Stefanini Group is hiring! Stefanini is looking for a Back-end Developer(Dearborn, MI/Palo Alto, CA) For quick apply, please reach out to Adil Khan at (***) ***-****/ ***email_hidden*** We are looking for a highly motiva…
development responsibilities for the entire technology stack and agile product teams in the company’s digital factory. Facilitates broader technical activities (e.g. DevOps, database processes, etc.) and collaborates wit…
This position will operate on a remote, contractual basis. Are you an experienced blogger with a knack for cutting through the fat and extracting the beating heart of a story in a flash? Oh, and do you have a passion for…
part-time role (10–15 hours/week) where you will interact directly with clients. You will participate in client meetings, explain technical details in plain English, and help bridge the gap between non-technical clients…
Job Summary Service Writer at Ed Rinke Chevrolet Buick GMC is a full-time sales role in the Automotive industry that provides excellent compensation and benefits to motivated and customer-focused individuals. This indivi…
automated workflow integration. By combining a designer’s eye, a writer’ s ear, and a technologist’s comfort with systems, the Content... ...efficiency. Serve as a bridge between creative concept and technical execution,…
What technical writers earn in Detroit
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $25–$34 | $51k–$70k |
| Mid level | $34–$45 | $70k–$93k |
| Senior | $44–$58 | $91k–$121k |
Adjusted for the Detroit 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 Detroit?
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.