Hi all,

I just got a job with Roche in their Rotkreuz branch as a tech writer. Having spoken with them I know they are looking for 4 or so more new staff in the Rotkreuz office, and they are having trouble finding people. I have also been contacted for a similar position with Roche in Basel, where they are also searching for several tech writer staff to support their growing office.

The jobs are by 6mth contract, but they have staff there who have done consecutive contracts over the last 10 years. So there is that as a bit of security - they don't intend to kick you out after a short time.

They also said that as the office grows there will be permanent positions made to expand their core base of writers.

search contract Tech writer positions on www.hays.ch, and it will give a job description etc.

PM me if you'd like more details

Meanwhile I need to celebrate my new job with a glass of something...

Although I feel that I should know something about "technical writing" I don't, at all.

Would you care to explain exactly what the job entails and what sort of qualifications/education you need to be a proficient/successful technical writer? All my experience is in academics and so don't know much about industry.

I thought you were a scientist ? Have you written-up yet ?

From an engineering point-of-view it is likely to be something fun like: here is a instrumenation-monitoring rack, that we have developed to monitor turbine speed. Before we can sell it to other customers, we need a complete DRL document suite, everything from maintenance , reference manuals, setup procedures, user guides and so on.... and we have the information required to document it on this pile of cigarette packets here , here and here. Over here is a corridor of offices containing some bearded-engineers who will give you approximately three minutes of their time to help you in the task...

dave

Hi chemgoddess,

It is basically the "art" of working with software or hardware etc. systems and documenting anything from their contractual requirements and system specs to the training materials and end user manuals.

With Roche in Rotkreuz, I will be given a product to use and learn and then required to compile the standard operating procedures for the hardware product and accompanying software apps, as far as I know. This will later go on to coordinating translations through external sources and compiling them for delivery to end users.

The companies usually like you to have:
1. quals in their area of expertise (science in this case);
2. experience in their specific area (hospital or laboratory environments);
3. experience in writing documentation;
4. experience in tools like bog standard MSWord etc of course, but also tools like adobe framemaker, HTML & XML etc... Even these are being superceded though these days...

I got the job based on my qualifications in communication and research, 3 years tech writing exp, 5 years University lecturing in English language for international students, and having spent the last 5 months or so (with having no work permit) learning framemaker, HTML and XML to create online documents.

The manager who interviewed me said that the tools can be learned in your own time in parallel if you don't know them already.

Hope this helps

I've written a thesis, quite a few pubs and some grants. But all my experience is academia

It's just not something I'm familiar with. Geez, I'm a scientist not omniscient.


But yeah, that makes sense. I say "Duh" to myself. Someones gotta write the manuals for all the instrumentation I use on a day to day basis. Guess I just never thought about it.

Yes, thanks for those realities, DaveA... I *was* trying to recruit some help here!

Sure like all jobs they want everything done 5 minutes ago and engineers aren't always very coherent ...

But another reality is 145k stutz per year.

The main difference I suspect in your case would be that you are documenting someone elses work for a variety of audiences. This may or may not appeal. I enjoyed writing technical documents as long as the source information was available and in reasonable shape.

dave

Not so much. I want a cadre of grad students to do the research and write the papers. I'd rather be responsible for coming up with ideas and obtaining the money.

Sorry, it wasnt meant to discourage, its actually quite good work if it suits your temperament. Beyond the usual planning, communicating the ideas and doing the graft, the biggest challenge is squeezing the information from those that have it and often guard it jealously to preserve their position within the project. As soon as the multitiered-configuration and startup procedures are fully documented, anyone can do his job...

dave

This sounds a lot like my Job at the moment, except the people that knew anything have all buggered off overseas, and all the info is in German!

Hey Chemgoddess - just think of it as writing SOPs for dummies.....

Does it involve graphics ? Are you required to produce these too ?

dave

Puddycat - Congrats on the new job, enjoy that glass.

We (Swisslinx) are also working on Technical Writer contracts for the company mentioned.

Search on www.swisslinx.com for Technical Writer.

This is v similar to my role, only I get my hands dirty and have to develop + test stuff also aswell as co-ordinate docs ;-)

Is this not similar to a "senior business analyst?" Probably not, but a more general name?

As are some other recruitment agencies having read the lead

The agencies cometh...

dave

No prob...

A lot of money would be saved and potentially earned if managers got their heads out of their jacksies and documented stuff properly...

As you say it's all about these bright sparks protecting their own arses

Yes it involves graphics... they are basic screenshots though as far as I've seen... I get my induction this thurs so will find out more then.

I ended up writing a User Guide/SOP merge in HTML, 900 pages later with 3000 odd screenshots job done... Was a bind but easy to manage with updates/moves etc.

The other trick I managed was to get the users/managers to then update the HTML, leaving a up to date user guide, rather than one that's stuck under a desk propping someones feet up..

You must be well dedicated, Cata1yst! Most engineers etc that I speak to avoid documentation like the plague and refuse to do it.

I think the days of developers doing their own docs will be a thing of the past soon enough... makes senseto let engineers focus on what they're good at (and more passionate about)

Good work! Yes I'm all for making the whole deal aspainless and maintainable as poss... Makes no sense to create work for myself... Or does it?... I am a contractor as yet

Well done especially on getting user feedback... that is usually mission impossible, I hear. I reckon its possible though, and you've proved to me that it is... I hope my fresh optimism doesn't get crushed as soon as it did on my last TW job

I come from a FDA testing background originally, so I am the plague or a close second!

Developers tend to have a tendency to avoid all things written, the trick is selling it back to them that's it's their good idea.

Mind Manipulation and bribary are another skills that are needed