Technical Writer, iwoca

• 1–3 years of experience of writing or editing in a technical field
• Familiarity with the software development lifecycle
• Ability to influence people without formal authority

Desirable

• The Knowledge Management team maintains iwoca’s internal documentation, which is primarily used by developers, analysts, and product managers, but also relied on by the wider company
• The team looks after a docs-as-code project that’s three years old, growing steadily, and supported by senior management
• There are already two technical writers—you’d be the third
• Iwoca’s technical writers are part of the Core Systems team, which provides the tools, infrastructure, and shared services that our product-focused development teams rely on
• There are ten more engineers in the Core Systems team (working in groups that focus on DevOps, data systems, systems architecture)
• Most of us work remotely, but we attend a (virtual) daily meeting, enjoy quarterly team meals in London, and socialise with each other at company parties twice a year
• As a technical writer on the Knowledge Management team, you will create and curate the internal documentation that supports iwoca’s engineering and product development. iwoca is growing fast and launching new products
• That means more readers, more systems to document, and more legacy content to renew as we integrate those new systems
• Influence and collaboration:
• The project has around 50 monthly contributors from 20 different product-focussed teams; you’ll need to encourage documentation to happen quickly and support it through the publishing cycle
• You’ll champion a culture of writing things down—essential as iwoca scales and communication debt compounds. We have around 100 developers, data scientists, and product managers—and we believe all of them should be writing good documentation
• You'll model high standards for clarity, rigour, and thoughtful communication. As a reviewer, you’ll need to do a lot more than just correct typos
• Technical variety
• Our documentation covers business concepts, analytical models and tests, and back-end, front-end, database, and infrastructure systems
• The team also supports other teams across the business, from Product Design to People Operations, and takes on other ad-hoc projects
• The docs-as-code project is mature, but there's an opportunity to automate some of the boring stuff, if you have the skills
• Autonomy
• The team plans its work in GitLab issues, but you’ll be trusted to choose which ones to work on according to impact. You’ll need to balance quick wins with long-term improvements and timely reviews for other contributors
• You'll be trusted to spot what’s missing or unclear and fix it without waiting for permission
• You’ll decide when to raise the bar—and when documentation is finished

• We’re open-minded, so definitely include your salary goals with your application