Experience Required/Desired Skills Skill Required /Desired Amount of Experience Experience in technical writing, digital communications or web content. Required 2 Years WCAG 2.1 Level AA compliance knowledge...
Technical Writer jobs in Indianapolis, IN
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 17 · sorted by freshness
reputation for exceptional achievement and consistently recognized as a leader in the industry! Our firm maintains a high level of technical expertise with the luxurious perks and schedule flexibility of a private compan…
Work for Indiana Begin a fulfilling career with the State of Indiana by joining one of the largest employers in the state, offering a range of opportunities across 60+ agencies. At the state, you'll find competitive comp…
Training & Career Advancement Chaplain Care Support Available Job Description Job Title: Automotive Service Advisor / Writer Location: 13048 Publishers Drive Fishers, IN 46038 Job Overview: As an Automotive Service Advis…
At Real Chemistry, making the world a healthier place isn’t just an aspiration—it’s our everyday reality. Our drive to transform healthcare is informed by our blend of deep scientific expertise, human-centred creativity,…
At Real Chemistry, making the world a healthier place isn’t just an aspiration—it’s our everyday reality. Our drive to transform healthcare is informed by our blend of deep scientific expertise, human-centred creativity,…
stronger. For more information, visit or follow MMS on LinkedIn . Responsibilities Under minimal supervision, the Medical Writer will critically evaluate, analyze, and interpret the medical literature to select primary r…
Job Description Job Description Description: Description Meyer Distributing is looking for a Front End Developer to join our Indianapolis, IN team - we are hiring immediately! Meyer Distributing is a leader in automotive…
development and SQL queries Help build APIs and backend services Develop basic UI components Collaborate with team members on technical solutions Write clean and maintainable code Participate in testing and code reviews…
Job Description Job Description Director, Social Media This is a full-time, in-person position located in Indianapolis, Indiana. About Us Audiochuck is a fast-growing, dynamic company driven by our mission to tell the ri…
backend services, APIs, and database systems using .NET and SQL Server Develop responsive, high-performance user interfaces Lead technical design discussions and system architect decisions Write clean, maintainable, high…
friendly, functional, and meet organizational needs. User Support and Training: Provide support and training to end-users, addressing technical issues and enhancing user knowledge of SharePoint features and best practice…
What technical writers earn in Indianapolis
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 Indianapolis 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 Indianapolis?
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.