<story><title>Technical and non-technical tips for rocking your coding interview</title><url>https://github.com/yangshun/tech-interview-handbook?utm_campaign=explore-email&amp;utm_medium=email&amp;utm_source=newsletter&amp;utm_term=weekly</url></story><parent_chain><item><author>kafkaesq</author><text>&lt;i&gt;2. What happens between you typing a URL into your browser address bar, hitting enter and seeing a web page?&lt;/i&gt;&lt;p&gt;&amp;quot;What happens when I&amp;#x27;m asked a question like X?  I spout a mutated form of some canned response I cribbed from a list I found on HN a while back.  Because I hear that&amp;#x27;s how you&amp;#x27;re supposed to &amp;#x27;rock your coding interview&amp;#x27;, these days.&amp;quot;&lt;p&gt;&lt;i&gt;3. What are the things you should consider if you were writing your own database server?&lt;/i&gt;&lt;p&gt;&amp;quot;Look, you know as well as I that this job has nothing -- as in, &lt;i&gt;nothing whatsoever&lt;/i&gt; -- to do with actually building production-grade database servers.  Or anything even remotely analogous to it.  Debugging that tangled mess of poorly conceived, never-reviewed JSON APIs left behind by the other developer (while you were pestering them about &amp;#x27;disruption&amp;#x27; and &amp;#x27;just needing to get this thing to market&amp;#x27;) is more like it.&amp;quot;&lt;p&gt;&amp;quot;But hey, since you&amp;#x27;re playing that game, I can play too:  here&amp;#x27;s a bunch of catchphrases like &amp;#x27;non-blocking I&amp;#x2F;O, sharding, blah blah.&amp;#x27;  Because I hear that&amp;#x27;s the killer answer to give to questions like these.  And BTW, if you really think that people Michael Widenius or Salvatore Sanfilippo would be interviewing for this job, then your problems are way bigger than I could ever hope to help you with.&amp;quot;</text></item></parent_chain><comment><author>wh-uws</author><text>Some permutation of this comment is made litterally everytime any coding interview resource is posted.&lt;p&gt;I&amp;#x27;m sorry man no cares that you and everyone who upvoted this comment are Super God programmers with 30 offers everytime they say they are looking who can afford to tell every company where they can stuff their interview.&lt;p&gt;Us mere mortals are willing to do whatever it takes to get our dream gigs.&lt;p&gt;These guides are largely targeted are getting into the some of the best, thus pickiest and most selective, companies in the world.&lt;p&gt;And if getting on means being a dsalgo monkey in front of a whiteboard for a few hours so be it.&lt;p&gt;Let us share interview tips in peace please.&lt;p&gt;This &amp;quot;hurr durr technical interviews suck&amp;quot; but I have no real alternative and have never built a company nor seen any really flourish at the top without this is monotonous.&lt;p&gt;Put your money where your mouth is and start and only support companies that skip these kinds of interviews.&lt;p&gt;Like these fine people&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;poteto&amp;#x2F;hiring-without-whiteboards&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;poteto&amp;#x2F;hiring-without-whiteboards&lt;/a&gt;&lt;p&gt;But the snarky comments are beyond annoying.</text></comment>
<story><title>Technical and non-technical tips for rocking your coding interview</title><url>https://github.com/yangshun/tech-interview-handbook?utm_campaign=explore-email&amp;utm_medium=email&amp;utm_source=newsletter&amp;utm_term=weekly</url></story><parent_chain><item><author>kafkaesq</author><text>&lt;i&gt;2. What happens between you typing a URL into your browser address bar, hitting enter and seeing a web page?&lt;/i&gt;&lt;p&gt;&amp;quot;What happens when I&amp;#x27;m asked a question like X?  I spout a mutated form of some canned response I cribbed from a list I found on HN a while back.  Because I hear that&amp;#x27;s how you&amp;#x27;re supposed to &amp;#x27;rock your coding interview&amp;#x27;, these days.&amp;quot;&lt;p&gt;&lt;i&gt;3. What are the things you should consider if you were writing your own database server?&lt;/i&gt;&lt;p&gt;&amp;quot;Look, you know as well as I that this job has nothing -- as in, &lt;i&gt;nothing whatsoever&lt;/i&gt; -- to do with actually building production-grade database servers.  Or anything even remotely analogous to it.  Debugging that tangled mess of poorly conceived, never-reviewed JSON APIs left behind by the other developer (while you were pestering them about &amp;#x27;disruption&amp;#x27; and &amp;#x27;just needing to get this thing to market&amp;#x27;) is more like it.&amp;quot;&lt;p&gt;&amp;quot;But hey, since you&amp;#x27;re playing that game, I can play too:  here&amp;#x27;s a bunch of catchphrases like &amp;#x27;non-blocking I&amp;#x2F;O, sharding, blah blah.&amp;#x27;  Because I hear that&amp;#x27;s the killer answer to give to questions like these.  And BTW, if you really think that people Michael Widenius or Salvatore Sanfilippo would be interviewing for this job, then your problems are way bigger than I could ever hope to help you with.&amp;quot;</text></item></parent_chain><comment><author>ptero</author><text>I think many technical interviews are simply trying to assess whether the candidate has his head screwed on straight and the ability to do basic engineering. As such, the specific topics are practically irrelevant.&lt;p&gt;At least that&amp;#x27;s what I try to do when I end up interviewing someone. For example, can he suggest what sensors would be good for a Lego robot that would knock a tennis ball off the ping pong table without itself falling off? Can he describe the logic? How would he test this? How long, on average, would it take? What position of robot and ball would give the worst case performance (success or time)? His job will not involve Lego robots, but IME the person who can give sane answers on those would do a lot better than a coder who knows one toolkit well and nothing else.</text></comment>