![]() ![]() Any cloud (public/hybrid) experience a distinct advantage.Demonstrable management and leadership experience, including prior experience ofīuilding and developing a successful technical team/s.Enterprise Architecture experience, utilising TOGAF or equivalent methodology.Confident, approachable, Self-driven, Result oriented and professional manner.Proven excellent consultative, facilitation and customer relationship skills.Excellent written and verbal communication skills in English.Ability to present to all levels from C-level to technical staff.Understanding of business processes and transformation aspects. ![]() Resilience and drive to deliver results.Knowledge of industry trends, vendors and partners and passion for technology.Extensive knowledge in Software DevOps practice (Desktop, Web, Cloud, Mobile Technology).Net, Java, Python) as well as other Open-source technology. Good understanding and hand on experience in Cloud Technology (AWS, Azure), Mobile Technology (IOS, Android and React Native/Flutter), Software Technology (Microsoft.Demonstrable relevant experience in defining reference architecture, technical standard works, governance standard works to a very high standard.Proven track record in managing software platform development, including requirement scoping, estimation, conducting demonstrations and proof of concepts.Proven ability to lead, manage and drive high performance across technical and project teams.Deep knowledge and experience in the area of enterprise application development, enterprise integration, enterprise mobile application development and cloud native development and cloud migration.Ability to assess, architect, design, and manage the implementation of large software solutions.Experience in defining and driving Technology Strategy, Roadmap & Technology consulting.At the functional level, for example, IT services can be categorized as interaction service, application logic service, data service and technical service.Īgile ESA helps clarify enterprise-level issues and key stakeholders’ major concerns (or the architecturally significant concerns) by forming critical architectural thinking blocks, especially those in between enterprise strategies and capabilities, business domains and applications, and applications and technologies.Location: Building No 12D, Floor 5, Raheja Mindspace, Cyberabad, Madhapur, Hyderabad - 500081, Telangana, India Job Role Enterprise Solution Architect Job Descriptionįocuses on establishing engineering practices, providing technology leadership across BU accounts and operational direction to Solutions Architects. Its focus is on different levels of service interaction, service offer, and service system. Importantly, the IT service serves as a liaison between the enterprise blueprint and solution architecture. Within this architecture, all high-level statements (business initiative, process, and the like) need to be clearly mapped into ESA elements before they can become part of the architecture. Therefore, what really matters in the IT world is an Enterprise Solution Architecture (ESA) that inter-mingles EA with Solution Architecture (SA) and provides holistic yet pragmatic modeling to enterprise information systems, along with an incremental and iterative approach for agility.Īgile Enterprise Solution Architecture mainly covers five areas: 1) enterprise capability (enterprise-wide organizational considerations of strategic planning, business context, and relevancy), 2) requirement/case scenario (business process and functionality required for enterprise IT systems), 3) architecture overview (including traceable business measurements, architecture patterns, and architectural metrics such as principle, risk, architecture decision, etc.), 4) IT functional service (relationship/interaction, granularity, etc.), and 5) IT infrastructure (operational aspect). Most of the routine work of enterprise architects, in fact, involves crafting application or technical architecture. In practice, an enterprise architect is either engaged in strategic planning (including business modeling) or solution-oriented architecture. Such improvements are constantly needed as complex systems EA guides and expects are subject to constant changes. In most cases, an enterprise architect starts from existing architecture and makes improvements. The traditional EA approach defines the to-be state architecture that may exist for a while but does not last long. By Sean (Chunhong) Gu, Chief Executive Architect at VCGĮnterprise Architecture (EA) as an enterprise planning framework has its place and merits, yet it often falls short of real-world IT expectations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |