Technical writers are often been questioned during the interview if they have worked earlier in the same domain or not. Even I have faced the same tune during my interviews on the previous occasions but mostly by those employers who have never shown any interest in my writing ability or my understanding ability of the subjects. For a writer, is it going to make any difference? If at all, it is going to make difference, the question is how much. Is there any one to quantify it? Interviewers possibly know this question much before they come across the candidate. The kind of work they have done previously or the companies they have worked for is enough to know about the domain a candidate has worked so far. Yet, this question is eventually asked.
I have not yet understood the real purpose of this question, may be the interviewers who are very much experience in the technical writing field can throw some light on this. Whereas I understand that technical writers are meant to work in a different setup at different times and they are basically writers who are by default supposed to clear up the mess in the writing and make it simpler and understandable to the readers. What happens if they have Domain Knowledge? Will their work be faster and smoother? I agree to some extent that writers will enjoy the comfort of knowing the subject well, and it will not be demanding either to spend much time in understanding it. But even if you are in the same domain, next time the topic changes, issue changes and the requirement changes. To cope up with all these one will have to spend required amount of time. Above all, can the writer be as knowledgeable as the Subject matter experts. The straight answer can be “no”. Technical writers can learn only some basics of the domain. That can be gathered during due course of time while working on the project.
So, why is this fuss? Is this a limiting factor for any of the technical writers to land up in any technical writing job before having domain knowledge? My answer is, it should not be. If it is so, then I believe subject matter experts will have to be the technical writers. Yes, but technical writers will have to be a fast learner and should have interest in learning things to present it to the audience what they are aiming for. In this perspective, it is right to have knowledge of your domain, which can always help you in understanding. But this is not the core requirement of a technical writer. The more years of work you put in some domain, the more you learn about it. But it should not become a constraint while you make a shift from one domain to another domain.
At the end of the day it is the choice of the technical writers themselves to analyze liking for a domain and if possible stick to that because that will eventually provide them some other opportunity in terms of career growth. Say for example, I have written for Telecommunication domain, Agriculture and now writing for Life Science products. My background is in life science and it gives me upper edge in understanding the business logic of the product but the work what we perform, does not require that much of specialized knowledge. For me this domain could be a liking domain and I may prefer to be in this domain and write about it. Similarly an engineer graduate who is into technical writing might choose to write more about hard core technology, a finance graduate might think of writing in financial product and management graduate can write about ERP and other related domain. It is all about likes and dislikes, which drives you to choose the domain.
This is one of the issues going round in the industry for quite some time and there should be clarity on this. Well, the necessity will definitely bring people to understand it by themselves. I remember there was a time when only engineers were in demand to be in the technical writing. But now the clout is out, writers can be found in any individual and of any background. Therefore, now the technical writers are from different backgrounds. Similarly the dearth of good technical writers will definitely wipe away the hypocrisy of domain knowledge, which some times block your entry into many of the good corporation. Early understanding would be the welcome step towards solving this issue.
2 comments:
I Agree with rama kant . we are writers and we are supposed to turn complex jargon into simpler words. It does not matter which domain u work on.
sangeeta
I have appeared in many interviews and have always been asked this question. I believe that domain knowledge may be a positive point but having only strong domain knowledge and weak writing skills do not work.
Writing has nothing to do with domain. For sharing domain knowledge, there are SMEs. The quality needed is quick learning. Quick learning makes all domain knowledge easy.
Post a Comment