$83.3k - $125k
leading scientific organization making meaningful contributions to global health, environmental protection, and food safety. As a Technical Writer III, you'll create clear, concise documentation that enables our customer…
Engineering & IT · Boston, MA
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.
71
Open roles today
$34–$80/hr
Typical pay range
$112k
Median, full-time
9
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 71 · sorted by freshness
$106.9k - $147k
end server management. Begins to influence department’s strategy. Makes decisions on moderately complex to complex issues regarding technical approach for project components, and work is performed without direction. Exer…
$99k - $225k
Full Stack DeveloperThe Opportunity:We’re seeking a highly skilled and motivated Full Stack Developer to join a small, high-impact team supporting Intelligence Community operations in the CBRN mission space. This is a un…
Company DescriptionBy working at Harvard University, you join a vibrant community that advances Harvard's world-changing mission in meaningful ways, inspires innovation and collaboration, and builds skills and expertise.…
$191k - $253k
exfiltration pipelines.Work directly with program teams and customers as they build real missions on your products.Contribute to technical leadership, design clarity, and long-term maintainability across a growing softwa…
requirements, in line with guidance provided Facilitate software application design discussions, and document design decisions to guide the technical team towards building software solutions Participate in coding and int…
Skip To Main ContentBack to SearchOffice in United States of America: BostonLooking for something else?Find a vacancy that works for you. Send us your CV to receive a personalized offer.Find me a jobWe’re seeking a .NET…
$125.7k - $203.1k
Please note this posting is to advertise potential job opportunities. This exact role may not be open today but could open in the near future. When you apply, a Cisco representative may contact you directly if a relevant…
Job Tittle: Technical Writer Location: Lexington, MA Background: Â This is a dynamic engineering environment where design modifications are always in flux. The primary documentation task is to produce comprehensive assem…
$40 - $49 per hour
If you’re looking for a rewarding career, a place to call home, apply with us today! Job Description As a CMC Technical Writer, you will have an integral role in Late-Stage Lipids Technical Transfer and Process Chemistry…
$94.3k - $160.3k
organization, a global team that creates the written and multimedia technical content that helps our customers understand and unlock the... ...Ability and eagerness to demonstrate leadership by mentoring other writers, a…
$95k - $174.2k
To create revolutionary, story-driven RPGs which go straight to the hearts of gamers — this is our mission. Want to dive deeper into our company’s culture? Explore our social media and check out our YouTube channel and B…
02
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.
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 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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.