I applied on www.homeserve.com site March 10 2021 soon after I completed my AWS Certified Solutions Architect Associate Certification. I thought the certification would go well with the Azure experience I have with AppSevices (WebApp, WebJob, logical and durable Function), Cosmos, API Gateway Blob and others services experience. There were a total of 5 interviews starting with HR. The HR interview was a screening interview scheduled for April 23. The second interview was with the Business Solutions Architect & Shared Services Leader in the US. This was a pleasant interview where he ran the down the team structure. HomeServeUS seems to be in need for more resources as there are many acquisitions occurring where those capabilities require a look and possible attention with minimal business interruptions while managing business concerns. I ran down my back ground which was in inline with what they need. A person that work with on-premise legacy that had the potential for cloud. My experience is both green field and migration of solutions for Azure, AWS some GCP. In this interview there was mention the need to change how they worked. Architects driving and delivering on signification architectural requirement for the business and project versus going deep in design and coding. Somewhere in the conversation I recall home serve having what I thought was similar to workforce optimization piece. A system to manage work orders from start to finish, the ability to schedule work, swap work orders etc.. The third interview was with who I initially thought was a middleware architect out of the UK . He explained his role was enterprise architect. He explained the manner in which HomeServe project life cycle moved and I found similar to the previous enterprise I worked with. Project Manager with business analyst providing BRB (requirement) where the architect's main goal is to vet not only the function requirement but the important non-functional requirements (security/availability/performance). The artifact delivered during the project cycle conceptual / HLD and logical / LLD documents. The architecture is review in a show and tell / architectural review board meeting. I would imagine the HLD architecture review meeting is more so business resources and the LLD architecture review meeting is more so QA / tech / dev leads to allow their input. The forth interview was with Director of Information Security at HomeServe USA and an alumni of the same University. He spoke how his team support the solutions architect. I explained how at my previous position the preference center and our .com site began using OKTA as identity access management of loyalty profiles where there were orchestration to manage session JWT and refresh token. The fifth and final interview was with the VP of the application team. I was asked a questions similar to, Can you describe a stressful situation and how you handled it? In the end the decision was made by HomeServe to pursue other candidates.