This is an opportunity to join a technical writing team within a fast-growing, independent software company. Our client develops Web-based financial trading software for the world’s largest financial institutions. They have an immediate vacancy for a Junior Technical Author/API Documentation Writer with a passion for technical communication.
You will developing end-user documentation for a range of products, producing user manuals, online Help and API documentation.
You need to have one years experience working in an IT environment, and some experience of writing technical documentation. You also need to be able to demonstrate you have excellent verbal and written communication skills, and outstanding attention to detail.
You will have:
- experience of writing technical documentation from scratch
- familiarity with Agile development approaches
- some knowledge of Java, C, C# or C++
- an understanding of Web application development tools and methods: HTML, DOM, CSS
More information: #4134 Junior Technical Author/API Documentation Writer, City of London, £28K DOE
This is an opportunity to join a technical writing team within a fast-growing, independent software company. Our client develops Web-based financial trading software for the world’s largest financial institutions. They have an immediate vacancy for a Technical Author with a passion for technical communication.
You will developing end-user documentation for a range of products, producing user manuals, online help and API documentation.
See #4133 Technical Author, City of London, £32K-£37K DOE
Here are details on the most recent vacancies we have on our books.
This is an opportunity to join a friendly team of authors, working for a large and progressive company. Our client needs a technical writer to join its team of writers who can write user guides, Help files and workbooks for scientific instruments.
You’ll need to have at least 2 year’s experience in technical writing and, ideally, a science (esp. chemistry) background. It would help if you have some experience writing standard operating procedures in a regulated environment.
You need to be skilled in using:
- Authoring tools such as Madcap Flare, RoboHelp, FrameMaker or Adobe Acrobat.
- Graphics tools such as Corel Photo-Paint, CorelDraw or PaintShop Pro.
You also need to be experienced in user-centred design writing techniques, such as user personas and task-based writing
You’ll be working on-site, at the client’s offices in South Manchester.
To apply, please email us a copy of your CV.
We have a revised job description for vacancy #4124 Lead Technical Author, City of London, to £50K DOE
This vacancy would be suitable for a graduate who would like to start a career as a Technical Author:
#4109 Graduate Trainee Technical Author / Trainer, Leeds, £22k-£26K
We have clients looking to recruit Technical Authors for the following positions:
This is a nice (please excuse the pun) vacancy for a Technical Author who would like to live in France’s “Silicone Vallé”, the Côte d’Azur:
#4093 Technical Author / Writer Nice, France €35K-€45K
We’re looking for a contract Senior Technical Author/Writer to work for us on a 8 month contract near Amsterdam. Unfortunately, the person who was working on this project has been taken ill. For more details, see our job posting.
We’ve a client looking to recruit a Technical Writer/Software Tester, which they are having difficulties filling (see
#4084 Technical Author/Software Tester, Surrey, £25K-£35K)
As part of the process of promoting this vacancy, we posed the following questions in a forum on LinkedIn for testers (Software Testing & Quality Assurance) and in a forum for Technical Authors (Technical Writer Forum):
What do Software Testers feel about hybrid roles – where you’re writing the user documentation and conducting the testing? We’ve a client looking for such a person, which is why I ask.
What do you feel about hybrid roles – where you’re writing the user documentation and conducting the testing?
We’ve a client looking for such a person, which is why I ask.
There were a lot of responses. In general, the Software Testers felt it should be two separate roles, whereas the Technical Authors felt it could work as an information hybrid role. They were more confident they could do both roles than the software testers. There were some concerns, however, over it extending the critical path of projects.
I suspect the roles are merged more often than people imagine, especially in smaller companies. What do you think?