<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Interviewing tips</title><link>http://blogs.msdn.com/b/jcalev/archive/2006/11/09/interviewing-tips.aspx</link><description>I will take a brief step away from globalized speech applications today and talk about some tips for interviewing. These tips may or may not help you when interviewing at Microsoft because I differ sharply from many of my colleagues on how to interview</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Interviewing tips</title><link>http://blogs.msdn.com/b/jcalev/archive/2006/11/09/interviewing-tips.aspx#1064851</link><pubDate>Mon, 13 Nov 2006 02:26:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1064851</guid><dc:creator>SReddy</dc:creator><description>&lt;p&gt;Thanks for sharing the details openly. I was interviewed last year and not selected at MS because each interviewer focussed on their own Complex data structure during their 45 min time slot :) At the end of the day i thought the interviewers should differentiate between a college out guy and an experienced guy..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1064851" width="1" height="1"&gt;</description></item></channel></rss>