40 karma · joined November 2, 2015
FB: I currently work here. LC style questions but with a frontend twist. Best believe if you don’t have a strong handle on algorithms, data structures and Javascript, you won’t stand a chance.
Google: Phone screen is leetcode, during onsite they ask two leetcode questions & 1 frontend focused one.
Apple: Phone screen is Leetcode, onsite is a combination of leetcode & frontend.
I actually find frontend interviewers to be harder because you have to have a strong handle on frontend technology + data structures and algorithms, as opposed to non-frontend roles where just doing leetcode is all you need.
Also, there is the very wrong notion among people ignorant about the frontend engineering world like yourself that assume all it entails is simply knowing how to use React & CSS. It is more complex than that, you’d have to know about the DOM tree, know how to manipulate it, think about accessibility & performance. It can become complex very fast. Most of these interviews create Leetcode style questions from DOM tree manipulation & they are harder to reason about.
while in college - myrumate.com [2011] I built a basic web app to help students find roomates, especially students coming from long distances.
- thestudybox.com [2012] (I still keep this domain don't know why) question and answer site for students, a cheap stackoverflow clone.
- Snatchh.com [2013] A classifieds sites for students to buy and sell stuff.ly
They all failed but I learnt a lot about building stuff from scratch to completion alone. Code was most procedural PHP(spaghetti) and I experienced first hand the problem with a large smelly code base.
I still build stuff, but it's mostly small personal stuff.
Find the code here: http://github.com/nkudo
2. Invested a lot of my time in learning more(Data structures/algorithms, advanced JavaScript) which gave me the courage to quit my soul sucking job and helped me land a much b€tt€r one.
I'm still very young so I'm actively saving up my "F-u" money.
PS: The startup's not American, American startups have an inflated ego.
2. Over-tooling and complex architectures, look at NPM and Flux(react)
3. Inbuilt dependency management by browser, Grunt/Gulp/Bower/Webpack/ the compression and minification done by these should be handled by browsers so that we no longer have need for them. Just one standard configuration to be used by everyone.