<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>benlivengood</author><text>I&amp;#x27;ve interviewed folks for FAANG roles.  If you know how to solve the problem already, just tell the interviewer up front.  Either they have another question or they will go deeper into a discussion about why and how you solved it the way you did, testing it, other approaches and why they are or are not good tradeoffs, etc.&lt;p&gt;It&amp;#x27;s pretty obvious to interviewers if you&amp;#x27;ve solved a problem before, and we appreciate the honesty.  Interviews are not adversarial; they&amp;#x27;re to see if a candidate is a good fit for the role and dishonesty is never a good fit.</text><parent_chain><item><author>mrfusion</author><text>I’ve gotten interview questions I’d recently solved and my problem was it was too easy. I had trouble acting like it was the right amount of struggle. Is there a trick for that?</text></item><item><author>arduinomancer</author><text>Interviews are really a dumb game these days so if you want to really game it you can go with a statistical approach:&lt;p&gt;* Practice questions by company on LeetCode, sort by frequency of last 6 months and work down the list, do maybe 75-100, the list updates once a week&lt;p&gt;* Search for the company on the LeetCode forums and sort by most recent. If a question is not on LC yet it will likely get posted there, so you can get really fresh intel.&lt;p&gt;I&amp;#x27;ve read of people doing this and getting like 6&amp;#x2F;6 questions they&amp;#x27;ve seen before.</text></item></parent_chain></comment><story><title>An Algorithm for Passing Programming Interviews (2020)</title><url>https://malisper.me/an-algorithm-for-passing-programming-interviews/</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>kortilla</author><text>Empty your bowel into your underwear. It’s all a show anyway, at least make it a good one.</text><parent_chain><item><author>mrfusion</author><text>I’ve gotten interview questions I’d recently solved and my problem was it was too easy. I had trouble acting like it was the right amount of struggle. Is there a trick for that?</text></item><item><author>arduinomancer</author><text>Interviews are really a dumb game these days so if you want to really game it you can go with a statistical approach:&lt;p&gt;* Practice questions by company on LeetCode, sort by frequency of last 6 months and work down the list, do maybe 75-100, the list updates once a week&lt;p&gt;* Search for the company on the LeetCode forums and sort by most recent. If a question is not on LC yet it will likely get posted there, so you can get really fresh intel.&lt;p&gt;I&amp;#x27;ve read of people doing this and getting like 6&amp;#x2F;6 questions they&amp;#x27;ve seen before.</text></item></parent_chain></comment><story><title>An Algorithm for Passing Programming Interviews (2020)</title><url>https://malisper.me/an-algorithm-for-passing-programming-interviews/</url></story>