Job Title: Sr. Information Engineer - System Analyst
Type of Company: I work for a health insurance company.
Education: BA, Marketing & Management Information Systems, Boston University MS, Management Information Systems, Boston University
Previous Experience: I started as an entry-level programmer for the same company I work for today.
Job Tasks: I work with a team of people who are responsible for the systems that handle the installation of new cases, the maintenance of eligibility and the renewal of existing cases.
My job responsibilities include deciding how changes should be made to the computer system, estimating the cost of those changes, and tracking their status. I have a weekly meeting with our business partners who requested the change, for them to give us the information to estimate the change. They provide some high level requirements and we take a guess at the changes required. This estimate goes back to the business and then they decide whether they want to go forward with the change. If they decide to go forward with the change we meet with the business to define the detailed requirements. After the requirements are defined, a conceptual design is created which is a high level picture of all the changes. Then a work plan is created so that the changes can be split among the members of the team. Once the system requirements are complete they can be turned over to the engineer. The SA team still stays involved by providing support to answer questions and develop solutions when problems occur.
Best and Worst Parts of the Job: The best part of the job is the satisfaction I get from knowing I've done my job well, but hearing how excited our customers are with the product we've designed is pretty gratifying too.
The worst part of the job is the constant focus on cost and time. When changes occur they increase our costs and delivery time, but since we've committed to a cost and a delivery date there's not much usually we can do about it.
Job Tips: Communication is critical to the success of the team. Everyone needs to know who's doing what so that work isn't duplicated and all the work gets completed. We have a lot of meetings just to make sure everyone is on the same page. Forget about the problem, or don't dwell on it anyhow. Always focus instead on finding a solution. It's easy to say this is wrong, or that's wrong, but it's much more productive to say we can prevent this by doing a, b or c.
Additional Thoughts: I like games and solving puzzles, which is why I like this job. A problem is just a puzzle that I need to solve. There is real satisfaction when the puzzle is completed.
The inside stories from people actually working in the field.
Click a story title to show the story, and click the title again to hide it.
Career Stories are concise, real-world career overviews written by people relating their personal career experiences and wisdom. They provide invaluable insights and mentoring advice to students and career changers.
Most stories include:
Please also see our detailed information about Computer Systems Analysts, including: