Thursday, July 23, 2009
What’s it like to be a…..Systems Architect/Sr Consulting Engineer?
My company job title is: Systems Architect/Sr Consulting Engineer
Current project or contract role: Lead Systems Engineer (architect & design), Information Assurance (security) Engineer, Control Account Manager (cost and schedule)
What does a normal day look like?
My current contract means that the majority of my work is paid for through a Government or Commercial contract for services or for development of a system. System development goes through software development lifecycle phases. So I play different roles depending what phase the system is currently in. For example, the requirements definition phase requires that I work on system requirements, performance requirements, security requirements, etc. In the design phase, I have to establish design goals, evaluate development methods and procedures, create architecture diagrams, define software packages, etc. In the build phase, I review development components and update architectural views. During integration and testing, I review documentation products for technical content, update systems documents, evaluate test results.
Is it consistent throughout the year?
There are variations which include management work to review technical personnel for promotions and salary raises. I sometimes have to work on new proposals to acquire additional system development contracts or evaluate the proposals that other organizations have prepared. We often meet with our customers to go over the planning for new tasks within existing contracts or to review problems and technical solutions.