Live data from Hacker News

I interviewed at six top companies in Silicon Valley in six days

blog.usejournal.com

311–320 of 740 posts

Re: I interviewed at six top companies in Silicon Valley in six days

#311

When I was a new college grad, I felt trapped by the fact that everywhere I looked they wanted several years of experience, and I had none yet. How can I get experience if it's required to get the job? Now that I am 51, I feel annoyed that all of these stories of interviews involve asking questions about algorithms that rarely come up in real coding, and if they do you should NOT be rolling your own code, you should…

I share both of your concerns (while I was very lucky in getting initial experience, I know of other beginners that haven't/arent, so I'm very sympathetic.) . Started coding for work in '95.

> was I wrong then? Or am I wrong now? Perhaps both.

Neither, I think. The Algorithm interviews are bad for 90% of the positions out there, and experience matters much more than trivia, so you were right then.

And today, everyone is trying to hire "senior" (and above), so there's no concept of "will learn, lacks experience" - and the algorthm questions do badly at identify THAT, so you're right today too.

It turns out that interviewing is hard, and we don't know what works well. Most of us think "we" are the ones that can obviously see what's wrong and everyone else is interviewing poorly. Most of us are wrong.

But even besides that, we need to focus more on getting newer coders that DON'T have experience. We'll spend years looking for people that have experience...longer than it would take to grow that experience. We want seniors because we want people that will grow without being mentored, because we have far more work than people...but we skip one of the ways to reduce that workload.

I'd much rather have an interview that was teaching something new, and see how the person processed it. That's not a good interview either, but at least it is trying accomplish the correct goal.

And when we do interview for senior and above, experience will count a lot more than building a frickin' linked list.

Re: I interviewed at six top companies in Silicon Valley in six days

#312

When I was a new college grad, I felt trapped by the fact that everywhere I looked they wanted several years of experience, and I had none yet. How can I get experience if it's required to get the job? Now that I am 51, I feel annoyed that all of these stories of interviews involve asking questions about algorithms that rarely come up in real coding, and if they do you should NOT be rolling your own code, you should…

There are career stages. For candidates just out of school or with little experience asking algorithmic questions totally makes sense. For more senior candidates (who actually progressed to the next stage, not just spent a lot of years), the questions become more real-life, more open ended and with more than one (or sometimes none) “correct” answer

Re: I interviewed at six top companies in Silicon Valley in six days

#313
If I were giving a technical interview, after asking some basic fizzbuzz style questions, I would just ask a candidate to bring a personal laptop and "do something cool", i.e. show me what you're good at that is also valuable or useful. Could be spinning up a website, could be some cool parallelized data science or processing job, could be setting up a simple REST server infrastructure, as long as it's done de novo. Has anybody ever been an interviewer or candidate with this kind of interview?

Re: I interviewed at six top companies in Silicon Valley in six days

#314

"After about a month of consistently practicing problems each day (maybe 2–3 hours/day, more on weekends)..." I'm reading this as a guy with a wife, kids, full-time job, and rusty whiteboarding skills. My inability to make this kind of time investment makes me feel trapped at my current position.

I was able to land a couple of solid offers but you have to be really persistent. I kept chugging away a hour or so a day and 3+ on weekdays when kids slept in and basically made algos my thing apart from work and family (which worked out for me since I was able to come up with the Aho-corasick algorithm for a question I was asked). After a while I started enjoying the prep process since I was learning quite a bit too.

Re: I interviewed at six top companies in Silicon Valley in six days

#315
> Companies don’t hire people based on the knowledge they were born with.

Yes, this, so much.

> Don’t get discouraged. There were multiple interviews I had where I didn’t know the solution and interviewers had to shepherd me towards a solution. I still got offers from everywhere I interviewed.

And this, so much, particularly for those with imposter syndrome. You miss all the shots you don't take. If you're unhappy, and have done your best to find a way to happiness in your present role, start looking. Don't keep telling yourself "in another year I'll be ready" or "once I learn X and Y".

Re: I interviewed at six top companies in Silicon Valley in six days

#316

When I was a new college grad, I felt trapped by the fact that everywhere I looked they wanted several years of experience, and I had none yet. How can I get experience if it's required to get the job? Now that I am 51, I feel annoyed that all of these stories of interviews involve asking questions about algorithms that rarely come up in real coding, and if they do you should NOT be rolling your own code, you should…

