Developer Relations
1 нед. назад
120k–175k USD / yearUSA
technical writingapi
Working closely with founders and customers to create technical content and support users to succeed with the platform.
Обязанности
- You’ll be working closely with our founders, early team, and customers. We’re looking for someone who can deeply understand the platform and help our users become wildly successful. This role is perfect for someone who has a technical background but loves teaching, writing, and building tools and resources that make other builder's’ lives easier.
- You’ll create high-quality technical content, like docs, guides, videos, and training materials, and be a key voice in making an amazing experience for builders from first touch to full adoption.
- Become a subject matter expert and help make every developer touchpoint world-class.
- Write technical content including tutorials, guides, and example use cases.
- Create and maintain documentation that’s clear, accurate, and easy to use.
- Record educational videos and walkthroughs that make using easy and fun.
- Build demo apps and sample integrations that show off the power of .
- Work with customers, support, and product teams to identify pain points and turn them into helpful content.
- Help drive community engagement and support our customers.
Требования
- You work hard and are excited to roll up your sleeves, build something you’re proud of, and take ownership.
- You’re a clear, concise communicator—whether you’re explaining code, writing docs, or recording a quick tutorial.
- You’re energized by helping builders solve real problems, and you care about getting the details right.
- You’re eager to learn about how API-first companies build and scale their products.
- Able to work in office 5 days a week in NYC
- Strong technical background (APIs, JavaScript)
- Excellent writing skills—especially technical writing
- Comfort creating videos, walkthroughs, or live demos
- Experience working in DevRel, documentation, or technical content roles
Другое
- You can’t work hard right now.
- You need a fully defined structure/playbook to be effective.
- You’re not excited about writing, educating, or supporting other developers.
- Intro call
- Take-Home Assessment (write a short guide / quick tutorial)
- Presentation of Assessment
- Meet in person
- Reference calls