<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>GuiA</author><text>&lt;i&gt;&amp;gt; If you are a good developer who sucks at whiteboard interviews, write open source code that everybody can see.&lt;/i&gt;&lt;p&gt;It&amp;#x27;s been done, still doesn&amp;#x27;t get you a job.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;mxcl&amp;#x2F;status&amp;#x2F;608682016205344768&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;mxcl&amp;#x2F;status&amp;#x2F;608682016205344768&lt;/a&gt;</text><parent_chain><item><author>peter422</author><text>People lie, people embellish.&lt;p&gt;If you are a good developer who sucks at whiteboard interviews, write open source code that everybody can see.&lt;p&gt;Otherwise there is no reason an interviewer can or should trust whatever story you tell of past successes.</text></item><item><author>majormajor</author><text>For getting a job at Google&amp;#x2F;Facebook&amp;#x2F;Amazon&amp;#x2F;X cool startup, it&amp;#x27;s a lot more important to do some narrow-minded rote-memorization of algorithms and data structures and hone the skills talked about in a small set of books like Cracking the Coding Interview than to learn something really interesting, or become good at a certain thing, or build some cool shit.&lt;p&gt;Most interviewers aren&amp;#x27;t really interested in figuring out &amp;quot;is it worthwhile that you built this thing &amp;#x2F; did you do it right &amp;#x2F; why do you think this was something worth learning?&amp;quot; when it&amp;#x27;s so much easier to evaluate your whiteboard code on a narrow problem against some ideal standard solution.&lt;p&gt;You can tell them about how you were able to learn enough about a particular database in a couple weeks to be able to cut 90% of the runtime out of a hot query in your first few months at a job, since that was an area that wasn&amp;#x27;t scaling well and it was something your boss asked if you could take a look at, and they&amp;#x27;ll be like &amp;quot;ok that&amp;#x27;s nice, now implement a trie.&amp;quot; What&amp;#x27;s the point of even having experience building and running real systems if that&amp;#x27;s the process?&lt;p&gt;If you&amp;#x27;d rather be building than practicing whiteboard questions, your best path to success is probably going to be a less predictable one where you need to come across one of the right companies willing to work harder at interviewing because they have to find the best candidates who fall through the cracks at the places with the name recognition.</text></item><item><author>bogomipz</author><text>&amp;gt;&amp;quot;and seem to have followed the type of curated success-seeking golden path that used to be reserved for finance.&amp;quot;&lt;p&gt;I am curious what you meant by this. Would you mind elaborating?</text></item><item><author>dasil003</author><text>This is beautiful.  It captures the spirit of wizardry and wonder that brought me to programming in the first place, juxtaposed against the reality of interviewing at &amp;quot;top&amp;quot; tech companies where the interviewers more often than not have only a fraction of my experience, and seem to have followed the type of curated success-seeking golden path that used to be reserved for finance.</text></item></parent_chain></comment><story><title>Acing the technical interview</title><url>https://aphyr.com/posts/340-acing-the-technical-interview</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pcsanwald</author><text>Eh, I disagree. A good interviewer can dig into past experiences and pretty quickly get a sense of a candidate. Interviewing is a skill that can be acquired and developed.&lt;p&gt;Problem is, the skills you need to be a good interviewer don&amp;#x27;t necessarily overlap so well with the skill set of a good software engineer. It&amp;#x27;s much easier to get people to ask about what they know, irrespective of whether or not that will be an accurate indicator of technical skill.</text><parent_chain><item><author>peter422</author><text>People lie, people embellish.&lt;p&gt;If you are a good developer who sucks at whiteboard interviews, write open source code that everybody can see.&lt;p&gt;Otherwise there is no reason an interviewer can or should trust whatever story you tell of past successes.</text></item><item><author>majormajor</author><text>For getting a job at Google&amp;#x2F;Facebook&amp;#x2F;Amazon&amp;#x2F;X cool startup, it&amp;#x27;s a lot more important to do some narrow-minded rote-memorization of algorithms and data structures and hone the skills talked about in a small set of books like Cracking the Coding Interview than to learn something really interesting, or become good at a certain thing, or build some cool shit.&lt;p&gt;Most interviewers aren&amp;#x27;t really interested in figuring out &amp;quot;is it worthwhile that you built this thing &amp;#x2F; did you do it right &amp;#x2F; why do you think this was something worth learning?&amp;quot; when it&amp;#x27;s so much easier to evaluate your whiteboard code on a narrow problem against some ideal standard solution.&lt;p&gt;You can tell them about how you were able to learn enough about a particular database in a couple weeks to be able to cut 90% of the runtime out of a hot query in your first few months at a job, since that was an area that wasn&amp;#x27;t scaling well and it was something your boss asked if you could take a look at, and they&amp;#x27;ll be like &amp;quot;ok that&amp;#x27;s nice, now implement a trie.&amp;quot; What&amp;#x27;s the point of even having experience building and running real systems if that&amp;#x27;s the process?&lt;p&gt;If you&amp;#x27;d rather be building than practicing whiteboard questions, your best path to success is probably going to be a less predictable one where you need to come across one of the right companies willing to work harder at interviewing because they have to find the best candidates who fall through the cracks at the places with the name recognition.</text></item><item><author>bogomipz</author><text>&amp;gt;&amp;quot;and seem to have followed the type of curated success-seeking golden path that used to be reserved for finance.&amp;quot;&lt;p&gt;I am curious what you meant by this. Would you mind elaborating?</text></item><item><author>dasil003</author><text>This is beautiful.  It captures the spirit of wizardry and wonder that brought me to programming in the first place, juxtaposed against the reality of interviewing at &amp;quot;top&amp;quot; tech companies where the interviewers more often than not have only a fraction of my experience, and seem to have followed the type of curated success-seeking golden path that used to be reserved for finance.</text></item></parent_chain></comment><story><title>Acing the technical interview</title><url>https://aphyr.com/posts/340-acing-the-technical-interview</url></story>