A career in Westfield's Information Technology (IT) department offers many exciting opportunities that require creativity, innovation, and technical expertise to deliver solutions that align with our corporate goals and business strategies. IT and our business clients partner together contributing to the company's success in an intensely competitive market. As a member of the IT team, responsibilities will enable you to define, design, implement, and maintain technology solutions that will continue to contribute to Westfield's long history of success.

A career in IT Involves:

Architecture and Emerging Technologies
Program and Project Management
IT Financial Reporting
Application Development
Testing Services
IT Risk, Security, and Compliance
Systems Development and Support
Service Desk - Help Desk and Desktop Services
Infrastructure Services
Data Center
Data Analysis
IT Service Management

After completing the GDP, you will be placed in one of these positions, based on the best fit for you:

Application Developer
Systems Analyst


	Bill Neff Application Developer talks about his job

Day in the Life of an Application Developer

8:00 A.M.

Check e-mail and listen to voice messages, and respond.

8:30 A.M.

Meeting with solution architects to discuss changes to our SOAP messaging standards and give us an update on IAA services. Ask questions based on background research I've done. The second part of this meeting will be to review the governance of reusable assets.

10:30 A.M.

Continue work on developing a new portlet to be deployed on our Application Development portal page. I need to add some content from our Enterprise Content Management.

1:00 P.M.

After lunch, check e-mail and listen to voice messages, and respond.

1:30 P.M.

Project status meeting to ensure we are on schedule. Review my work on the supplementary specifications for the new policy processing project with the solution architect and designer. We'll make sure all the pieces fit together, compare them with the business requirements, and add traceability.

3:30 P.M.

Conference call to review technical issues with our vendor and consulting company.

4:00 P.M.

Do some research on the wiki to see what updates have been done in regards to a service that our project is going to implement. I'll be working with the designer and development team to answer any questions before coding begins.

This brief overview is provided to help give some context to this role.
It is not comprehensive, nor is it a job description.

A Day in the Life of a Systems Analyst

8:30 A.M.

Send an e-mail with an agenda for meeting with Personal Auto business team later today. (This is a follow-up to an e-mail I sent last week setting expectations for what we had to accomplish in the meeting.) There are several key decisions needed from business subject matter experts about the new procedures, coverages, and rating rules for our auto insurance products.

9:00 A.M.

Prepare for the Personal Auto systems development team meeting: There are new areas of functionality that business partners are requesting for integration with our existing systems. I need to bring these to the attention of the Application Developers, Data Analysts, Solutions Architects, and Testers during our requirements review so we can identify the key areas of risk for the project.

10:00 A.M.

Personal Auto systems team meeting: Review system requirements with the systems development team and facilitate questions and discussion. Take notes, capture action items, and keep the group on task. There were several requirements clarifications brought out during the discussion that will need to be included in the system requirements documentation after validation with our business clients. We also discovered that our project may have integration points with the Agency Automation projects.

11:30 A.M.

Lunch with another Systems Analyst I am mentoring. Discussed ways I can assist with some on-the-job training using our requirements management tools. This helps us both out. She will be able to increase her technical skills and I will be able to apply what we have discussed on my project.

1:00 P.M.

Requirements Management: I set aside time this afternoon to analyze the requirements changes that surfaced during meetings I had earlier in the day. I updated the Personal Auto project in our requirements management tool with the necessary updated. I need to ensure I understand the impact these updates have on other requirements and the existing test cases. This requires a synchronization to be performed between our requirements management tool and test case/defect tracking tool. I follow the procedures in my requirements management plan and notify the systems development team of the changes.

4:00 P.M.

Meeting with Agency Automation Project Manager: Discuss areas where our projects require changes to similar systems. Make sure we understand the scope and timeline of each other's projects because we may need to implement some of their requirements as part of our project.

4:30 P.M.

Prepare notes and send a follow-up e-mail to SMEs and Agency Automation project team after both meetings. Call the Systems Analyst I am mentoring to ask for her help on the Agency Automation project.

This brief overview is provided to help give some context to this role.
It is not comprehensive, nor is it a job description.