I bomb most technical interviews if I'm being honest. I struggle quite a bit with the text book questioning part of the process, mostly with using the correct terminology. I think this is partly because I've been remote for the last 10 years and don't talk programming with other developers very often, but also I'm just the kind of guy that struggles grasping the words I'm looking for in conversation and ends up saying things in a round about way.
I'm probably in the minority here, but I prefer live coding exercises. Definitely more confident showing my competence than trying to explain it.
Planet fitness is the absolute worst offender in my mind.
I had a membership once at a location and did not close it before moving out of state. Fair to assume I could just cancel over the phone, but this is not something they would do. Apparently the contract says cancellations have to be in person at the branch you opened your membership at.
Even after explaining I was multiple states away and could not do this they refused to close my account and continued to bill me.
I asked my bank to deny all future payments to them, and this worked for a month or two before payments started getting pulled again.
this went on for over a year until I eventually went back to visit friends and was able to close the membership in person.
I can't imagine this is legal, but I guess it's probably worked out well enough for them to be worth it. I've heard the same story from a few people since this all happened.
>Generally, the "10x devs" are the ones who got to do the initial greenfield work. They are the ones who understand the system, including all the undocumented domain knowledge that has been embedded into it over the years.
I think this is exactly right. Especially when working on large projects with complex business logic.
I'm probably in the minority here, but I prefer live coding exercises. Definitely more confident showing my competence than trying to explain it.