41–50 of 300 posts
Earlier quoted context omitted.
I have been interviewed at Google and I was given a brainteaser. "Can you estimate Google AdWords revenue for Italy - B2B?"
Get population estimate for all countries with adword revenue, get adword revenue for each of these countries, fit to a linear model, predict italy. Or calculate adword revenue per capita and apply.
My issue is more with tricky algorithmic questions. I faced these tricky interview questions, where you either have to know the trick beforehand or there is NO way you can come up with a solution in an interview. I never understand the point of these questions. Because these esoteric hypothetical questions will almost never come up in real-life. They don't test someone's skills, because these problems don't follow an…
Earlier quoted context omitted.
This isn’t a brain teaser. It’s market size estimation, I’m guessing this was not an engineering role?
How is that question different from "please estimate how many golf ball fit in a school bus" ? The only thing changing are parameters. EDIT: it was for the Search team, search spam prevention, can't remember role it's been 4-5 years, sorry.
The single most effective interview question I ask: "What do you want to do?". I drill down on that to a granulator level as I try to make sure the tasks, duties and overall position matches what the candidate really wants for themselves. Its followed-up with a "How would you do it?", again persisting in the discussion (not interrogation) until we both are comfortable with the sensibility and symmetry of the answers.
Do you 'really' love your job? Would you do it for free?
How do I view the PDF with my javascript-disabled browser?
The single most effective interview question I ask: "What do you want to do?". I drill down on that to a granulator level as I try to make sure the tasks, duties and overall position matches what the candidate really wants for themselves. Its followed-up with a "How would you do it?", again persisting in the discussion (not interrogation) until we both are comfortable with the sensibility and symmetry of the answers.
If you think anyone 'really' wants to build your shitty CRUD app then you are deluding yourself. Do you 'really' love your job? Would you do it for free?
The single most effective interview question I ask: "What do you want to do?". I drill down on that to a granulator level as I try to make sure the tasks, duties and overall position matches what the candidate really wants for themselves. Its followed-up with a "How would you do it?", again persisting in the discussion (not interrogation) until we both are comfortable with the sensibility and symmetry of the answers.
I'm going to try this. The questions my team comes up with haven't been very satisfying and this seems like a good way to find out what they do know vs what they don't.
Literally said those words.
Eventually figured it out but I came away with a bad impression of the company. Not the kind of stuff I judge people on.