01
Write clear, technically accurate tutorials, guides, references, and learning resources.
Back to careers
Content · Open role
Technical Writer
Turn complex technology into documentation developers can understand, trust, and actually use.
documentation.mdx
JavaScript fundamentals
Understand the event loop
JavaScript uses an event loop to coordinate asynchronous operations...
console.log("Learn by building.");
Explain the concept first. Then show the code.
Technical review
RoleTechnical Writer
LevelJunior / Mid / Senior
Work modelRemote-first
Primary focusDeveloper Education
The opportunity
Make technology easier to understand.
CodeHarborHub is building an open-source learning ecosystem for developers — from their first HTML page to advanced software engineering, AI, and computer science.
As a Technical Writer, you will help create the educational layer that makes that ecosystem useful. You will research, explain, structure, test, and continuously improve technical content.
Your work will not simply fill pages. It will help learners understand why something works, how to use it, what can go wrong, and where to go next.
You will work closely with engineers, contributors, and educators to turn technical knowledge into high-quality learning experiences.
What you'll do
Own the content from research to publication.
You will work across writing, technical research, information architecture, quality assurance, and open-source collaboration.
02
Transform complex programming concepts into beginner-friendly explanations without losing technical depth.
03
Work with engineers and subject-matter contributors to validate technical accuracy.
04
Create structured learning content for HTML, CSS, JavaScript, React, TypeScript, Git, Linux, computer science, AI, and related technologies.
05
Improve existing documentation based on learner feedback, analytics, technical changes, and content quality reviews.
06
Design content structures that help learners move from fundamentals to advanced concepts.
07
Use examples, diagrams, code snippets, exercises, and practical projects to make technical concepts easier to understand.
08
Maintain consistent terminology, tone, formatting, navigation, and information architecture across documentation.
09
Contribute to open-source documentation workflows through GitHub issues, pull requests, reviews, and discussions.
10
Help establish editorial standards, documentation guidelines, and content quality processes for CodeHarborHub.
Required
What you should bring
- Strong written communication and the ability to explain technical concepts clearly.
- Good understanding of web development and modern software development concepts.
- Hands-on familiarity with technologies such as HTML, CSS, JavaScript, Git, or React.
- Ability to research technical subjects and verify information before publishing.
- Ability to write for developers with different levels of experience.
- Strong attention to structure, readability, consistency, and technical correctness.
- Comfort working with Markdown, MDX, Git, and GitHub.
- Ability to understand and review source code, examples, and technical implementations.
- Ability to receive feedback and iterate on content.
- Curiosity, ownership, and a genuine interest in helping people learn technology.
Bonus
Great if you also have
- Experience writing developer documentation or technical tutorials.
- Experience with Docusaurus, VitePress, GitBook, or similar documentation platforms.
- Experience with React, TypeScript, Node.js, or frontend development.
- Knowledge of SEO and content information architecture.
- Experience creating Mermaid diagrams or other technical visualizations.
- Experience contributing to open-source projects.
- Experience with documentation testing, broken-link checking, or CI workflows.
- Understanding of accessibility and inclusive technical writing.
Our writing standard
We don't just publish words. We build understanding.
Every piece of content should have a clear purpose and make the learner's next step easier.
Clarity over complexity
Explain difficult concepts in a way that makes the reader feel capable, not overwhelmed.
Accuracy matters
Examples and explanations should work in the real world, not just look good on the page.
Write for humans
Understand what learners are trying to accomplish and structure content around their actual needs.
Keep improving
Great documentation is never finished. We continuously refine it based on feedback and technology changes.
How content gets built
A writing workflow designed for technical quality.
Great technical content combines research, writing, engineering validation, and continuous improvement.
01
Research
Understand the technology, audience, prerequisites, common mistakes, and learning objective.
02
Structure
Turn the research into a logical content structure with clear progression and useful examples.
03
Write
Create concise explanations, examples, diagrams, exercises, and practical learning material.
04
Validate
Test examples, verify technical claims, review links, and get feedback from technical contributors.
05
Publish
Ship the content through GitHub-based workflows and make it easy for learners to discover.
06
Improve
Use feedback and real learner behavior to continuously improve the content experience.
Open source advantage
Your documentation can become part of the public web.
CodeHarborHub is built in the open. Writers collaborate through GitHub, review technical content with contributors, and improve resources that developers can discover and use freely.
README.md
# Learn by buildingBuild practical knowledge through tutorials,
roadmaps and projects.```javascriptconst learner = {
learn: true,
build: true
}```
roadmaps and projects.```javascriptconst learner = {
learn: true,
build: true
}```
Questions
Before you apply.
A few things candidates commonly want to know about technical writing at CodeHarborHub.
Not necessarily. Strong technical understanding and the ability to explain concepts clearly are more important than having a specific job title in your previous experience.
Yes. Developers who enjoy teaching, documentation, tutorials, code examples, and explaining technical concepts can be a particularly strong fit.
No. You should have solid technical fundamentals and be comfortable learning new technologies. You are not expected to be an expert in every subject.
Yes, but the role is broader than beginner tutorials. Content can range from introductory explanations to advanced guides, references, workflows, and project-based learning.
Yes. Documentation contributions are an important part of the CodeHarborHub ecosystem, and public contributions can demonstrate your ability to work with technical content and collaborative workflows.
We look at technical accuracy, clarity, structure, audience awareness, examples, research ability, communication, and how effectively the content helps a reader accomplish something.
Write something useful
Help the next developer understand what you already know.
If you enjoy learning technology, breaking down difficult concepts, and helping other developers grow, we'd love to see your work.
A writing sample, technical article, documentation PR, portfolio, or open-source contribution can help demonstrate your skills.