Pradeep bhatt wrote:Thanks everyone. If you are in the interview panel, would you ask the candidate to write code.
Pradeep bhatt wrote: I have seen several architects who don't write code. I think given that they are busy having meetings and providing solutions they hardly have time to code.
Pradeep bhatt wrote:Thanks for the tip. I have met several architects at job fairs who get dislike been asked to write code by the interview panel.
Pradeep bhatt wrote:There is something called as solution architects. Do they belong to that category ?
Jeanne Boyarsky wrote:
I disagree. In companies that have a management and technical track, the architect is not a manager. He/she is a leader, yes. But the management track people still supervise.
Where I work, architects still code. Granted not as often. I have nine years experience and still code every week by myself. Plus I pair with/mentor/help solve problems of those who code more. A colleague who has been doing development 20+ years also still codes sometimes.
Palash Nandi wrote:Hi Guys, Can you tell me your portrait of a ideal architect. What skills do you look for in an architect. I am asking because, I want to get there in a few years and so i would like to try and learn those skills and i don't think, those skills are gonna magically come.
Henry Wong wrote:
No short cuts. Whether you come from the technical track, or the project management track, an "architect" is about experience -- and confidence with it. Without it, getting through the interview process will be hard. And staying in the job, if you get lucky and get it without the qualifications, will be very very hard. My best recommendation is that if you feel that you need a skill, then learn it -- and don't beat yourself over it if you just use it for one project.
Palash Nandi wrote:By experience do you mean, exposure to multiple types of projects, or multiple different companies and work culture ? Still very confused...
Henry Wong wrote:Unfortunately, the "architect" title seems to be overloaded (or maybe tiered is a more correct word). And some of those architects, such as "solution architect" and "enterprise architect" are working at such a high level, such as directly for the office of the CTO, that it is actually better (arguable) to hire a very experienced program manager for the role than a very experienced programmer. I know that you weren't referring to such an architect, but they do exist, all large companies have them.