Life as an analyst programmer

To be an analyst programmer, you would need a diploma or a degree in Computer Science, Computer Studies or a related discipline.

I started off as an analyst programmer. It was my first job after getting my degree. As I had no experience, I was not choosy and accepted a job on the mainframe, that paid below the market rate.

Getting instructions

As a new analyst programmer, I would received program specifications from my supervisor. Based on those specifications, I would write my program. For complex programs, the specifications might be more detailed. For simpler programs, the specifications would be sketchy. I would be expected to ask when uncertain of the details on how the program should react to situations not stated in the specifications.

As time went on, I would receive verbal summary of what is required by the user and would work from there.

In some cases, the analyst programmer would interview the users to find out their needs and then work independently from there.

Programming

This is what a programmer or Analyst programmer is paid for. You write the code in the language the system is using. Maybe COBOL, Oracle, Microsoft products, whatever. Then you test it to make sure it works. You create test scenarios. Test cases for your program to run against, then you check the results are what you expect. You need to spend time preparing the test plan. Think of all possible scenarios and what the outcome should be. Then put in test records that fulfill those scenarios and see if you get the correct results.

Once that is OK, your program is tested with all the related programs in the system. If it works fine, then it can go into production.

Maintainance

Not all your time would be spent writing new applications. Most of my time as an analyst programmer was spent maintaining other people's programs. These existing programs need to be modified now and then as circumstances change. The business may change, an existing bug uncovered, whatever.

Also you'll probably have to deal a lot with user enquiries. Why the computer gives this message for this record. Why the system doesn't work? Why there are discrepancies? How to use this system and so on.

Administrative tasks

Most of the time may be spent filling in forms. Forms to move to testing environment, forms for production, forms to indicate how much time was spent on each activity for each day, forms for user enquiries, forms for the changes made. The list goes on.

What next

From and Analyst Programmer, the next level would be either a senior analyst programmer, then systems analyst then senior systems analyst. From there, it would be in supervisory roles or as a consultant.