Coding Challenges

In rare occasions, there are jobs that attempt to simulate what you'll do day to day, distilled into a few hours in an interview; and in every case I've heard they're unrealistic and ablest -- even with attempts to accommodate for disabilities.

It isn’t productive to just lament that the industry wasn’t made for me, thankfully I’ve built a great career for myself, but occasionally I enter the fray. Here’s a list of my most notable exercises:

Check out my reading list to see what I’ve been doing to level up in my full stack engineer skills.


Q. Systems Architecture Interview: "Create a Logger"


System Design : How to design a distributed logging? -

Scalable and Reliable Logging at Pinterest (DataEngConf SF16) -

Part 1: Building a Centralized Logging Application -

Q. Live Coding Python : Create an anagram checker

Q. Live Coding JavaScript : Look at this data tree representing parents and children. Please create a function that returns all of the childlessPerson (s) and singleParent (s)


I hate coding challenges. I’m morally opposed to being tested on things that don’t directly translate to practical day to day skills. There is no fool proof way to vet a candidate to make sure they’re able to perform the first day on the job — nor should there be. You’re investing in the capabilities of a *human* not a bot that churns out code to your feature specifications. You’re hiring them for their experience and aptitude.

What ends up happening is you’re rejecting great candidates who don’t have time to practice coding challenges in the same fashion one would study for the GRE, SAT or another standardized test. Hiring managers have no idea what they’re doing and it shows.

*sigh* while I’m coordinating lining up every Engineering HR department to do a cartoonish row of slaps all the way down the line, I practice some coding exercises and try not to take it personally that the industry was not made for me.