Enterprise Architect Diane

Enterprise Architect with 5 to 8 years of experience for the Platform of the Future Program. Locations is Malvern, PA (45 Liberty and has to be in the office 2 days at week (Tuesday and Wednesday) as this is Vanguard charitable. the duration is 12 month

Additional information

Change management and transformation skills: Leading transformation initiatives requires skills in change management and the ability to communicate the vision, benefits and challenges of the new architecture to stakeholders and developement teams alike. The architect should be adept at guiding teams through the transistion and managing any resistance to change.

B. Analytical and problem solving abilities: An EA needs strong analytical and problem-solving skills to assess the existing monolithic application, identify areas for decomposition and devise an effective architecture roadmap. They should be able to anticipate challenges and provide solutions.

C. Collorabation and leadership: As an EA, collaboration and leadership skills are crucial. The architect should work closely with development teams, stakeholders, and other architects to gather requirements, align objectives and drive the implementation of the architecture roadmap.

Responsibilities

Build Enterprise architecture roadmap including:

• Capability map
• Transformation roadmap

Support and coach architecture team and drive deliverables that will roll up to the EA roadmap such as:

• Reference architecture diagrams
• Data and integration workflows
• CRUD matrices
• Conceptual, logical, physical data models
• Proofs of concept related to microservices and IPaaS initiatives

Qualifications

Proficiency in cloud platforms: the architect should have expertise in the AWS service offerings, especially those related to serverless computing, such as AWS Lambda, Amazon SNS, and Amazon SQS, DynamoDB, etc. and understand how to migrate to these patterns from more traditional application patterns

Strong understanding of architectural principles: The architect should have a solid grasp of software architecture principles, such as modularity, scalability, and maintainability. They should also be able to translate this for the business to understand the tradeoffs of the decisions being made

Experience with monolithic applications: The enterprise architect should have hands-on experience working with monolithic applications built using Java EJB and Spring Boot frameworks. They should be familiar with the intricacies of these technologies and understand how they contribute to the monolithic architecture. Additionally, the architect should have expertise in working with Oracle and PostgreSQL databases commonly used as backends for monolithic applications. This knowledge enables the architect to analyze the existing application structure, identify potential areas for decomposition into microservices, and design the integration strategies with the new serverless architecture

Expertise in microservices architecture: In-depth knowledge of microservices architecture is essential. The architect should understand the benefits and trade-offs of microservices, including their scalability, fault tolerance, and loose coupling. They should be able to design and define the boundaries of microservices effectively

Expertise in API management and API lifecycle management:

With the move towards a microservices architecture, effective API management becomes crucial. The enterprise architect should have expertise in designing and implementing an API management strategy that includes:

• API gateway solutions
• Security measures
• Monitoring
• Versioning
• Reusability
• Documenting APIs
• Fully API lifecycle management

By incorporating API management and API lifecycle management into the architecture roadmap, the enterprise architect ensures that the microservices are easily discoverable, accessible, and well-governed. This enables seamless integration between microservices and facilitates efficient collaboration between development teams and stakeholders

Knowledge of integration and communication patterns: Microservices often rely on asynchronous communication patterns like message queues and publish-subscribe systems. The architect should be familiar with messaging protocols, event-driven architectures, and patterns for integrating and coordinating between microservices and IPaaS solutions (such as Boomi)

Knowledge of Salesforce and Salesforce Financial Services Cloud: In the context of enterprise architecture, it is valuable for the architect to understand Salesforce as a platform, particularly Salesforce Financial Services Cloud. This includes familiarity with the capabilities, limitations, and integration options provided by Salesforce for financial services organizations

Ability to assess "build vs. buy" decisions: As part of the architecture roadmap, the enterprise architect should possess the expertise to assess when it is appropriate to leverage Salesforce, or other SaaS products for specific functionalities versus building a custom solution. This involves evaluating factors such as cost, time-to-market, complexity, scalability, and compliance requirements. The architect should consider the organization's specific needs and align them with the capabilities offered by Salesforce, and other SaaS providers, ensuring that the chosen approach optimizes resources and aligns with long-term goals

Strong understanding of Architecture layers: The Enterprise architect should have a strong understanding of the operational, development, application, integration, and data architecture