Senior Technical Writer

The company

Small businesses move fast. Opportunities often don’t wait, and cash flow pressures can appear overnight. To keep going, and growing, SMEs need finance that’s as flexible and responsive as they are.

That’s why we built iwoca. Our smart technology, data science and five-star customer service ensures business owners can act with the speed, confidence and control they need, exactly when it’s needed.

We’ve already cleared the way for 100,000 businesses with more than £4 billion in funding. Our passionate team is driven to help even more SMEs succeed, through access to better finance and other services that make running a business easier. Our ultimate mission is to support one million SMEs in their defining moments, creating lasting impact for the communities and economies they drive.

The Knowledge Management team maintains iwoca’s internal documentation — the Handbook — used by developers, analysts, product managers, and increasingly by the wider company. The project is four years old and has around 60 monthly contributors from across the business. The team has two other technical writers: you’ll be the third.

The documentation scope is expanding. iwoca is launching products on new, separate architectures — which means documentation can be better structured from the start. An internal AI chat uses the Handbook as its knowledge base, so well-organised content has a direct, visible impact on how the whole company finds information. There are also active projects to bring operations and people documentation into the Handbook.

The Knowledge Management team is part of Core Systems, which provides the tools, infrastructure, and shared services that product-focused development teams rely on. There are ten more engineers in Core Systems, working in groups that focus on Dev Ops, data systems, and systems architecture. The team is mostly remote, with a daily virtual meeting, quarterly team meals in London, and company parties twice a year.

• The current documentation is aimed at developers, yet half the company reads the Handbook each month and a third use it every day. About half of iwoca’s developers contribute to it in any given month. The documentation you maintain and improve has a daily, visible effect on how people work — this is not documentation that sits on a shelf never to be read.
• An internal AI assistant uses the Handbook as its knowledge base, so the quality and structure of what you write directly determines how well the whole company can find answers.
• Document new products from day one, setting the standard before complexity accumulates.

• Run documentation migration projects end-to-end: scope what needs to move (and improve), get buy-in from the team that owns it, and deliver it — from operations documentation to people documentation and beyond.
• Choose your work based on impact. You decide when to raise the bar and when documentation is finished.

• Shape how new departments adopt the Handbook. Work with teams that have never used Git, explain why their knowledge belongs in the Handbook, and either run the migration for them or support them doing it themselves.
• Mentor another technical writer — raise their standard by reviewing their work, sharing approaches, and role‑modeling how to run projects independently.
• Advocate for culture change: the documentation practices that worked for a startup of humans do not serve a scale-up of AI‑builders. You’ll help iwoca recognise that and adapt.

• 5+ years of experience writing or editing technical documentation.
• Proficiency with Git — you’ll use it daily and help others learn to use it.
• Experience running documentation projects end-to-end: scoping, stakeholder buy‑in, and delivery.
• Experience influencing teams outside your own to adopt new practices or ways of working.
• Experience using AI tools to scale editorial and documentation work — not just writing assistance, but directing AI for reviews, migration tasks, and workflow automation.

• Experience documenting financial services or lending.
• Programming experience (Python, shell scripting).
• The ability to influence people in different teams who…