Live data from Hacker News

Tech Interview Handbook

techinterviewhandbook.org

61–70 of 132 posts

Re: Tech Interview Handbook

#61

Earlier quoted context omitted.

If your question is specifically referring to the leetcode style coding interviews, this is exactly how Silicon Valley engineering careers work if you want to change jobs.

Which is such a strange optimization. As an industry we should boycott leetcode style questions.

You're welcome to, but don't expect to get jobs at any company folks have heard of.

I don't like it, but it's just the way it is now.

Re: Tech Interview Handbook

#62
post #49

Earlier quoted context omitted.

Github stars show the developer is either good at creating a project that serves a real need or at least decent at marketing their project, which in a startup role might be useful when you need somebody doing multiple things

I dunno how stars help with that. I use plenty of projects that I never star.

[deleted]

Re: Tech Interview Handbook

#63

Earlier quoted context omitted.

I wouldn't want to work with someone that doesn't have their fundamentals down. Most people spend at least 4 years studying CS, they should know their stuff.

I studied CS for 4 years and have used exactly none of it since leaving college. Our devs all help with hiring and agree as a 20-person team that academic "experience" means almost nothing unless you have no other job experience. How little academia prepares you for anything in real software engineering has become a cultural meme.

Did your CS degree cover algorithms and data structures? Did you learn Big O?

Re: Tech Interview Handbook

#64
post #58

Earlier quoted context omitted.

> Or they read a prep bible that told them this is how Google does things. Or they read an actual book about a subject (a bit better) but didn't really absorb the ideas (which is fine! happens to me too!), but wanted to use the thing they learned about anyway. In my experience and from what I have heard from other people, this is just how people generally are. It seems rare that people consider things rather than reg…

I mean, I have 10 years of experience in the field and when someone asks me that in an interview I still go like ‘duuuh?’. They’re like asking me to package up 10 years of experience into a 3 sentence package. How many ways are there to tell you that a caching mechanism is better for a site that barely ever changes than using database replication (yes, answering that question probably gave me some form of trauma). I…

It’s really about approximating the experience as a why to a decision. Usually I try to think through questions and talk out their benefits and things start to get more “obvious” to me as I go.

Admittedly, I don’t struggle near as much in system / software design questions, it’s my “niche” (tldr thinking in systems changed my life as a teen) but data structures and algorithms still kill me, in much the same way. I have the correct intuition but can’t for the life of me correctly describe it in Big O notation and I sometimes “freeze” on questions because it’s not something I do every day and I can just well…look things up sometimes, or work through a problem iteratively until I have a solution

Re: Tech Interview Handbook

#65
post #15

One thing that always blows me away (literally) is candidates that will eat like a tunafish sandwich with onions five minutes before they come in for an interview.

With that kind of confidence, I hire them on the spot!

If you’re going to melt my face when we are talking you should at least bring me a sandwich too. I’d hire that guy for sure. Hasn’t happened yet, but I’ll still hold out hope.

Re: Tech Interview Handbook

#66

I disagree with this resume advice actually. He for example removes that he was in the military sniper team and won best shot, but keeps high school education? I would totally say the opposite, keep the cool the side thing that's a conversation starter, but remove irrelevant educational experience. Including the number of stars on the github projects they worked on seems so.... narcissistic? Promotional? Idk but its…

[deleted]

Re: Tech Interview Handbook

#67
post #58

Earlier quoted context omitted.

> Or they read a prep bible that told them this is how Google does things. Or they read an actual book about a subject (a bit better) but didn't really absorb the ideas (which is fine! happens to me too!), but wanted to use the thing they learned about anyway. In my experience and from what I have heard from other people, this is just how people generally are. It seems rare that people consider things rather than reg…

I mean, I have 10 years of experience in the field and when someone asks me that in an interview I still go like ‘duuuh?’. They’re like asking me to package up 10 years of experience into a 3 sentence package. How many ways are there to tell you that a caching mechanism is better for a site that barely ever changes than using database replication (yes, answering that question probably gave me some form of trauma). I…

I'm not talking about interviews themselves, but the way people prepare for them.

> Do I really need to stop and unwind the steps my mind takes to arrive there

If the other person can't tell whether you're regurgitating it or you actually know what you're talking about then yeah probably.

Re: Tech Interview Handbook

#68

I disagree with this resume advice actually. He for example removes that he was in the military sniper team and won best shot, but keeps high school education? I would totally say the opposite, keep the cool the side thing that's a conversation starter, but remove irrelevant educational experience. Including the number of stars on the github projects they worked on seems so.... narcissistic? Promotional? Idk but its…

Github stars show the developer is either good at creating a project that serves a real need or at least decent at marketing their project, which in a startup role might be useful when you need somebody doing multiple things

Maybe it's just me, but contributed to X with no more information does not strike me as compelling. My initial assumption would be that they didn't do anything. It did not say created it, it did not say primary maintainer, or wrote X feature in Y.

Re: Tech Interview Handbook

#69

This is... incredibly disconnected from my 15-odd years of experience in my career. Is this how Silicon Valley engineering careers work?

This is really skewed to recent or new graduate and elite universities. When I was out of college, 15 years ago, some of the internships listed were hard or near impossible to get into. Take for example Goldman Sachs. They should be listing more regular internships and not those who managed to matriculate into the elite of the elite (hint: not a meritocracy). If anything it creates disillusionment that STEM careers a…

This is a pretty garbage take. Goldman Sachs is easier to get into as a software engineer than any FAANG. And every FAANG I know takes the majority of their new grad hires from public universities which, at least in California, are banned from affirmative action and legacy admits. Despite the UC administration's best efforts to remove merit from the equation by not counting standardized test scores admissions into a top UC is still merit-based.

Software engineering is not investment banking or law.

Re: Tech Interview Handbook

#70

Earlier quoted context omitted.

I studied CS for 4 years and have used exactly none of it since leaving college. Our devs all help with hiring and agree as a 20-person team that academic "experience" means almost nothing unless you have no other job experience. How little academia prepares you for anything in real software engineering has become a cultural meme.

Did your CS degree cover algorithms and data structures? Did you learn Big O?

Algorithms? yes, basic algorithms and sorting and Big O, none of which I've needed in 10 years of professional and hobby dev work. But to say "well you learned data structures and you use hashmaps and arrays so obviously it helped" is a very strange defense of academia. I can also learn "datastructures" online in a few days of studying as a new dev, so that's not really a good defense of 4 years of study.
Post reply on HN