paulkearney

Can you provide examples?

My broad (20 years) experience is that IT is usually later than forecast and often the 'business' make up the shortfall by producing miracles/take the pain.

The only point I'd disagree with is "these days". Overmanagement is the perennial problem in my experience. More do'ers less say'ers is my proposed solution.

There is the old adage of 'better to be in the tent peeing out as opposed to being outside peeing in.'

This action feels better described as 'taking a dump on the tent while blaming the tent'

I'd go with:

'What do you expect to be involved in as a software architect and what can you contribute?'

and take it from there. If you are interviewing for that role then surely what they do in the context of your organisation is key and open questions help you understand whether the person is a fit for that.