work architect

Architects: If you can't code, don't apply for senior dev jobs

There seem to be several different understandings of the job title "Architect". The company I work for sees this as a position that involves coding, research, management of developers, and setting of technical direction. Others apparently treat this as a pure management or management/analyst title. Okay, fine, to each their own.

However, if you are a non-coding architect, please don't tell your recruiter you're interested in senior developer positions. We require all our developers to pass a written coding test, and several times now I've seen people give answers like "I've been working as a system architect for several years now and am not really a hands-on developer anymore". "Senior Developer" is clearly a coding position, so what good is a non-coding analyst/manager for this job?