message, and delights our users. Job responsibilities Help define Chase’s motion design language and guide its application within technical and accessibility parameters. Create high-quality animation proposals that celeb…
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.
220
Open roles today
$35–$83/hr
Typical pay range
$116k
Median, full-time
10
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 220 · sorted by freshness
$74 - $85 per hour
Tubi's B2B owned-and-operated channels, and shepherding deliverables from brief through launch. The ideal candidate is an excellent writer and editor, a strong project manager, and a confident cross-functional partner wh…
$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…
$140k - $215k
Unified Detections Management (UDM) system, ensuring a consistent and comprehensive detection experience for all customers.Serve as a technical leader, mentoring mid-level and senior engineers, and driving cross-function…
$50 - $90 per hour
Greetings from ProIntegrate, A Micro1, Partner. We have Excellent remote opportunity for VFX Artist / 3D Animator(50-90 USD ) per hour - Remote Work any time, weekends or when you have time, completely flexible. This rol…
$155k - $180k
services with evolving, incomplete, or inconsistent data.Strong communication skills and the ability to work effectively with non- technical stakeholders, including attorneys and investigators.Sound judgment and discreti…
services.Develop business logic and database solutions.Collaborate with Product, QA, DevOps, and Engineering teams.Participate in technical design, code reviews, testing, troubleshooting, and performance optimization.Int…
$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…
products in a secure, stable, and scalable way. You are responsible for carrying out critical technology solutions across multiple technical areas within various business functions in support of the firm’s business objec…
$25 per hour
organizing and supervising on-site student showcases, workshops, and animation screenings. Offer assistance with art displays and technical execution to ensure successful presentations. ~Departmental Collaboration: Colla…
$200k
full lifecycle of product development, from ideation through to delivery, playing a key role in shaping both the user experience and technical roadmap while utilizing modern AI-powered tools to accelerate innovation and…
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…
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.