I recently went through the hiring process for an AWS Architect role. The initial stages were well-structured and challenging, including multiple assessments that tested problem-solving and real-world engineering ability. I cleared all these stages, including a final interview with a senior leader. However, the experience became disappointing in the final round. Only at that stage was it clarified that the role was heavily focused on infrastructure management, RCA analysis, and on-call operations, rather than broader architecture or system design responsibilities. This was not clearly communicated earlier in the process. When I expressed interest in roles aligned with my experience (architecture, system design, and building systems), I was told this was not what they were looking for, and I was not moved forward. The main issue is not the rejection itself, but the lack of clarity around the role expectations earlier in the process. Candidates invest significant time in assessments and interviews, and this misalignment could have been avoided with clearer communication upfront.