Software Architect

● Abstracts the complexity of a system into a manageable model that describes the essence of a system by exposing important details and significant constraints
● Maintains control over the architecture lifecycle parallel to the project’s software development lifecycle and proactively monitor the adherence of the implementation to the chosen architecture during all iterations.
● Stays on course in line with the long term vision of the platform. Must focus on actions that produce results early while staying on course for the long term and is able to adjust strategy given the resources available while maintaining long-term goal.
● Works closely with executives and other departments to explain the benefits and justify the investment in software architecture of a solution by participating in process re-engineering activities, by using Cost-Benefit Analysis or by measuring the level of component / architecture re-use between projects in order to deliver results that are meaningful to the projects and have an impact on the bottom line.
● Inspires, mentors, and encourages colleagues to apply intelligently customized industry’s best practices. Specifically, the stakeholders must be able to understand, evaluate, and reason about software architecture
● Fights entropy that threatens architect’s structural approach to problem solving. Convinces all relevant stakeholders that the chosen approach is sound – moreover the chosen architectural solution must be well explained and justified. The benefits of implementing a system in a particular way must be explained not only in terms of “that’s the right pattern for this problem,” but also to demonstrate the measurable benefits – such as easier integration.
● Act as an agent of change in organizations where process maturity is not sufficient for creating and maintaining architecture centric development.

19th Floor Marco Polo Ortigas Manila, Sapphire Road, Ortigas Center, Pasig City, 1600 Philippines.