From: Me
Sent: Wednesday, June 14, 2017 4:07 PM
Subject: RE: Documentation meeting tomorrow afternoon
My status:
- I classify the documentation from [Team Lead 1] as “operational” – the main procedure they would follow has links to sub-documents with more details.
- I am going to continue to focus on the files from [Team Lead 2] and incorporating.
- I met with [Team Lead 3] this AM and it was a very good meeting. We created folders under the S:\Disaster Recovery Planning folder for his team to put documents in. He said he can begin putting some general documents in the folder structure and then, after he meets with his team next week, more documents will be added. He was in agreement about the idea of putting the documentation that his team would need in a disaster situation into that folder structure. I walked out of the meeting excited about the ideas we discussed.
I feel really good about where I am at work - the disaster recovery documentation is progressing nicely!
And, oh yes, as for the question I began this post with, here it is:
What is the difference between Can-Am Consultants, Inc. - Remote & Can-Am Consultants, Inc. - Parma, OH?
I ask because of what was in my Indeed.com job email this AM:
Is it for full-time or part-time? I have no clue. Thus, I'm not going to give Can-Am Consultants, whether they are in Parma, OH, or "remote" (wherever that is) my information. Plus, what is the difference between "Mandatory" requirements and "Required experience" is unclear to me. Good luck to Can-Am Consultants - may their quest to find the right candidate be short. Just for the record, here's the full job description:
Technical Writer (Software)-W2 Contract
Can-Am Consultants, Inc. - Remote
ContractMajor banking institution seeking a contract remote Technical Writer
We are looking for a senior Technical Writer to produce high-quality documentation and help capture requirements that contribute to the overall success of our products. We have a large project that will impact several areas. You will work collaboratively with various members to document and explain information in a clear and concise manner. You will be participating in, and potentially facilitating, meetings to help capture notes/requirements and document current processes/procedures. Previous experience in banking and/or the PCI area is a plus. Also, Business Analyst experience is a plus.
- Work with internal teams to obtain an in-depth understanding of the changes needed and document the requirements
- Attend meetings a capture notes to then organize in a readable and understandable manner
- Produce high-quality documentation that meets applicable standards and is appropriate for its intended audience
- Analyze existing and potential content, focusing on reuse and single-sourcing opportunities
- Create and maintain the information architecture
- Analyze documents to maintain continuity of style of content
- Manage updates and revisions to technical documentation
Mandatory:
- Proven working experience in technical writing of software documentation
- Ability to deliver high quality documentation paying attention to detail
- Ability to quickly grasp complex technical concepts and make them easily understandable in text and pictures
- Skilled at prioritization and multi-tasking
- Excellent written and verbal skills
- Ability to write in explanatory and procedural styles for multiple audiences
- Strong working knowledge of Microsoft Office
- Basic familiarity with the SDLC and software development
Job Type: Contract
Required education: Bachelor's
Required experience:
- Technical Writing: 1 year
- Software Documentation: 1 year
- Payment Card Industry (PCI): 1 year
Editor's Note: Without being cocky, job descriptions like the above are nothing more than a reminder that the job search of 2016 is over.
No comments:
Post a Comment