<p>it seems like every interview i have, there's a surprise question that im not really sure how to answer, so I made some bs right on the spot and tell it to recruiters. Is this a good idea? I mean, its better than taking 2 minutes to think and say, "idk how to answer this question" right?</p>
<p>how often do interviewees get offers? I have no problem getting interviews but i cant seem to get pass the interview process, is this typical?</p>
<p>BSing is a must for any interviews. I have gotten almost all the interviews in IBD, S&T, asset management and strat consulting. Well guess what, one story doesnt work for everyone. So you craft a story for each one, why you are best, why your past experience lead you here, what you seek… then you tell each version of your story over and over again so it sounds genuine… practice makes perfect my friend</p>
<p>sounds good :)</p>
<p>same thing happens to me</p>
<p>:(</p>
<p>Depends. If it’s a technical question, don’t BS. If it’s a soft question, who cares?</p>
<p>you can BS technical questions. You just BS into area above your interviewer’s pay grade.</p>
<p>Just couple days ago, I was talking about how I used Monte Carlo simulation on the credit derivative structuring desk over the past summer and all of a sudden, the interview jumped in and asked me how to explain what Gaussian Copula is in the context of MC. Not knowing how to explain thoroughly, I decided to start BSing a little about gaussian copula (i knew about it somewhat) but then BSed my way into talking about the short comings of MC in option pricing in the sense that the greeks (especially the second derivative greeks like vomma, vanna, zomma, speed) you generate with MC simulation are unstable for options with discontinuity properties (ex barrier option). Then I proceed to talk about why PDE works better and then again, switch gear to derive the main PDE for Heston stochastic volatility model out of nowhere and told the interviewer why I thought it was interesting.
By the end of my string of BS, the interviewer had forgotten that he asked me about the guassian copula and we moved onto other stuff… (oh, and my derivation for heston was wrong to boot but again, I kinda knew the interviewer wouldnt know that anyway)</p>
<p>Result: Second round interview</p>
<p>Yea bull*<strong><em>ing is important. Just make sure you don’t get caught. It’s much better to admit you aren’t sure of something and take your best guess than do a poor job bull</em></strong><em>ing. And remember: never bull</em>*** a bull****er.</p>
<p>I suppose a little BSing on technical questions isn’t too bad, but to completely BS an interviewer on such a question and to get away with it would really make me doubt the quality of employees working at the company. I’d rather work with people who are better than I am, not with people who will believe some BS. Then again, I’m mostly talking about CS-related questions, which are harder to BS. I’m not sure what the OP’s field is.</p>
<p>im ME, so far all the questions asked are highly BS’able. I just need to find examples and practice thoroughly :)</p>
<p>Is it fine to talk about experiences not related to school/EC such as personal experiences?
For example,“Tell us a time when you had to make a choice but the decision will disappoint others”</p>
<p>I’d say BS the behavioral interviews (first interview) but not the technical interview. I tried this last year…</p>
<p>Result: No internships.</p>
<p>Know your ****, research the company, go through what you’re going to say in your head a few times.</p>
<p>
</p>
<p>Yes.</p>
<p>
</p>
<p>It’s definitely easier to BS behavioral questions.</p>