Contacted by recruiter via LinkedIn. Set up phone interview. First time I interviewed, I thought it went pretty stellar. I forgot one concept that we absolutely never use client-side, so I couldn't finish that portion of the problem. Everything else though, which should have done enough of a job to display my skills as an OOPs programmer, was completely ignored.

The recruiter decided to give me another shot, so I interviewed with another engineer. The engineer gave me the exact same problem I was given last time. I let him know that, but we proceeded anyway. I eventually got to the end with the assistance of the interviewer, but I still left the interview confounded on how developers, especially client developers, are vetted from problems like these.

I received an email about them wanting more senior developers, but I am in fact quite senior at what I do. What I've done for my current company absolutely overshadows anything they have done, yet this is not enough because of a Leetcode problem. I'm not sure if it's laziness or a complete lack of interviewing skills that causes this, but it is time for us all to move on from it.

Something about representing a tree flow through code.