If you're really a senior developer, will you enjoy to work with C's?
Try to actively «fire» the interviewer at the first minutes of interview by showing the darkest points of your CV upfront. If you succeed, you will save 6 hours of hazing and a few months of your life after that.
I was in a team with inexperienced PM and few crooks, which negotiated 2x salary over mine, but had no skills. They hated programming, actually. I tried to help, but PM fired me instead. The project collapsed, so they started to blame me, damaging my reputation. It was an awful experience.
For me, it's easy to recognize the technical level of somebody else, because I will just ask a high-level question and then see how the discussion goes. If they say «Okey, now tell me about your experience», then they are definitely not A's.
You cannot bullshit A's, so bringing your weak points to the table upfront will give you some credibility in the eyes of A's, but it will do the opposite in the eyes of B's. It's detailed in "Getting naked"[0].
If you are doing consultation and want satisfied clients only, or looking for an A level job only, then it's OK. If you are looking for any job (with high salary, of course), then it better to hide your weak points, to be accepted by a B, and then do the dull work.
I'm sorry to veer off topic but is anyone else infuriated that a brand new hard cover edition of this book is $13 (or as low as $7 from other sellers) but the Kindle version is $15? I don't even own a Kindle but that's ridiculous pricing.
It's immaterial because the 6 hours of hazing, which resembles nothing like what one would encounter on the job, is the bad part. Is the point of a hiring process to hire people who can regurgitate algorithms on a whiteboard in 45 minutes, or is it to find the people who are best able to do the job you're hiring for among the people who are willing to come work for you?
