1. 22
  1. 13

    A recruiter should never ask questions that are written down on a piece of paper they don’t understand.

    1. 3

      On another hand, my score is four on ten, that’s better than my best Google pagerank [sic]

      So funny.

      1. 3

        This post is more than a little questionable.
        It has been posted to HN a couple times (1 2).
        The consensus was that he was interviewed for an SRE position.

        1. 1

          Yeah, I got these questions ~2015 when considering a SRE position. My recruiter was a lot nicer when I explained why I thought that the sheet was incomplete though. But I would not be surprised at all if the same minds that generated that sheet of questions thought it was a good idea to screen director candidates in the same way.

        2. 2

          I’ve had a couple of pretty bad technical interviews from technical people. In those cases the interviewer wasn’t asking for a solution to the problem, but instead the exact solution that they had in their mind.

          1. 3

            I know someone who flunked a coding interview at Twitter because the graph-theory problem they used had two standard solutions (depending on what tradeoffs you cared about), the interviewer only knew one, she provided the other, and he just failed her without even checking whether it worked.

          2. 2

            I went through a similar process when interviewing with Yelp, although that was in 2014. My guess is that things are different now. I was interviewing for an iOS role; the recruiter read from a list of CS trivia questions (also featuring SIGKILL!). I stayed on the call purely out of professionalism, but it left me with a bad taste for a long time.

            1. 1

              I recently did an in-person interview where the CTO literally asked me the 13th digit of pi off the top of my head. I regret not walking out immediately.

            2. 1

              When you have to read hexadecimal packet dumps to find what’s happening, 3-letter mnemonics won’t help you to troubleshoot a dead network service.

              While I agree that his hex answer is correct… who reads packet dumps in hex when even most simplistic traffic dump tools can decode them for you? I haven’t seen anyone talk about hexadecimal flag values, no RFC does that either.

              Not that it invalidates the post as a whole, but still.

              1. 4

                To be fair, he also knows that the hex codes mean “synchronize” and “acknowledge”, and mentioned as much.

                1. 2

                  I’ve debugged network traffic flows before where I was printk-ing the raw hex output of ethernet frame headers, while attached to real network hardware running real traffic, over a serial connection. I’ve also just dumped traffic to a file and looked at it on my dev PC with a tool that parses the headers; but if you’re debugging a problem it’s sometimes very useful to just look at a printed hex digit and see if that digit is off in a way that allows you to fix the problem in context.