Please submit your application through this posting only. We're unable to review applications or follow-ups sent via email, direct message, or website inquiry. ABOUT NEN CREATIVE Nen Creative partners with tech startups…
Engineering & IT · New York, NY
Technical Writer jobs in New York, NY
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.
506
Open roles today
$35–$83/hr
Typical pay range
$116k
Median, full-time
2
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 506 · sorted by freshness
ASR is seeking an experienced Senior Technical Writer, Office Supplies and Furniture Branch for an exciting opportunity supporting engineering technical support services for the U.S. General Services Administration’s Off…
millions across digital channels. Job Summary Help define Chase’s motion design language and guide its application within technical and accessibility parameters. Create high-quality animation proposals that celebrate own…
$62k - $85k
our data and research practice. This person will help make all of that possible. What You Will Be Doing: Creative Craft & Technical : Create motion graphics and animated content for digital and social platforms. Work wit…
$2,500 - $5,000 per month
work will be seen by 10M+ people every. single. week. About Shown Media Emmy winners, ex-Mr. Beast filmmakers, and the most technically gifted motion designers on the planet. We engineer viral launches for the founders h…
$92.8k - $127.6k
At Bose Corporation, we believe sound is the most powerful force on earth — and for over 60 years, we have been a company built on innovation, excellence, and independence. Privately owned, fiercely customer-focused, and…
$115k - $170k
Harvey, Rippling, Vanta, LinkedIn, Monday.com, Nvidia, and Bridgewater. About the role We’re seeking a detail-oriented Technical Docs Writer who can take complex technical concepts and transform them into easily understa…
$105k - $183k
Figma is growing our team of passionate creatives and builders on a mission to make design accessible to all. Figma's platform helps teams bring ideas to life-whether you're brainstorming, creating a prototype, translati…
$90k - $100k
on proven instructional design methods, and collaborate with course developers. As a course developer, you will be very skilled in technical course development and convert instructional materials into interactive/engagin…
$70k - $95k
social promos and explainer videos to polished corporate interviews. This role offers the perfect balance of creative freedom and technical precision, allowing you to showcase your versatility across a diverse client por…
We request candidates to provide writing samples with their application We are seeking a skilled Technical Writer to join our IT department. The ideal candidate will be responsible for creating clear, concise, and user-f…
$130k - $145k
Premiere Pro, After Effects, Figma, Adobe CS, etc.) ~ You have a strong portfolio that demonstrates your storytelling abilities and technical skills ~ You're comfortable with lots of ambiguity and can work autonomously ~…
02
What technical writers earn in New York
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$48 | $73k–$99k |
| Mid level | $48–$63 | $99k–$132k |
| Senior | $62–$83 | $129k–$172k |
Adjusted for the New York 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 New York?
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.