Technical Writer
Content + Source + Freshness • 11 Dec 2025 • 95% confidence
Offer value
Moderate value due to essential documentation role but lower compensation transparency.
- Key role improving technical documentation.
- Collaboration with engineering staff enhancing clarity.
- Opportunity for gradual career growth.
Pros
- Highly relevant position with broad implications for software quality.
- Opportunity to work closely with development teams.
- Scope for improving documentation standards and user experience.
Cons
- Lack of clarity around salary potential.
- Possibility for monotonous tasks in documentation.
- Limited opportunities for upward mobility.
Who it's for
Mid-level • Remote / On-site
Good fit
- Technical writers with software development knowledge.
- Candidates interested in improving tech documentation.
- Writers with attention to detail and technical skills.
Not recommended for
- Those uninterested in technical aspects.
- Creative writers seeking non-technical roles.
- Individuals lacking experience in collaboration with tech teams.
Motivation fit
Key skills
About the job
EvoPlay is looking for a skilled technical writer with experience in documenting code. The ideal candidate will be responsible for creating well-structured and understandable documentation that improves code interaction for our developers.
Requirements:
• 2+ years of experience in the position of Technical Writer;
• 2+ years of experience working with the Swift programming language;
• Experience with JIRA/Confluence;
• Deep understanding of software development processes and related technical concepts;
• Ability to work independently and in cooperation with technical teams;
• Attention to detail and commitment to create high-quality and user-friendly documentation.
Nice to have:
• Experience in writing unit tests;
• Experience in the position of QA Engineer will be an advantage. Responsibilities:
• Create and maintain complete code documentation;
• Collaborate with the development team to translate technical information into user-friendly manuals;
• Regularly update documentation to reflect changes in features and software updates;
• Make a description of the documentation directly in the code itself;
• Ensure documentation meets standards and best practices, ensuring clarity and consistency.
