Content Writer

What This Role Exists to Do

The content team publishes to an audience of technical leaders and business decision-makers: CTOs and IT Directors who evaluate architecture decisions, and Founders, COOs and Operations leaders who are accountable for technology outcomes without a technical background of their own.

This role produces the first drafts that sit underneath that output. You take a written brief, do the reading, and deliver a draft that is clean, on topic, and written for the reader named in the brief. The brief comes to you. The voice is already defined. Your job is to write well inside both.

What You Will Own

• First drafts of blog posts and long-form articles, written from briefs set by the Content and Thought Leadership Specialist
• Client case studies and project write-ups, working from delivery team inputs
• Social media copy for the 2Base company channels
• Website page copy and updates
• Research and source gathering behind longer pieces, including reading the technical material well enough to summarise it accurately
• Publishing and scheduling support once a piece has cleared the quality gate

What You Will Not Own

• The 2Base content voice: it is already defined and documented, and you write within it
• Content briefs: the Content and Thought Leadership Specialist writes them, you write to them
• SEO keyword selection: the Organic Growth and SEO Specialist sets this
• Visual design of content assets: the Visual Designer owns this
• Distribution and channel decisions: the Marketing and Growth Lead owns this
• Final publishing approval: nothing goes live without passing the content quality gate

Requirements

Experience

• 0 to 2 years of writing experience. Fresh graduates are welcome and are a core part of the target profile.
• Any discipline. We do not require a journalism, English or communications degree.
• Evidence of writing, in whatever form you have it: an internship, freelance work, a campus publication, a personal blog, a newsletter, or a piece written for a university project.
• If you have no published work at all, the application instructions below tell you what to send instead.

Writing Ability

• Writes clean, correct English. Grammar, punctuation and sentence construction are sound before an editor sees the work.
• Can write to a brief: hits the topic, the named reader and the length asked for, without being chased.
• Can explain something to a reader who does not already understand it, without either talking down to them or hiding behind jargon.
• Reads their own work back and fixes it before submitting.

Mindset

• Genuinely interested in technology. You do not need to know how software is built. You do need to want to find out.
• Takes edits without taking them personally. This role is heavily edited by design for the first 90 days.
• Reliable on deadlines, and says so early when something will be late.
• Uses AI tools as a drafting aid and can say clearly where the tool stopped and their own thinking started.

What We Are Not Looking For

• Writing that has been generated and lightly edited. We check for this, and it is the fastest route to a decline.
• Candidates who are interested in writing in the abstract but have no curiosity about the subject matter.
• Anyone who cannot accept a rewrite.
• Candidates looking for a short engagement to add a line to a CV. This role assumes you are here to learn the craft properly.

An Honest Note on This Role

This is an entry-level role with real output. It is not a shadowing role and it is not an observation period. You will be given briefs and you will be expected to deliver against them.

It is also closely supervised. The brief structure, the voice standard and the quality gate already exist, so you learn inside a working system rather than inventing one. Expect a great deal of editing in your first three months, and expect the reasoning behind each edit to be explained to you.

If you want to be an accomplished technology writer in two years and you are willing to be edited hard to get there, this is a good place to start. If you want to publish your own work largely unchanged, it is not.

How to Apply

Send your CV and one writing sample to [email protected] with the subject line: Content Writer, followed by your name.

If you have no published sample, send a 200 word piece instead, explaining one benefit of automated software testing to an operations head at a client company who does not write code.

Benefits

A growth-driven environment with opportunities to lead, innovate, and upskill continuously.