$73k - $132k
concepts through rapid visualization, prototyping, and reduced reliance on physical samples. Collaborate cross-functionally with technical artists, merchandising, marketing, digital teams, and external partners to ensure…
Engineering & IT · Minneapolis, MN
Technical Writer jobs in Minneapolis, MN
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.
22
Open roles today
$27–$64/hr
Typical pay range
$89k
Median, full-time
3
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 of 22 · sorted by freshness
troubleshooting and deployment experience with strong understanding of transforming business and functional requirements into efficient technical solutions Experience with system integrations, optimizing performance and…
$60k
Role Location: Greater Minneapolis/St. Paul, MN (partial in-office requirement) About Bold Orange: Bold Orange is a customer experience company. We believe authentic human connections are the single most important driver…
$78.3k
Instructional Designer to actively assist with the development and execution of innovative training programs within our Capital Equipment Technical Services department. This individual develops and conducts product train…
$84k - $100k
Copywriter Duke Cannon Supply Co. is a growth-oriented CPG company that operates with an entrepreneurial mindset – and has become one of the fastest-growing brands in the men’s grooming category. Our mission is to better…
$65k - $85k
Description:: Under the direction of the Technical Writing Manager, the Technical Writer serves as a subject matter contributor for product documentation, developing and maintaining clear, customer-focused content that s…
$75.19 - $90.22 per hour
troubleshooting efforts, and ongoing platform enhancements Contribute to iterative software delivery by participating in story sizing, technical design discussions, and solution planning Follow engineering best practices…
$112k - $180k
Description Arrowwood Heart is on the lookout for a talented 3D Character Artist to join our creative team, working remotely from Minneapolis. This full-time position is ideal for entry-level artists ready to unleash the…
Service Writer Department: ServiceReports To: Service Manager Overview The Service Writer - Second Shift is responsible for supporting the daily operations of the service department by accurately documenting customer con…
delivering high-quality products that meet client needs and business goals. As a leader on the development team, our Developers ensure the technical execution of projects, from architecture to estimation to completion. T…
$105.6k - $144k
Description Arrowwood Heart is looking for a creative and passionate VFX Artist to join our team in Minneapolis. This full-time, remote position provides an exciting opportunity to contribute to innovative visual project…
$96k - $134.4k
Description Arrowwood Heart is looking for a creative and passionate Animator to join our team in Minneapolis. This full-time, remote position offers an exciting opportunity to contribute to engaging visual storytelling…
02
What technical writers earn in Minneapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $27–$37 | $56k–$76k |
| Mid level | $37–$49 | $76k–$102k |
| Senior | $48–$64 | $100k–$133k |
Adjusted for the Minneapolis 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 Minneapolis?
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.