3 phone interviews first with architect, then development team, then hiring manager. The first three went well I believe but during the in-person it was clear that something was wrong. Architect was frowning as I spoke with team.

Groping for what might have gone wrong I do have thoughts. I've been architect, lead and individual contributor and had left "architect/lead/sr. developer" at top of resume. Since the position was individual contributor I should have deleted the other two. It's never a good idea to advertise that you'd held the job of the one you'd be reporting to in the past.

The phone interview questions were fairly straightforward. I consider myself knowledgeable and think I answered almost all to architects satisfaction. Thusly the process continued. The team of two developers seemed nice and like people I would enjoy working with.

The phone interview with hiring manager went OK but he had concerns regarding my gaps which I think I managed to lay to rest. He was concerned over "taking direction" and not knowing much about me at that point I can only conclude that it was from my blunder on the resume. Later in the in-person interview it became apparent that the hiring manager had been voicing concerns of the architect.

The in-person interview was technical from architect but team members had more general questions. They wanted to hear about past projects. I had done public speaking at one point in my career and that was clearly a test geared to test the veracity of resume in general. At one point I began to get the feeling that there was a need to "knock the candidate off the horse". In speaking before user conferences I had always been able to prepare in the past so this was vastly different.

I was shown code samples and I was asked what was wrong or how it could be improved. It was a combination of subjective and objective aspects. One was a basic simple class that would have compiled.