SUMMARY

• I am a Senior Technical Writer based in the Richmond, VA area with some 20 years of experience developing technical documentation in a myriad of diverse environments.
• Exceptional writing capabilities coupled with rhetorical analysis, document planning, substantive editing, strong organizational, time management, and interpersonal skills.
• Demonstrated ability to handle multiple tasks, respond to shifting priorities, meet deadlines, and pay attention to details.
• Top quality, timely technical writing skills coupled with crystal clear communication in print and electronic form that allows me to bridge people and technology to assist with the business.
• Technical writing and editing
• Documentation project management
• Online documentation and help systems
• Analysis (and troubleshooting) of functional processes and tools
• Outstanding organizational, leadership, and analytical problem - solving skills
• Ability to communicate technical information in a clear and concise manner to any audience
• Diverse skills in technical communication, engineering, and IT
• Superior written and verbal skills
• Problem solving and analytical skills
• Creating and implementing effective documentation plans
• Wide range of subject matter experience
• Information architecture
• Suite of documentation tools: Word, Visio, Snag-it

PROFESSIONAL EXPERIENCE

Sr. Technical Writer / BA contractor onsite

Confidential

Responsibilities:

• Confidential is responsible for issuing individual and general permits that control stormwater discharges from municipal separate storm sewer systems (MS4s) and construction activities. Confidential administers these programs through the Virginia Stormwater Management Program (VSMP) Regulations, which are authorized by the Virginia Stormwater Management Act.
• Tasked with the clean sheet development of the Confidential Stormwater Construction General Permit System User Guide.
• Assisted with the development of the UAT test planning. I also captured and edited the test results for Executive Management assessment.
• Gathered information needed to develop additional ad hoc Agency documentation including proactively participating in cross-functional meetings, interviewing SME and Analysts.
• Determined documentation resource needs. Coordinated documentation development across Engineering and Business boundaries. Developed standards and instigated process improvements.
• Elicited and gleaned information to revise technical requirements based on user input and SME interviews.
• Performed reviews on internal Agency documents including downgrading, safeguarding, access, disposition, reproduction, accountability, dissemination. Reviewed documents for proper classification by working with subject matter experts within the agency. Ensured that the content is conformant with guidelines, and performed regular and reoccurring reviews of content based upon current technical and functional requirements.
• Applied experience with technical editing, formatting, and quality assurance output to ensure that the content is communicated clearly, concisely, and effectively, this is done to ensure all of the documentation deliverables meet quality, relevancy, congruency, and consistency with the Agency standards.
• Triaged content from multiple sources, and identified topics and the appropriate subject-matter experts to respond to requests. Also, maintained inquiries and responses, and acted as a team lead developing and refining documentation procedures.
• Provided recommendations for continuous process improvement in the QA / technical editing functions and advised Developers in matters of style, syntax, mechanics, and usage to improve the general quality and effectiveness of the content being developed.

Sr. Technical Writer / BA contractor onsite

Confidential

Responsibilities:

• Information Management Systems (IMS) Application Development Group documentation tasks included developers’ handbook, software operation manuals, install / config / troubleshooting procedures, and managing requirements throughout the SDLC lifecycle, also determined the appropriate basis standards for the all of the group documentation. Gathered information needed to develop the documentation including proactively participating in cross-functional meetings, interviewing Managers and Personnel.
• Determined, analyzed and performed a documentation gap analysis coupled with a single point of failure for Management review.
• Developed and implemented the program level document development plan. Also, tasked to document the existing IT development lifecycle, update or develop clean sheet procedures as needed for each section of the group.
• Documented application processes, requirements and specifications for an updated software development lifecycle
• Established documentation template and styles for internal use
• Assisted Management, Developers, Web Services, Law, Testing and Ops Support and InfoSec with questions about their documentation needs and downstream suggestions.

Confidential, Glen Allen, VA

Sr. Technical Writer / BA contractor onsite

Responsibilities:

