<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Security Architecture</title><link>http://blogs.technet.com/michael_platt/archive/2004/07/14/182857.aspx</link><description>One of the disadvantages about being the oldest in the group, apart from receding hair and growing stomach, is that I tend to get asked to do the technical part of the new candidate interviews. When we are doing lots of interviews as we are at the moment</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>RE: Security Architecture</title><link>http://blogs.technet.com/michael_platt/archive/2004/07/14/182857.aspx#182974</link><pubDate>Wed, 14 Jul 2004 22:05:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:182974</guid><dc:creator>rcallaby@nospam.earthlink.net (Richard Callaby)</dc:creator><description>Please take this as a good thing. As I have done many a technical interview in my day (it is sometimes exclusively what I am hired on to do!) I can attest to the difficulty of finding and asking the right questions in the interview. If the interviewee says that they have learned something this is usually an indicator that some rapport has been established.&lt;br&gt;&lt;br&gt;Depending on how my client wants me to interview I do not nessearily rely on the interviewee getting all technical answers correct. However, the manner in which they approach the problem is the key indicator of a good employee in my book. Technical prowess can be learned, an inituative way of looking at a problem however takes far more time and quite frankly more intelligence.&lt;br&gt;&lt;br&gt;Thanks for the good ideas on performing technical interview. I learned something from this post &amp;lt;g&amp;gt;.</description></item><item><title>re: Security Architecture</title><link>http://blogs.technet.com/michael_platt/archive/2004/07/14/182857.aspx#182981</link><pubDate>Wed, 14 Jul 2004 22:18:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:182981</guid><dc:creator>Michael Platt</dc:creator><description>Thanks Richard. How about when they bang their heads on the table!! This normally happens at the end of the interview when I tell them I am an application architect!&lt;br&gt;&lt;br&gt;I agree about the approach. I normally expect about a 50% i dont know rate, thats the nice thing about  a scenario, it leads them through a problem solving exercise where in many cases gives a good idea of how they are thinking.</description></item><item><title>re: Security Architecture</title><link>http://blogs.technet.com/michael_platt/archive/2004/07/14/182857.aspx#183288</link><pubDate>Thu, 15 Jul 2004 03:30:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:183288</guid><dc:creator>Mark Ayers</dc:creator><description>If a security guy can't talk to a business unit manager, end-user, infrastructure engineer and also understand the cryptic mind of the application architect is in trouble anyway. [wink]</description></item><item><title>re: Security Architecture</title><link>http://blogs.technet.com/michael_platt/archive/2004/07/14/182857.aspx#183743</link><pubDate>Thu, 15 Jul 2004 14:13:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:183743</guid><dc:creator>Michael Platt</dc:creator><description>That must be it. :)</description></item><item><title>re: Security Architecture</title><link>http://blogs.technet.com/michael_platt/archive/2004/07/14/182857.aspx#184676</link><pubDate>Fri, 16 Jul 2004 10:36:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:184676</guid><dc:creator>Toby Considine</dc:creator><description>An interview that doesn't leave them head-banging in non-discrimant and therefore note usefull.  I always like to see what questions they ask when stumped; that is some of the most usefull stuff&lt;br&gt;&lt;br&gt;And, alas, the security stuff sounds like another day on the job. . .</description></item></channel></rss>