I applied for the position from their careers site. I visited their careers site based on a position that appeared on my LinkedIn feed, but ended up applying for a different position that seemed more interesting to me. I received an email from the recruiter within a couple of days expressing interest in my candidacy. From here it was three steps to the job offer. Step 1 was a phone screen with the recruiter. He explained the job at a high level going over the job description again, but focusing on areas where the environment maybe different from what I was used to - for example, if I was ok with the extent of travel required to succeed in this position. He also verified that my salary expectations were in line with Salesforce norms. Step 2 was a video call with an architect lasting about 45 minutes. I was quizzed on technical capabilities. This had more of a rapid fire format. Questions on technology infra/Middleware/frameworks that an Enterprise Architect should know were fired at me. Short, crisp response is what was expected. Step 3 was a panel interview. I was asked to make a presentation on a topic or project of my choice. The presentation was more business focused - provide context for the business problem, challenges, solution design and outcomes. I also explained my role in enabling the outcomes highlighting the competencies expected from the architect role. Once you clear step 3, you enter the offer stage. I had the opy ask questions at all stages. The recruiter helped prepare me for the interviews and was eager to see me succeed.

Recruiter Phone Interview & Process Review (30-45 mins) - Cultural fit, career alignment, and baseline communication skills. Technical & Architectural Deep-Dives (2 Interviews, 60 mins each): Focuses on large-scale data volume strategies (LDV), identity management (SSO, OAuth), integration patterns (pub/sub, ETL, real-time), and multi-org vs. single-org strategy. The Panel Interview & Case Study Presentation (90 mins) This is the crucible of the hiring process. You are usually given a complex, fictional multi-cloud enterprise use case 48 to 72 hours in advance to prepare a presentation.