Solution Architect

Designation

Experience

Roles and Responsibilities Solution Architect

• Bridges business need and technical execution.
• Detailed requirement elicitation with the functional team.
• Breaking down the high level functional requirements to epic, features and user stories.
• Based on experience and discussion with Technical Architect team, deciding if solution has to be implemented in Platform, Payments Product (core or rail).
• Breaking down the approach and detail design documentation.
• Detailed solution walk through to developers and testers explaining with use cases.
• Generic approach design validation with stakeholders (ARB team, Solution Team, PO (all rails))
• Reusable approach implementation design.
• Based on Customer requirement, give recommendation for implementation approach. This could be a feature already available in product which may require configuration change or could be a custom solution for which design details to be provided.
• Available to Customer team, Pre Sales team or stakeholders for clarification of Payments Product functionality.
• Available to the team which interact with customer to understand the initial customer requirement. Based on interaction with stakeholders creating the split up of features and stories. Categorizing the user stories based on product or customization.
• Coordinating with different stakeholder to ensure end delivery of each and every requirement taken up for solution.
• Have end to end knowledge about the functionalities available in Payments Product and Platform.
• End to end understanding of Single SDK/Centralized structing and coding practice.
• Understanding of Payments Product repository structure, branches available, DevOps build pipeline.