Junior Technical Writer - Manila

SafetyCulture; Manila; On-site; PHP 420,000 - 640,000; Full time

Job summary

Mitti by SafetyCulture is hiring a Technical Writer to maintain Help Center articles and release documentation for assigned product teams. You will ensure content accuracy and relevance for customers and AI support tools.

You will collaborate with product, engineering, and learning specialists, producing clear product copy and knowledge notes for releases, while leveraging approved AI tools to boost output without compromising quality.

Qualifications

• Strong writing and communication skills, translating technical concepts into clear language.
• Organizing information across Help Center articles, release notes, short-form copy.

Responsibilities

• Create, update, and archive Help Center articles for assigned product teams.
• Publish articles after review.
• Create knowledge notes for every release with context and links.

Skills

Strong writing & comms

Agile environment

Headless CMS exposure (advantage)

Product documentation

Job description

Why join us?

Mitti by SafetyCulture is a global tech company, just not the kind you're picturing. Our almost 1,000-person team builds tools that make work better for the three billion frontline workers who keep the world moving. We've got big tech scale, without the sign-off layers or corporate theatre. Every permanent team member gets equity, so when we grow, you do too. This next chapter is about scaling smart, powered by AI, a clear vision and real ownership.

Big tech impact, without the big tech ick.

Job description

Role purpose

This role exists to keep Help Center articles and release documentation for assigned product teams accurate, current, and ready for customers, so the Help Center remains a reliable source of information for customers and our AI support agent.

Key Responsibilities

• Creates, updates, and archives Help Center articles for assigned product teams, collaborating with an experienced peer on high-complexity work to make sure the approach and scope are sound.
• Publishes Help Center articles once they've been reviewed.
• Creates a knowledge note for every release from assigned product teams, covering what changed, why, platform context, and relevant links, including visuals.
• Works on product copy for assigned product teams.
• Partners with Customer Learning Specialists developing courses for their product area to keep content accurate.
• Uses approved AI skills as part of their daily workflow to increase output while maintaining quality, and flags unexpected outputs or gaps to their lead or an experienced peer.
• Contributes to internal documentation and team projects where relevant.

Technical Skills

Required skills and experience

• Strong writing and communication skills, with the ability to translate technical concepts into clear, customer-friendly language.
• Comfortable organizing and structuring information across Help Center articles, release notes, and short-form product copy.
• Familiarity working in an agile development environment, or a demonstrated ability to pick this up quickly.
• Exposure to a headless content management system is an advantage, not a requirement.

Behavioural Skills

• Proactive in staying close to their assigned product teams, following release cycles closely enough to flag documentation needs early.
• Open to feedback, treating content review as a way to build craft rather than as criticism.
• Comfortable working independently within a defined scope while knowing when to loop in an experienced peer.
• Curious about new tools and ways of working, including AI, and willing to build new habits into their workflow.

AI Skills

• Uses the team's approved AI skills as a default part of their daily workflow for drafting, reviewing, and administrative tasks, not as an occasional tool.
• Builds fluency over their first few months so AI-assisted work becomes second nature, while keeping content quality and accuracy as the priority.
• Flags unexpected AI outputs or gaps in existing tools to their lead or an experienced peer.

Success looks like

• Every release from their assigned product teams has a knowledge note published within the team's standard turnaround.
• Their Help Center article content consistently meets the team's quality bar, without repeated rework flagged in review.
• Assigned product teams loop them proactively, before release rather than after, on both documentation and product copy, and treat them as reliable partners.
• By month six, they've built a steady record of quality articles that their lead can consider for the reviewer qualification process.

Key stakeholders

• Lead Technical Writer
• Assigned Product and Engineering teams
• Customer Learning Specialists
• Support Operations Specialists

What This Role Is Not

• Does not independently own high-complexity Help Center articles; these require collaboration with an experienced peer.
• Does not review content until being considered for the reviewer qualification process at month six.
• Does not own developer documentation.
• Does not lead or own mobile app release notes.

What You Need To Know

• Office: Manila, two to three days a week (hybrid).
• Work hours: 6am to 3pm (aligned with Sydney business hours).

We're committed to building inclusive teams and cultivating a sense of belonging so our people can bring their whole authentic selves to work each day. We seek to make reasonable adjustments throughout our recruitment process to create an even playing field for all candidates. Thanks to the tireless efforts of the entire Mitti team we've built an incredible culture which has seen us recognised as a Best Place to Work in Australia , the US and the UK .

You can find out more about life at Mitti via Youtube , Twitter , Instagram and LinkedIn.