4 ms·

Closures, specificity, home made getElementsBySelector, DOM traversal stuff, weird IE things, coding standards, an understanding of how jquery works, how to pro

Closures, specificity, home made getElementsBySelector, DOM traversal stuff, weird IE things, coding standards, an understanding of how jquery works, how to protect against npm poisoning/leftpad issues, lodash, semantic naming strategies, being opinionated (why is BEM shit/great?), box model, floats, flex box, centering techniques, an understanding of how plane old js works, cross origin/same origin stuff, basic design principles (spacing, fonts, information hierarchy, fitts law), react.

dwaltrip 10y ago
xhr, promises, a modern build tool (webpack? browserify?), prototypal inheritance, virtual dom, object oriented programming, when to add more abstractions and when to tear them down, front-end performance & memory profiling, browser dev tools, canvas, svg, service workers, browser caching, cookies, websockets, SASS, Ecmascript 6, API design principles, data modeling, when to use a hash and when to use an array, basic concepts of UX, and of course, most importantly, box shadows
- andy_ppp 10y ago
  All correct! Babel, Redux/data flow and immutable data structures. Basic software design principles. Anything else?
russelluresti 10y ago
A couple of years ago, I would have answered the same way. Now, at least in the SF Valley area, these types of things are largely ignored and instead we're asking a lot more CS questions (algorithms, data structures, design patterns, etc). In fact, I'd say about 99% of interviews for a front-end position don't ask ANY CSS questions at all - they're all JS-based. For example, in a recent string of interviewing here for a couple of large SF-based companies and startups, I've encountered questions like re-implementing jQuery, doing the JS for the game Snake, palindrome checkers, longest chain of ascending numbers in an array, shortest path, matching node (given a node in one tree, find the same node in an identical tree), and basically a whole bunch of other questions where only JS skill were assessed.
- andy_ppp 10y ago
  If people want to ask computer science question that's great but I'm not going to learn how to balance a binary tree (again) I'm going to get them to teach it to me in the interview by asking the right questions. If they can't see that I'm smart enough to pick new things up quickly I'll probably be trapped doing the same thing for them forever so I'd rather not work there :^)

dwaltrip 10y ago

xhr, promises, a modern build tool (webpack? browserify?), prototypal inheritance, virtual dom, object oriented programming, when to add more abstractions and when to tear them down, front-end performance & memory profiling, browser dev tools, canvas, svg, service workers, browser caching, cookies, websockets, SASS, Ecmascript 6, API design principles, data modeling, when to use a hash and when to use an array, basic concepts of UX, and of course, most importantly, box shadows

andy_ppp 10y ago
All correct! Babel, Redux/data flow and immutable data structures. Basic software design principles. Anything else?

russelluresti 10y ago

A couple of years ago, I would have answered the same way. Now, at least in the SF Valley area, these types of things are largely ignored and instead we're asking a lot more CS questions (algorithms, data structures, design patterns, etc). In fact, I'd say about 99% of interviews for a front-end position don't ask ANY CSS questions at all - they're all JS-based. For example, in a recent string of interviewing here for a couple of large SF-based companies and startups, I've encountered questions like re-implementing jQuery, doing the JS for the game Snake, palindrome checkers, longest chain of ascending numbers in an array, shortest path, matching node (given a node in one tree, find the same node in an identical tree), and basically a whole bunch of other questions where only JS skill were assessed.

andy_ppp 10y ago
If people want to ask computer science question that's great but I'm not going to learn how to balance a binary tree (again) I'm going to get them to teach it to me in the interview by asking the right questions. If they can't see that I'm smart enough to pick new things up quickly I'll probably be trapped doing the same thing for them forever so I'd rather not work there :^)