• Accountable for the development, writing, editing, and managing of all technical requirements, process and procedures docs and all internal core documentation for the AGILE Program Shield driven by Information Security and Risk Management group (ISRM) to bring Capital One in compliance with PCI DSS. Note that PCI DSS is a set of requirements mandated by the Payment Card Brands like Visa and MasterCard to protect cardholder data and prevent fraud by reducing risk of stolen credit and debit card information.
• Responsible for the development, writing, editing, managing, and delivery of highly proprietary use cases, technical requirements, and procedures for the Technical Information Security Operations Group at Capital One.
• Worked directly with InfoSec Directors and Senior Management, Network Engineering, CIRT, Infrastructure Development, Requirements SME, the Systems Analysts, and the Process Owners and Network Security Engineers to develop, write and edit program and system documentation, procedures, technical security standards and Information Security Controls. Developed, documented, and edited pre-existing, legacy examples of Information Security Programs and processes to be documented include Intrusion Monitoring, Intrusion Detection, Security Event Management, Computer Incident Response, Data Leakage Prevention, Information Security Controls, Anti-Malware.

Confidential, Glen Allen, VA

Sr. Technical Writer contracted

Responsibilities:

• Performed clean sheet development of a proprietary Systems Requirements Specification document for the U.S. Confidential (“In-Processing” for new naval recruits).Worked with the SME to define the technical and functional requirements for this document.
• Performed a series of substantive edits on eight (8) proprietary documents for the U.S. Confidential . Also, co-authored templates to meet a variety of technical documentation needs. Developed detailed, highly technical documentation, including system administrator guides, end-user guides, and step procedure guides.
• Developed four (4) highly proprietary documents for the U.S. Confidential: End User Guide for the Naval Examination Development System (EDS). A Systems Requirements Guide for the Officer Programs Management Information System (OPMIS), and EDS System Administrators Guide.
• NOTE: From Spring 2009 to Fall 2010, I was unemployed

Confidential

Analyst

Responsibilities:

• Processed standards from identified status to final approval; analyzed the standards to identify and raise awareness within affected business areas, and also to analyze standards discussions and prepare summary statements for Chief Technology Officer and Director of FRIT (Federal Reserve Information Technology) approvals.
• Also took and posted Standards Pipeline meeting minutes and agendas on the Standards Quickplace (IBM product) intranet site, managed the site, tracked and administered pipeline reports, and worked closely with Standard Authors and Advocates to facilitate the timeliness of getting their standards through the approval process.

Confidential, Richmond, VA

Sr. Documentation Analyst

Responsibilities:

• Worked with Federal Reserve Information Technology (DSE) Design Systems Engineers to research, develop and understand functional and technical requirements. Created technical documentation artifacts, developed detailed pattern documentation, and assisted DSEs in creating narratives for their detailed design documentation. Edited input from multiple authors into a guide with a single voice.
• Lead Documentation Analyst for FRIT Network Systems and Design Network group working on the Treasury Automated Auction Processing System (nTAAPS) project (managed by Federal Reserve Bank of New York on behalf of the US Treasury). Developed proprietary, highly technical network design and architecture documentation with narrative.
• Successfully lead initiatives to develop documentation frameworks/templates and standardizations in tandem with the InfoSec Group obtaining ISO 9000 and 27001 certification. Edited and reviewed 400 + COSO (The Committee of Sponsoring Organizations of the Treadway Commission (COSO) defines risk as “the possibility that an event will occur and adversely affect the achievement of objectives”) proprietary documents for this group for certification.
• Lead documentation/editorial focal point for all FRIT InfoSec documentation. Developed FRIT template for the ISO requirement of a global look and feel. Established an updated documentation structure based on a hierarchy of Requirements>Standards>Procedures for all FRIT InfoSec team members. Incorporated internal customer and stakeholder feedback into standard documentation.
• Identified gaps in processes for documentation/following up with teams to suggest risk assessment when raising gaps to management in a timely manner.
• Assisted co-workers with writing projects and taught “how to “writing and editing lessons to DSE staff.
• Edited all DSE documentation for correct style, grammar, and organization of technical material in legacy manuals. Assisted design engineers in updating engineering specs.
• Developed an interdepartmental writer's guide for the group. Helped organize manuals archiving system to accommodate new design docs and extensive peripheral documentation.