Enterprise Solutions Architect

Job Summary The Architect II - Enterprise Solutions role focuses on designing and optimizing applications within ERP/CRM systems to transform them into scalable solutions. This position involves selecting appropriate technical development options, identifying and improving technical design patterns, and optimizing efficiency, cost, and quality. The role requires interpreting application designs to develop them according to specifications, validating results with user representatives, and integrating solutions. A key aspect is influencing customer satisfaction through proactive suggestions, code refactoring, and early sprint deliverables, as well as fostering employee engagement and staying updated with new technologies. This role is also responsible for conducting peer reviews, contributing to practice‑related activities, performing technical assessments for hiring, and ensuring industry best practices are adopted. The individual will design, execute, and maintain business domain solution architectures, guide technical delivery, resolve design issues, and own the design of complex modules for various project types. Serving as a technology and process expert, the role leverages enterprise solutions expertise to enhance the ERP/CRM practice. Key Responsibilities Review design and optimize applications transforming into scalable solutions in ERP/CRM systems. Select appropriate technical options for development. Identify problem patterns and improve the technical design of applications/systems. Optimize efficiency, cost, and quality. Interpret application/feature/component designs to develop them in accordance with specifications. Validate results with user representatives, integrate, and commission the overall solution. Influence and improve customer satisfaction through suggestions for code refactoring and business process improvements, and by completing sprint deliverables ahead of time. Influence and improve employee engagement within project teams. Learn and implement newly released technology features. Attend industry/technology specific conferences and share knowledge. Conduct peer reviews and ensure high‑quality standards. Contribute to ERP/CRM Practice related activities, such as assembling content for case studies and coordinating internal seminars. Conduct technical assessments for hiring candidates in architect/lead roles. Review designs and ensure adoption of industry best practices. Design, execute, and maintain business domain solution architecture. Guide and review technical delivery by internal teams. Resolve delivery and design issues. Own the design of a complex module for projects involving architecture enhancements, mid‑sized development, or maintenance. Serve as a technology and process expert. Use expertise and skills in enterprise solutions technologies to develop/enhance the ERP/CRM Practice. Define Architecture for mid‑sized projects. Design the technical framework and implement it. Identify and conduct design of complex sub‑components/modules in collaboration with project team architects and client SMEs. Present detailed design documents to stakeholders and seek feedback. Undertake project‑specific Proof of Concepts to validate technical feasibility. Optimize solutions and resolve performance issues. Support the team in designing functional modules and review deliverables. Conduct code reviews. Clarify requirements and provide guidance to the development team. Present design options to customers. Conduct implementation reviews with stakeholders. Work closely with customer architects for finalizing designs. Proactively influence customer thought processes. Manage all aspects of problem management, investigating root causes and recommending SMART solutions. Maintain software process improvement activities and communicate them to various individuals, teams, and entities. Advise software developers on design and development with a deep understanding of the business problem. Learn about customer domains and identify opportunities for value addition. Understand functional and non‑functional requirements. Collect non‑functional requirements through discussions with SMEs and business users. Identify technical aspects as part of story definition, especially at an architecture or component level. Share technical inputs from an Agile/project planning perspective with SCRUM Masters/Project Managers. Help SCRUM Masters/Project Managers understand technical risks and develop mitigation strategies. Help developers overcome technical challenges. Analyze the technology landscape, processes, and tools based on project objectives. Understand application architecture criticality to analyze and assess tools. Support architects in drafting recommendations based on Proof of Concept findings. Analyze and identify new developments in existing technologies. Document new developments to build team capabilities. Provide support for project estimations and sprint/component level estimates. Articulate estimation methodology and module‑level estimations. Contribute to proposal development from a technology/architecture perspective. Conduct technical trainings/webinars to impart knowledge. Create collaterals such as case studies and business value documents. Contribute to the knowledge repository and tools. Create reference architecture models, reusable design patterns, and reusable components. Identify avenues to improve project delivery parameters using tools and automation. Understand technical tools used in projects to improve efficiency and productivity. Required Qualifications Demonstrates thorough knowledge of end‑to‑end SDLC process (Agile and Traditional). Demonstrates thorough knowledge of SDLC methodology, programming principles, tools, and best practices (refactoring code, code packaging, etc.). Specialized knowledge in estimation and resource planning techniques (e.g., TCP estimation model, case‑based estimation, scenario‑based estimation, work breakdown structure estimation). Applies specialized knowledge of requirements gathering for non‑functional requirements and analysis for functional and non‑functional requirements. Familiarity with requirements analysis tools (e.g., functional flow diagrams, activity diagrams, blueprint storyboards). Familiarity with techniques such as business analysis and process mapping. Familiarity with requirements management tools (e.g., MS Excel). Basic knowledge of functional requirements gathering. Proactively identify solutions for technical issues. Ability to maintain technical evaluation procedures. Ability to estimate project effort based on requirements. Perform and evaluate test results against product specifications. Break down complex problems into logical components. Ability to interface with other teams, designers, and parallel practices. Ability to set goals for self and team. Ability to provide feedback for team members. Ability to create and articulate impactful technical presentations. High level of business etiquette in emails and other business communication. Ability to drive conference calls with customers and answer customer questions. Ability to work under pressure, determine dependencies, manage risks, and facilitate planning while handling multiple tasks. Ability to build confidence with customers by meeting deliverables in time with quality. #J-18808-Ljbffr