Best Programmers

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 30 July 2004

Wanted: Sr Technical Writer for Informatica Corporation

Posted on 03:04 by Unknown
Location: Bangalore


Corporate Headquarters: Redwood City, CA


Contact: Thao Diep, tdiep@informatica.com





Job Description



Responsible for writing documentation to support our PowerAnalyzer and PowerCenter Connect product lines. PowerAnalyzer is a business intelligence tool that helps decision makers access, analyze, and share enterprise data. PowerCenter Connect products enable integration to ERP systems such as SAP and PeopleSoft, CRM systems such as Siebel, and messaging systems such as IBM MQSeries. As a Senior Technical Writer at Informatica, you will be required to write new manuals and update existing ones. You will be responsible for delivering high-quality printed manuals, online help, release notes, and webzine articles on time.






Responsibilities


Plan, develop, and write highly technical information (concept, task, and reference) that describes the functionality of our PowerAnalyzer and PowerCenter Connect products.

Maintain schedules for specific products and communicate documentation status to documentation manager.

Edit documentation for completeness, style, and accuracy to ensure it reflects Informatica's commitment to quality.

Mentor new writers.





Qualifications


  • 3+ years technical writing experience (software).
  • BA/BS (English, Journalism, Linguistics, History, Computer Science).
  • Experience writing about a BI tool (Microstrategy, Business Objects, Cognos).
  • Working knowledge of business analytics (BS in Business or similar work experience).
  • Working knowledge of data warehousing, dimensional modeling and star schemas, web portals, web servers, application servers, and wireless protocols.
  • Familiarity with databases, Java, SQL, ERP software, CRM software, and XML.
  • Experience with FrameMaker, Web Works Publisher, DreamWeaver, or HTML.
  • Excellent analytical and written communication skills.
  • Excellent leadership and project management skills.
  • Ability to quickly learn technical information.
  • Ability to meet deadlines and help others meet them.
  • Ability to multitask, prioritize, and develop schedules.


Write to me: Suman[at]techwritersindia[dot]com
Email ThisBlogThis!Share to XShare to Facebook
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Finding the voice
    Excerpt from LOUIS MENAND's review of Eats, Shoots & Leaves: The Zero Tolerance Approach to Punctuation” (Gotham; $17.50), by Lynne ...
  • Context Sensitive 'Sticky Notes': Stick a Sticky Note to your Blog!
    Conceptworld's Quick Notes Plus might appear like any other Sticky Notes Plus (QNP) program, but its context-sensitive notes feature is...
  • Use it before you write it.
    From the Nikkor ED 80-400mm f/4.5-5.6D VR Review (emphasis is mine): [quote] Here's the warning in the manual : "When the camera is...
  • Style guides: Sacrosanct?
    How many times have you paused and reflected, ‘man, I know I am right, but the style guide does not agree…’? For example, some style guides ...
  • (no title)
    Next STC Chennai Meeting On March 7 : This will be the second knowledge sharing session. The first meeting was a wonderful success and we h...
  • Wanted: Sr Technical Writer for Informatica Corporation
    Location : Bangalore Corporate Headquarters : Redwood City, CA Contact : Thao Diep, tdiep@informatica.com Job Description Responsibl...
  • The Personable Manual
    Why do product manuals sound formal and stiff-upper-lipped? Why don’t users read manuals? These questions have haunted the hallowed precinct...
  • Comments System: Anyone Can Post Comments Now!
    Folks, I know some of you were irritated by the fact that you had to login (if you're a Blogger user) or post as Anonymous while posting...
  • A brand name gone wrong
    "Did you know that Heroin was originally a brand name for cough syrup? In 1874, German scientists developed a formula for a painkiller ...
  • Promoting Document Usage: Taking a leaf out of Business Directories
    You can argue all day that you know a customer that reads your manuals but my point is that most don't. It is a blessing in disguise fo...

Categories

  • conferences
  • contigency design
  • culture
  • design
  • error messages
  • google
  • hall of shame
  • ideas
  • management
  • manual
  • standards
  • stc
  • strategy
  • tools
  • usability
  • writing

Blog Archive

  • ►  2009 (1)
    • ►  February (1)
  • ►  2008 (5)
    • ►  November (1)
    • ►  September (1)
    • ►  May (2)
    • ►  April (1)
  • ►  2007 (7)
    • ►  October (1)
    • ►  August (2)
    • ►  June (1)
    • ►  March (1)
    • ►  January (2)
  • ►  2006 (10)
    • ►  November (2)
    • ►  October (3)
    • ►  September (1)
    • ►  August (3)
    • ►  June (1)
  • ►  2005 (17)
    • ►  December (2)
    • ►  November (1)
    • ►  October (3)
    • ►  September (2)
    • ►  August (3)
    • ►  June (2)
    • ►  May (1)
    • ►  April (2)
    • ►  February (1)
  • ▼  2004 (32)
    • ►  December (4)
    • ►  November (1)
    • ►  October (3)
    • ►  September (3)
    • ►  August (2)
    • ▼  July (5)
      • Wanted: Sr Technical Writer for Informatica Corpor...
      • Style guides: Sacrosanct?
      • Wanted: Technical Writers for Wipro Technologies, ...
      • Job openings for young under-grads and graduates i...
      • Installing a gas stove: Why I think technical writ...
    • ►  June (3)
    • ►  May (1)
    • ►  April (5)
    • ►  March (2)
    • ►  February (1)
    • ►  January (2)
  • ►  2003 (42)
    • ►  December (2)
    • ►  November (3)
    • ►  October (1)
    • ►  September (3)
    • ►  August (7)
    • ►  July (2)
    • ►  June (1)
    • ►  April (4)
    • ►  February (4)
    • ►  January (15)
Powered by Blogger.

About Me

Unknown
View my complete profile