<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Coding the Architecture - interviewing tag</title>
  <link>http://www.codingthearchitecture.com/tags/interviewing/</link>
  <description>Software architecture for developers</description>
  <language>en</language>
  <copyright>Coding the Architecture</copyright>
  <lastBuildDate>Wed, 16 May 2012 08:01:04 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Interviewing architects</title>
    <link>http://www.codingthearchitecture.com/2006/03/01/interviewing_architects.html</link>
    
      
        <description>
          &lt;p&gt;
In &lt;a href=&#034;http://getahead.ltd.uk/blog/joe/2006/03/01/1141219345542.html&#034;&gt;Architect Level Interview Questions&lt;/a&gt;, Joe Walker shares some of the interview questions that he uses to quiz architects. For me, the comment that sums up the essence of Joe&#039;s questions is as follows.
&lt;/p&gt;

&lt;blockquote&gt;
These are not trick questions - there is generally no one correct answer; just opinions.
&lt;/blockquote&gt;

&lt;p&gt;
Whenever I interview architects, I always go for the open questions too. Some of my current favourites include &#034;how would you define architecture?&#034;, &#034;what are the responsibilities of an architect?&#034;, &#034;how do you start chasing down a performance problem in a J2EE system?&#034; and &#034;how do you take requirements through to design?&#034;. Open questions allow you to really get involved in a two-way dialogue, which subsequently lets you explore and get a feel for experience. Of course, like Joe, I still like to throw in a few very specific technology questions (if applicable) to ensure that they *do* have experience with technology X.
&lt;/p&gt;

&lt;p&gt;
I really enjoy interviewing because it&#039;s a great way to learn about other architectures and helps broaden *my* experience. If you interview architects, what are your favourite questions?
&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>What is the the role of a software architect?</category>
    
    <comments>http://www.codingthearchitecture.com/2006/03/01/interviewing_architects.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/03/01/interviewing_architects.html</guid>
    <pubDate>Wed, 01 Mar 2006 18:18:54 GMT</pubDate>
  </item>
  
  </channel>
</rss>

