<story><title>Questions I&apos;m asking in technical interviews</title><url>http://jvns.ca/blog/2013/12/30/questions-im-asking-in-interviews/</url></story><parent_chain></parent_chain><comment><author>pamelafox</author><text>I wrote a blog post on a similar topic, after mentoring several would-be engineers that were curious about finding a good fit after graduating:
&lt;a href=&quot;http://blog.pamelafox.org/2013/07/what-to-look-for-in-software.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;blog.pamelafox.org&amp;#x2F;2013&amp;#x2F;07&amp;#x2F;what-to-look-for-in-softwa...&lt;/a&gt;
That post also turned into a slide deck:
&lt;a href=&quot;https://speakerdeck.com/pamelafox/engineering-culture&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;speakerdeck.com&amp;#x2F;pamelafox&amp;#x2F;engineering-culture&lt;/a&gt;&lt;p&gt;I think we cover very similar areas. One of the big red flags for me, personally, is code review (lack thereof). If a company doesn&amp;#x27;t believe in its value, that reflects on its whole perception of coding as a collaborative process, and I just can&amp;#x27;t get on board with them.</text></comment>
<story><title>Questions I&apos;m asking in technical interviews</title><url>http://jvns.ca/blog/2013/12/30/questions-im-asking-in-interviews/</url></story><parent_chain></parent_chain><comment><author>greenyoda</author><text>These would also be excellent questions to ask yourself about your current job to decide whether it&amp;#x27;s a place where you really want to be.</text></comment>