I can't remember the numbers of times that I would quickly read up on a topic / language / technology the prospect was using the night / morning before the meeting, then during the meeting try to sound like an expert in the topic. I know exactly how convincing I was, but I was never called out enough during the meeting to out me.
I'm the technical guy on the other side of the table. We don't call people out of politeness - just smirk and enjoy the ride. After the meeting we talk freely to people in charge and destroy all your hopes of sale.
We knew we (collectively as a team) weren’t experts in everything, but the prospects called for expertise in x, y and z. Most of the time we knew a lot about x and y but not much about z. But at the same time we also knew no one is a perfect fit and we were pretty good for the job. In a lot of ways it’s very much like most interviews. It’s a back and forth of some BS and attempts to detect BS. The BSing wasn’t always successful I’m sure, but seemed necessary in most cases.
I certainly understand that when expertise in topics A, B and C are necessary to get in the door, you do the best you can. Getting a handle on the basics of a tertiary topic so you can start the conversation and focus on your legitimate strengths is a far cry from throwing up a smoke-screen in front of a potential client to push a sale.
Thanks for the follow up.
We had a laugh about it with our line manager the other day. He was leading that interview.
Most likely I was not asked for real details, which makes me question the effectiveness of the interviewers back then.
"Scaling a service to millions of requests per second? Sure, you will need X, Y, and Z."
Now, on the other side of the table, I am quick to spot the bullshit.
Also, I realize how criminal those interviews were back then. I was answering architect level questions asked by a senior engineer when applying for a junior level position.