Solutions Architect

Solutions arch role is for the verticals that Steven owns--com client life cycle and onboarding--this is functional area. Nilesh has tech area--for example, Appian or similar, AWS or similar. Sol Arch not hands on developer. Need someone who understands what com client life cycle is--especially as it relates to workflows in a bank--and what are challenges, business requirements for solutions, etc. Sol Arch should understand constraints and boundaries that one needs to think about when designing a solution. More focused on client life cycle and workflows to this space--Appian is the front end for all interactions. For the next 3 years, there is going to be a big effort to modernize and consolidate all their applications and platforms across 3 branded banks. Long term strategy is to build app's and consolidate where they can. It would be great if architect had experience with Appian and Fenergo but the bigger pic is that they want this person to design the platforms that they are going to move forward with over the next 3 years. Most important is that they are a sol arch skilled person who has a vision to be able to build and design modern banking platforms. Don't want to pigeon hole someone as Appian architect.

For example, someone who is sol arch who knows business process mnmgt in banking and workflow automation--maybe they don't know Appian so well but they know workflow. Maybe they know Pega instead of Appian.

This role is going to be under David's vertical and Nilesh and Steven will be sharing this resource. This sol arch will also partner with Enterprise Architecture Group, which will be putting recommendations around best practices, policies, compliance items to adhere to so that they have standardization across the bank. This group is very technical so interaction with this group requires someone who is strong and good at selling their solution to this group. Person must be experienced and senior enough to communicate their designs to this group so that the solution gets approved. Otherwise, the design approval gets stuck in their governance cycle and it impacts their project. If the design is not clear, then it will get delayed.

For example, group will ask them to fix the API integration or go back and put more details around Kofka and database or details about security, etc. They will hire this person down the road. Phx, Dallas or Austin, Raleigh (FCB hubs) are highly preferred b/c they will want the person to come into the office at times to white b