Algorithm interviews are good for people that will be writing algorithms. Most of us are just plumbers, even so a solid knowledge about what algorithms are available and what their strengths and weaknesses are is as important as good knowledge about the tools is to plumbers.

Re: I interviewed at six top companies in Silicon Valley in six days

#317
post #254

Earlier quoted context omitted.

>Not once did we actually talk about my past experience or rather anything software engineering related. I had 5 rounds instead of 4 because I skipped phone screen, but I was pretty sure at least 3 of my interviewers didn't even look at my resume before the interviews haha. I also did a lot of interviews for Google when I was there, and I can totally see why that's the way it is, but at least I tried to see each inte…

I interview at Google and I never look at resumes - to avoid bias. I don't want to be biased by whether you went to Yale or UT Austin. My question is always a standard algo/DS question anyway.

I say the following having worked at multiple "big-5" including G.

Do you not feel any of the twist in your stomach that I feel when reading your post? That we're discarding any vestige of track record and accomplishment (that I pragmatically see as having correlated better than any other variable with effective coworkers in the past) for a readily gamable trivia question that I take some perverse pride in not having wasted time studying over the last decade? (Personally, I've spent my time doing far more actionable and applicable things such as running large distributed systems and learning how to do so more effectively while developing better patterns in that scope)

To be clear, this is not some defense of bias. This is a statement that your stated approach seems to throw the baby out with the bathwater. If I think to myself of what this interview process incentivises, it's not behavior that would lead me to be the engineer I am today, nor the behavior that I would chose in a coworker.

I'm just curious as to if there's any amount of dissonance inside G any more as to whether this is an effective way to get the people they want. Maybe it is, per their constant trumpeting of data driven hiring, and that's probably a great signal of why I didn't really feel at home there.

Re: I interviewed at six top companies in Silicon Valley in six days

#318
post #220

Earlier quoted context omitted.

Two different approaches. Each have their adherents. But when someone can’t find their phone or keys that that just had, they probably don’t start by ripping one room apart top to bottom.

I might pull the couch cushions, but I'm not going to start moving furniture until I check other places first.

so, basically A* search

Re: I interviewed at six top companies in Silicon Valley in six days

#319

When I was a new college grad, I felt trapped by the fact that everywhere I looked they wanted several years of experience, and I had none yet. How can I get experience if it's required to get the job? Now that I am 51, I feel annoyed that all of these stories of interviews involve asking questions about algorithms that rarely come up in real coding, and if they do you should NOT be rolling your own code, you should…

I share both of your concerns (while I was very lucky in getting initial experience, I know of other beginners that haven't/arent, so I'm very sympathetic.) . Started coding for work in '95. > was I wrong then? Or am I wrong now? Perhaps both. Neither, I think. The Algorithm interviews are bad for 90% of the positions out there, and experience matters much more than trivia, so you were right then. And today, everyone…

As I see it, the difficult algorithm interviews screen for people who are motivated enough to spend 100s of hours studying for an interview, or know this stuff for some other uncommon reason. Both types are acceptable hires.

Re: I interviewed at six top companies in Silicon Valley in six days

#320

When I was a new college grad, I felt trapped by the fact that everywhere I looked they wanted several years of experience, and I had none yet. How can I get experience if it's required to get the job? Now that I am 51, I feel annoyed that all of these stories of interviews involve asking questions about algorithms that rarely come up in real coding, and if they do you should NOT be rolling your own code, you should…

Is BFS really that hard, especially if the interviewer is willing to talk it out with you and doesn't care a lot about finding the most efficient solution possible?

I've been out of college more than 10 years now, do a mix of hardware and software (so am not coding all day everyday) and I can hack together algorithms like BFS if I spend a couple of minutes thinking about it.

I get that there are many awful interviewers out there and that hiring is pretty broken, but BFS seems like a pretty reasonable interview question, so long as the interviewer talks through what it actually needs to do and isn't only looking for a memorized answer. The question is well contained, doesn't require the candidate to know any specific API or framework, and can be implemented in pretty much any language. Probably the biggest downside to it is it's such a common question that many candidates study it ahead of time which makes it a worse filter.

Post reply on HN