Thanks for sharing your thoughts, and congrats on nderground.
upeka bee

My experience has been that there’s no shortage of software engineers. Employers don’t adjust their process, since they appear to be able to find a candidate who fits their criteria, what ever that might be.

I developed one of the first graph databases. I also have a lot of background in computer language processing (I also developed a graph query language). I talked to one company that was looking for someone to work on their GraphQL database.

The interview consisted of someone with a heavy French accent grilling me about where IP addresses were located in an HTTP packet/transaction. I had done a little bit with HTTP IP addresses, since nderground does some limited IP address tracking (to help find possible security breaches). But apparently what I had done was not sophisticated enough to handle cases of IP address obfuscation via proxies.

I later pointed out that this had nothing to do with what I had to offer the company (which was graph database expertise, in this case). Their response was, more or less, that everyone should know about HTTP packet format. And presumably if you didn’t know this, you were completely unqualified to work at their company.

In many cases small companies assign people to do interviews who have no idea what their doing or even what the objective of interview process should be. The result is that the people who do the interviewing hire people who are just like them.

I am somewhat in awe of your experience, upeka bee, since during the periods where I’ve done a lot of interviewing I have not had multiple job offers. I’m not sure if this is do to my areas of expertise, my interviewing skills or my age. I’ve read books like Gayle Laakmann McDowell Cracking the Coding Interview. But it didn’t seem to help.

Yet I have the skills to build a scalable social network, hosted on AWS…

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.