Tim Flaherty

FAQ About Tim Flaherty

• What is Tim Flaherty's address?

  Tim Flaherty is located at
  New York City Metropolitan Area, New York City Metropolitan Area, United States

• What is Tim Flaherty's job title?

  Tim Flaherty is a
  I work as a technical writer because I love the work. Technical writing is rewarding because it offers a unique challenge. You start off as one of the least knowledgable people in the room, and have to quickly become one of the most informed. I've done this over and over and the process is exhilarating. I enjoy gathering raw information from whatever sources are available and refining that rough material into precise and straightforward documentation. I'll learn from whatever sources are available. Formal requirement specifications and design documents are ideal, as are interviews with subject matter experts. But I can also glean information from email threads, conversions in messaging tools like Slack, or story and task descriptions in scrum-tracking systems. Or let me loose on product prototypes. Let me play with the GUI or API, and I'll also help by suggesting possible design improvements. Or I might find some bugs in the product while I'm searching for the information I need. I've now accumulated over 20 years or varied experiences in the industry. I've created documentation primarily for system administrators and application programmers, and also for less-technical end users. I've documented parallel programming environments, programming tools, administration tools for high-performance clusters, a geographic information system, factory automation tools, a statistical process control API, an API for instrumenting application programs, mainframe security and cryptography facilities, and a centralized data-protection platform. I've led teams of technical writers. I've planned technical writing projects. I've coordinated nightly automated builds of DITA source files into PDF and HTML output, troubleshooting problems as needed. I've guided larger teams through tough transitions to new tools and organizational styles. I've served as an accessibility focal point for documentation teams, ensuring that documentation is useful to users with physical or situational impairments. So I can do a lot more than just the writing. But primarily I'm a technical writer, and all my other capabilities stem from that. Palo Alto Networks

• What industry does Tim Flaherty currently work in?

  Tim Flaherty currently works in the
  Palo Alto Networks

• What is Tim Flaherty's area of expertise?

  Tim Flaherty specializes in
  I work as a technical writer because I love the work. Technical writing is rewarding because it offers a unique challenge. You start off as one of the least knowledgable people in the room, and have to quickly become one of the most informed. I've done this over and over and the process is exhilarating. I enjoy gathering raw information from whatever sources are available and refining that rough material into precise and straightforward documentation. I'll learn from whatever sources are available. Formal requirement specifications and design documents are ideal, as are interviews with subject matter experts. But I can also glean information from email threads, conversions in messaging tools like Slack, or story and task descriptions in scrum-tracking systems. Or let me loose on product prototypes. Let me play with the GUI or API, and I'll also help by suggesting possible design improvements. Or I might find some bugs in the product while I'm searching for the information I need. I've now accumulated over 20 years or varied experiences in the industry. I've created documentation primarily for system administrators and application programmers, and also for less-technical end users. I've documented parallel programming environments, programming tools, administration tools for high-performance clusters, a geographic information system, factory automation tools, a statistical process control API, an API for instrumenting application programs, mainframe security and cryptography facilities, and a centralized data-protection platform. I've led teams of technical writers. I've planned technical writing projects. I've coordinated nightly automated builds of DITA source files into PDF and HTML output, troubleshooting problems as needed. I've guided larger teams through tough transitions to new tools and organizational styles. I've served as an accessibility focal point for documentation teams, ensuring that documentation is useful to users with physical or situational impairments. So I can do a lot more than just the writing. But primarily I'm a technical writer, and all my other capabilities stem from that.

• Which languages does Tim Flaherty speak? 

  Tim Flaherty speaks the following languages:
  No languages available.

• Which industries has Tim Flaherty previously worked in?   

  Tim Flaherty has prior experience in the following industries:
  Capgemini Engineering , Ibm , Fastech Integration , Centerline Software , Sykes

• What is Tim Flaherty’s work experience?  

  Tim Flaherty has the following professional experience:
  Palo Alto Networks , Capgemini Engineering , Ibm , Fastech Integration , Centerline Software , Sykes .

• How can I find Tim Flaherty on LinkedIn?  

  You can view Tim Flaherty’s
  LinkedIn profile at LinkedIn URL.

• What are Tim Flaherty’s work email addresses?  

  Tim Flaherty’s work email addresses are
  [email protected] .

• What company does Tim Flaherty work for?  

  Tim Flaherty works at
  Palo Alto Networks