Technical Writer Interview

260 views
Skip to first unread message

John

unread,
Feb 15, 2012, 3:54:39 PM2/15/12
to Technical Writing Mentors
Hello,

I am a Writing and Rhetoric student at Oakland University, MI. One of
my assignments this semester is to find a person that is working in
the field of technical writing and conduct a short interview. Would
anyone here be interested, or can you refer me to an interviewee? The
questions are as follows:

1. What is it about this occupation that drew you to it in the first
place?
2. Please describe what an average day of work is like.
3. What type of education did you need to complete in order to obtain
this position?
4. Are there any particular skills that are most useful?
5. Are there any writing skills you found were not useful?
6. What challenges do you face when working on an assignment?
7. Who is the audience for your writing?
8. How much time, on average, do you spend writing each day?
9. What is the work environment like? How does your job fit into the
overall picture?
10. Is there any advice you would like to give to an aspiring
professional writer?

I greatly appreciate any assistance. If you would like to be the
interviewee, please give me your first name and occupation. You can
respond to me in email if you like.

Sincerely,
John

Bill

unread,
Feb 16, 2012, 2:08:17 PM2/16/12
to Technical Writing Mentors
Hi John,

I'll reply publicly, hoping that others will do the same so you and
others with similar questions see what similarities and differences
exist in the field.

> 1.      What is it about this occupation that drew you to it in the first
> place?

It was a natural fit for me. I was interested in technology, and
writing came easily.

> 2.      Please describe what an average day of work is like.

I don't think I've ever had a truly average day of work. Over the
years I've worked for many different clients and companies and in
nearly as many techcomm-related roles. For technical writing, I was
primarily documenting software. An average day in that regard involved
a mix of using the product, researching features in technical specs
from the development team, talking to developers, testers, support
techs, marketing and sales, and writing.

> 3.      What type of education did you need to complete in order to obtain
> this position?

I received a BS in Communication from an Engineering school, but
you'll find that answers to this question will vary quite a bit.

> 4.      Are there any particular skills that are most useful?

Quite a few, though ability and willingness to learn, ability to
interact with others, dig for information, and take a formulaic
approach to writing helped me most.

> 5.      Are there any writing skills you found were not useful?

Not particularly.

> 6.      What challenges do you face when working on an assignment?

Conflicting personalities will always top the charts, in my opinion.
One of the most important thing you can do is build rapport in your
workplace. that will ensure you get the cooperation you need to get
the job done.

> 7.      Who is the audience for your writing?

It varied greatly, from the most technically inclined to the most
technically deficient. I've written for the general home computer
user, I've written for experienced programmers and software
architects, and for quite a few ranks in between.

> 8.      How much time, on average, do you spend writing each day?

This varied greatly from day to day, but I'd say maybe 10-20% of total
project time was spent writing, depending on the project.

> 9.      What is the work environment like?  How does your job fit into the
> overall picture?

This varied as well. I was part of a team producing a product, I was
the guy leading a project or implementation, I was the troll in the
corner who was avoided at all costs...

> 10.     Is there any advice you would like to give to an aspiring
> professional writer?

Don't stop learning. Figure out what you enjoy doing most and align
with it, but not to the detriment of other needed activities. Build a
solid rapport with your team. Keep your eyes open for new or missed
opportunities to improve your customers' experiences. Don't be afraid
to ask questions. Look for ways to improve how you perform your job.
and if you find yourself in a situation where you aren't working, find
a way to keep your techcomm skills sharp and account for it on your
resume.

I'm happy to answer any follow-ups as well.

Bill

John

unread,
Feb 18, 2012, 12:27:42 PM2/18/12
to Technical Writing Mentors
Bill,

Thanks a lot for all of the info!

-John

Tom Johnson

unread,
Feb 21, 2012, 12:25:34 AM2/21/12
to John, Technical Writing Mentors
Bill, thanks for responding to John's questions. Because this is a Google Group, your answers will be archived in the forums.

Tom
---------------------
blog: idratherbewriting.com
twitter: tomjohnson



--
You received this message because you are subscribed to the Google Groups "Technical Writing Mentors" group.
To post to this group, send email to technical-wr...@googlegroups.com.
To unsubscribe from this group, send email to technical-writing-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/technical-writing-mentors?hl=en.


Reply all
Reply to author
Forward
0 new messages