    <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
     <channel>
        <title>ACCU  :: I Can't Think Fast Enough in a Coding Interview</title>
        <link>https://members.accu.org/index.php/articles/2371</link>
        <description>Professionalism in Programming</description>
        <dc:language>en-us</dc:language> 
        <dc:creator>Administrator</dc:creator> 
        <admin:generatorAgent rdf:resource="http://www.xaraya.org" /> 
        <admin:errorReportsTo rdf:resource="mailto:webeditor@accu.org" />
       <sy:updatePeriod>hourly</sy:updatePeriod>
       <sy:updateFrequency>1</sy:updateFrequency>
       <docs>http://backend.userland.com/rss</docs>




<div class="xar-mod-head"><span class="xar-mod-title">Process Topics + CVu Journal Vol 29, #2 - May 2017</span></div>

<table border="0" cellpadding="1" cellspacing="0">
    <tbody>
    <tr>
        <td valign="top">
            Browse in :
       </td>
       <td valign="top">

                                            <a href="https://members.accu.org/index.php/articles/">All</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c13/">Topics</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c221/">Process</a>
<br />

                                            <a href="https://members.accu.org/index.php/articles/">All</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c76/">Journals</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c77/">CVu</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c373/">292</a>
<br />

                                            <a href="https://members.accu.org/index.php/articles/c221-373/">Any of these categories</a>

                    -                        <a href="https://members.accu.org/index.php/articles/c221+373/">All of these categories</a>
<br />
</td>
   </tr>
   </tbody>
</table>




<div class="xar-error">
   <p>
 <strong>Note:</strong> when you create a new publication type,
the articles module will automatically use the templates
<em>user-display-[publicationtype].xt</em>
and <em>user-summary-[publicationtype].xt</em>.
If those templates do not exist when you try to preview or display a new article,
you'll get this warning :-)  Please place your own templates in themes/<em>yourtheme</em>/modules/articles . The templates will get the extension .xt there. </p>
</div>
<div class="xar-norm xar-standard-box-padding">
   <h1><strong>Title:</strong>&nbsp;I Can't Think Fast Enough in a Coding Interview</h1>
<p><strong>Author:</strong>&nbsp;Martin Moene</p>
<p>
<strong>Date:</strong> 04 May 2017 09:22:31 +01:00 or Thu, 04 May 2017 09:22:31 +01:00</p>
<p><strong>Summary:</strong>&nbsp;Sean Corfield shares his thoughts on the technical interview process.</p>
<p><strong>Body:</strong>&nbsp;<p>â€˜Practiceâ€™ is not the answer. â€˜Cracking the Coding Interviewâ€™ is not the answer. A few people have said it â€“ and more of us should be saying it: these â€˜coding monkey interviewsâ€™ are stupid. They do not determine how good a programmer someone will be once theyâ€™re actually hired and working. The big companies that use them have finally started to admit this. The hiring process is broken and we need to stop participating in this silly game so many companies have adopted because theyâ€™re too lazy to figure out how to interview people effectively. Iâ€™ve refused to interview with companies that do this and Iâ€™ve walked out of interviews that have turned out that way. If a company really believes a quick fire â€˜coding monkey interviewâ€™ will find them the â€˜best programmersâ€™ then that is a company you want to avoid â€“ they donâ€™t understand their engineers, they donâ€™t know what makes a good team.</p>

<p>Remember that the interview is a two-way street. You are interviewing the company as much as they are interviewing you. An interview should be a conversation about what you enjoy in a software project, in a team, in a manager â€“ as well as what you find problematic. It should be a chance for you to talk about how you approach problems â€“ both technical problems and people problems â€“ how you balance trade offs, and how you deal with things that donâ€™t go your way. You should be able to defend your choice of technology but you should also know it well enough to be able to talk about its flaws or the situations where it isnâ€™t such a good fit. You should be able to ask about the companyâ€™s processes, how they manage teams, how they resolve conflict, how they reward success.</p>

<p>An interview should reflect the sort of collaborative process you can expect once you are an employee at that company. If an interview seems to be a confrontational process, assume thatâ€™s how the company will treat you once youâ€™re hired.</p>

<p>Iâ€™ve been a hiring manager for about twenty years now. I do not do â€˜coding monkey interviewsâ€™ because I know they do not work. And I have never hired anyone that canâ€™t do the job Iâ€™ve hired them for.</p>

<h2>Reference</h2>

<p><a href="https://www.quora.com/Im-a-software-engineer-with-20-years-experience-but-I-cant-think-fast-enough-in-coding-interview-What-should-I-do/answer/Sean-Corfield?share=1587c4af#">https://www.quora.com/Im-a-software-engineer-with-20-years-experience-but-I-cant-think-fast-enough-in-coding-interview-What-should-I-do/answer/Sean-Corfield?share=1587c4af#</a></p>
</p>
<p><strong>Notes:</strong>&nbsp;</p>
<p><em>More fields may be available via dynamicdata ..</em></p>
</div>
</channel>
</rss>
