Pros: freedom. lunches could be taken anytime, time off granted with ease, etc.
Cons: culture where, of all the team members involved in a build, it was the analyst who took the brunt of the blame if something went wrong.
Worked extensively with data analysis, designing news subject matter from raw data to publishable online data. This was done by writing conversion instructions for programmers to code the raw data and write a customized conversion to get the data in proper format for online publication. There were many more tasks, including troubleshooting data problems – more... and helping customers with issues. A typical day involved a lot of desk work, using many analysis tools...and a lot of interaction with peers and programmers.
We were given a great deal of latitude as long as we accomplished our daily responsibilities. We were encouraged to work as a team, in a fun, casual environment. This freedom was perhaps the most enjoyable; no micro-managing and great co-workers. No threatening corporate culture.
The most difficult part of the job was being held accountable for every possible problem with an online publication, even years down the line. The fact is, the years after a publication release, many hands were in the pot, making changes, often resulting in customer complaints. However, it was the original Analyst held accountable; it was frustrating and also a waste of productivity trying to determine the origins of the problem, and often being forced to defend our actions from years prior. – less