Yahoo Architect interview questions

I was called up for the architect position. After briefly asking me about my previous projects, it straightaway went to strategies for searches for huge number of web pages followed by searches in huge files. I explained that I have never done such a thing and gave it a try. The interview was abruptly cut within 20 minutes making it clear that I am not answering to the interviewers satisfaction.

An employee referred me to an Architect level software engineering position within the company. A couple weeks after he forwarded my resume to the hiring manager, I received an initial phone call from the hiring manager. The hiring manager was pleasant and very easy to speak with. We made plans for phone interviews and on-site interviews. The manager sent me an official job description. The job description clearly indicated that the job was an "architect" level position. However, my on-site invitation referred to the position as a "Sr Principal Engineer" role. Later, the recruiter verbally confirmed that Yahoo would offer me a "Principal Engineer" position. Is this a bait-n-switch act. I don't know for sure, but I don't like the initial feelings I have about it. Over the course of a week, the architect job has disappeared and has rematerialized as a job title 2 or 3 levels lower. This simply does not agree with my initial expectations for the job role and title.