Philips Principal Architect in Bangalore, India


 Monitor the Software Development Process to ensure quality of project/program deliverables in the sector

 Participate in start up activities of new programs or BU’s from technical perspective

 Identify current and future competency needs of the sector and participate in establishing competency development plans

 Designs and describes the software architecture (world class level) of specific products

 Provides leadership to the architecture directions and monitor architectures and recommend ways and means of achieving synergy across BU in the sector

 Scouts the environment to identify best practices, industry and technology trends and roadmaps of competition

 Is responsible for key technical decisions in the product program

 Represents the BU/ organization in PH wide bodies (eg:ATT) and can be the external interface in industry collaboration ( Eg: Microsoft, Intel)

 Is responsible for technology planning and forecasts.


 Input to formulation of the budget plans of the sector.

Customer management

 Contributes to the business development activity of the sector

 Ensures escalation in technical areas are handled effectively


 Recommends staffing needs of BU’s/ sector

 Contributes towards the performance appraisal of the senior technical staff in the sector

 Acts as a role model for other technical members in the group

 Plan for competency development in the sector to match current and future needs of the group


 Is a member of sector management team

 Plays an advisory role to the senior management of the Sector/BU on technical and organizational matters

 Ensures that there is good co-operation with other Sector's/BU’s

 Influence all technology policies of the Sector

 Supports product programs in their road mapping process

Accountability and Authorities


 Responsible for the architecture/design of world class product program

 Makes all key technical decisions

 Accountable for specific deliverables


 Approving architecture and top level design documents

 Stopping release if it does not conform to minimum standards

 Resolves differences in architectural choices with products/ programs

2.6 Decision Making

 Defines/Approves any architectural changes in the product program

 Technical changes in the product program