4 ms·
The front-end interviews are a mix of front-end focused interviewers and gen-eng interviewers (usually 3 & 2, respectively). That's because the frontend-SWE po
by nostrademons 15y ago
The front-end interviews are a mix of front-end focused interviewers and gen-eng interviewers (usually 3 & 2, respectively). That's because the frontend-SWE position involves writing JS/HTML/CSS to run in a browser, but it also involves writing the server code that generates that JS/HTML/CSS (same reason that Java or C++ is part of the job req). We care very much about efficiency when your code runs on tens of thousands of servers.
There are also a bunch of algorithmic questions that come up in the browser as well, because unlike a lot of sites, Google actually cares about latency. You often can't use a library function if it involves pulling in a 300K library, nor can you write an O(n^2) algorithm if it involves locking up the browser.
- jumby 15y agoThen ask about browser caching, expires headers, js/css minimization, yslow (or page speed :/), CDNs, and generic front end stuff
- deleted 15y ago[deleted]
- nostrademons 15y agoA non-trivial percentage of visitors hit Google Search with an empty cache and no cookies. I know the numbers but aren't sure I can share them, but it's enough that relying on caching to solve latency woes doesn't work.
- nl 15y agoIn 2007 Yahoo shows that ~40-60% of users hit their pages with an empty cache[1]. Newer numbers would be good :) [1] http://www.yuiblog.com/blog/2007/01/04/performance-research-part-2/ http://www.yuiblog.com/blog/2007/01/04/performance-research-...
- jumby 15y agoThat's fine, but are you asking your frontend devs to solve Google's latency woes as a normal part of their interview?
- jojopotato 15y agoFrom my experience, they do ask those questions.