Job Title: Remote Data Entry Specialist (Typist) Company: DLN Consulting Group Location: Remote Job Type: Full-Time / Part-Time Description DLN Consulting Group is hiring a Remote Data Entry Specialist to accurately inpu…
Technical Writer jobs in Boston, MA
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 112 · sorted by freshness
sales teams to deliver impactful, high-quality content across channels and audiences. The successful candidate is an exceptional writer, strategic thinker, and project manager with a knack for breaking down complex topic…
We are looking for an experienced Grant Writer (Freelance, Remote) to support a nonprofit organization dedicated to improving the lives of individuals and families affected by Barth syndrome, an ultra-rare disease. The o…
We are digital marketing agency seeking a web developer who exhibits strong attention to detail and thrives in a dynamic environment. We’re looking for someone who is passionate about what they do and enjoys working with…
Our responsibilities include product operations training and adoption and user documentation. We are seeking an experienced Technical Writer to create and maintain user documentation across our diverse business lines. We…
essential to operating safely training our team and meeting the expectations of our regulators and customers. We are seeking a Technical Writer to own the documentation that underpins ATPs engineering projects and manufa…
Senior Technical Writer Employment Type: Full-Time, Experienced Department: Technology Support CGS is seeking an experienced Senior Technical Writer to provide consultative, analytical, and documentation support for a la…
contributor into decisions about what we create and why, edit writers and subject-matter experts into work that holds up to a reader... ...every asset ~ Genuine curiosity and the discipline to learn a technical domain de…
OVERVIEW As part of the Client Services Department, the SEO Specialist plays a key role in the expansion and growth of the division. They work alongside Sales to pitch digital marketing services and data-driven strategie…
Our responsibilities include product operations, training and adoption, and user documentation. We are seeking an experienced Technical Writer to create and maintain user documentation across our diverse business lines.…
Our responsibilities include product operations, training and adoption, and user documentation. We are seeking an experienced Technical Writer to create and maintain user documentation across our diverse business lines.…
documentation, and explain why each source matters. Create supporting materials: preparatory (non-credit) modules for learners without a technical background, a program glossary, templates and worked examples. Collaborat…
What technical writers earn in Boston
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$46 | $70k–$96k |
| Mid level | $46–$62 | $96k–$128k |
| Senior | $60–$80 | $125k–$166k |
Adjusted for the Boston 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 Boston?
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.