Live data from Hacker News

Getting a job at Apple without going to college or doing LeetCode

aheze.substack.com

121–130 of 399 posts

Re: Getting a job at Apple without going to college or doing LeetCode

#122
post #114

Earlier quoted context omitted.

can confirm, it's as simple PG says "just build something people want" it will open many doors :)

Why would you want to become a wage slave if you've already built something that people want (thus can monetize it yourself)?

HN moment.

Software jobs, especially at the kinds of FAANG companies largely being discussed here, are quite a stretch for the term "wageslave."

Entrepreneurship isn't for everyone, even those who've tried it before.

Re: Getting a job at Apple without going to college or doing LeetCode

#123
Team dependent hiring is not “unique” to Apple, as the author posits. This used to be the norm before Google. It is fairly well known that Apple has a “hire different” approach that heavily values specific experience, which frustrates the Leetcode monkeys on Blind

Re: Getting a job at Apple without going to college or doing LeetCode

#127
post #32

Earlier quoted context omitted.

I think it makes sense to use LC or something like it. Is there a better way to judge the 100 random developers who've applied to your position? - They may not have formal education, you can't judge on that. - They may not have active GitHub projects, you can't judge on that. - They may not be active on social media or have any kind of fame, you can't judge on that. - They may not have built anything they can show of…

Especially for Senior Developers I think systems design questions are more interesting. They usually don't just have one right answer and you need to discuss the advantages and disadvantages of the different approaches. They require knowledgeable interviewers of course. Then again, I'm not working in a huge corp, so I don't know if this scales.

The issue with system design is that it doesn't always have a perfect answer and a lot of things are arbitrary about it. This leaves a lot of bias with the interviewers as to how to interpret the answer and question. This is less the case with Leetcode where there is usually only one or two optimal ways to solve a problem and you can just argue over time and space complexity as a means of what "optimal" is.

System design has a ton of bias in it and it's my least favorite type of interview because of it.

Re: Getting a job at Apple without going to college or doing LeetCode

#129

The problem is that "leetcode" is a definitely a thing that exists in "FAANG" interviews. The biggest stumbling block with leetcode is that you shouldn't be programming like that in real life. "make a linked list" no, just use a library like everyone else. "Implement addition in python but with string inputs", "no you can't use the built in x" All of that "clever" shit should be filtered out at PR/MR/diff review time…

Hiring should be a team level decision. Product roadmap should be an exec level decision. Google has it completely backwards. That's how you end up with hoards people gaming the hiring process by spending months on leetcode. And 3 chat apps from Google competing against each other.

Re: Getting a job at Apple without going to college or doing LeetCode

#130
post #114

Earlier quoted context omitted.

Why would you want to become a wage slave if you've already built something that people want (thus can monetize it yourself)?

HN moment. Software jobs, especially at the kinds of FAANG companies largely being discussed here, are quite a stretch for the term "wageslave." Entrepreneurship isn't for everyone, even those who've tried it before.

Golden handcuffs if you will :)
Post reply on HN