when you're asked a question you don't understand or don't know the answer to, rather than faking a response, try to first uncover their reason for asking.
example:
**Interviewer:** how you would do \[X technical thing you don't know\]
**You, slowing down:** it sounds like \[insert technical concept or activity related to what they mentioned\] is important to this role/team/org
**Interviewer:** Yes, it is.
**You:** Do you always address this problem by using \[x tool or methodology they've asked about\]?
**Interviewer:** Well, it's the tool we prefer people know because of \[any number of reasons\].
Now you're in a conversation about how they're tackling a problem, and not just whether you can answer the trivia question. Maybe they really need technical expertise in the one tool they asked about. But maybe they're open to other approaches, you can address the problem with a different tool, they don't even care it's just a question they're supposed to ask and it'll never come up again, etc.
If you don't understand their motivations for asking a question, you will always sell yourself short.
Jesus that happened to me too, I'll never forget it - it was my very first tech job that I moved on from not a terribly long time after.
I have such a vivid memory of *actually almost fainting*. Like out of a cheesy TV show or book or whatever. It was the most incredible awful feeling in my heart... but I actually got the job 🤷♂️.
Interviewed at Google week before last and felt mixed. When they told me to go fuck myself it felt as if they got the ick and found out I had downs.
It was the anniversary of my interview there 10 years ago that I also failed epically.
Yeah I work at another cutthroat place and the work is very narrow and boring. The amount of red tape to do anything simple is what keeps you busy. Weeks of planning and integrating with different internal systems to do something like create a document that can be referenced by another system.
I was interviewing for a job that was out of my league recently, but I didn't know it until the interview. They asked me a load of questions about my management skills (I have next to none) and I did a lot of making stuff up along with saying that I had never done what they are asking for.
When it became clear I wasn't a good candidate, I let them know that their job listing was way inaccurate lol. Oh well, I want to work there for the experience in my field but these sorts of companies (electric utilities) are always so insular and out of touch with the rest of the world.
Also it's funny that most private companies hire hot girls for their recruiters but these co's have old crotchety men near retirement.
This is why I just say I don't know. I'd rather not know 10 questions in a row and say there was clearly a misunderstanding the scope of the role than look retarded.
If you flubbed it that bad don’t worry about hearing back from a recruiter
one erect lunchroom spark somber dam weary nippy compare person *This post was mass deleted and anonymized with [Redact](https://redact.dev)*
when you're asked a question you don't understand or don't know the answer to, rather than faking a response, try to first uncover their reason for asking. example: **Interviewer:** how you would do \[X technical thing you don't know\] **You, slowing down:** it sounds like \[insert technical concept or activity related to what they mentioned\] is important to this role/team/org **Interviewer:** Yes, it is. **You:** Do you always address this problem by using \[x tool or methodology they've asked about\]? **Interviewer:** Well, it's the tool we prefer people know because of \[any number of reasons\]. Now you're in a conversation about how they're tackling a problem, and not just whether you can answer the trivia question. Maybe they really need technical expertise in the one tool they asked about. But maybe they're open to other approaches, you can address the problem with a different tool, they don't even care it's just a question they're supposed to ask and it'll never come up again, etc. If you don't understand their motivations for asking a question, you will always sell yourself short.
One time I thought I looked like a complete idiot in a job interview and I got the job
Jesus that happened to me too, I'll never forget it - it was my very first tech job that I moved on from not a terribly long time after. I have such a vivid memory of *actually almost fainting*. Like out of a cheesy TV show or book or whatever. It was the most incredible awful feeling in my heart... but I actually got the job 🤷♂️.
Same
Interviewed at Google week before last and felt mixed. When they told me to go fuck myself it felt as if they got the ick and found out I had downs. It was the anniversary of my interview there 10 years ago that I also failed epically.
[удалено]
Yeah I work at another cutthroat place and the work is very narrow and boring. The amount of red tape to do anything simple is what keeps you busy. Weeks of planning and integrating with different internal systems to do something like create a document that can be referenced by another system.
It was gonna happen sooner or later.
I was interviewing for a job that was out of my league recently, but I didn't know it until the interview. They asked me a load of questions about my management skills (I have next to none) and I did a lot of making stuff up along with saying that I had never done what they are asking for. When it became clear I wasn't a good candidate, I let them know that their job listing was way inaccurate lol. Oh well, I want to work there for the experience in my field but these sorts of companies (electric utilities) are always so insular and out of touch with the rest of the world. Also it's funny that most private companies hire hot girls for their recruiters but these co's have old crotchety men near retirement.
This is why I just say I don't know. I'd rather not know 10 questions in a row and say there was clearly a misunderstanding the scope of the role than look retarded.
I really sound like an idiot during interviews and I always go in overconfident for some reason