Re:Technical and non-technical tips for rocking your coding ...
by IncRnd on Tuesday September 26, 2017 @06:16PM
(#15343041)
If it's a job to work on a haptic feedback system, they may very well want to plumb your understanding of when interrupts fire, without prompting for canned answers.
If you're interviewing for a front end position, you can make a nod to interrupts and continue on with BGP, ARP, DNS, TCP, IP, routers, etc. If you want to show your knowledge of security you could mention heartbleed, poodle, or even say why this isn't vulnerable to shellshock. An overview will take a minute, and the interviewer will follow up with more targeted questions if needed. It's a chance for the candidate to shine.
Re:Technical and non-technical tips for rocking your coding ...
by majormajor on Tuesday September 26, 2017 @06:36PM
(#15343205)
I think it's worth being aware that the more open-ended you make the question, the more you might freeze a less-practiced-at-interviewing candidate on not knowing where to start.
I'm always ready when asking something very open ended to follow up after 15 seconds or so to say "let's talk about [area X] first." For URLs, maybe this is "let's talk about what the actual network request, if you sniffed the traffic, looks like."
Re:Technical and non-technical tips for rocking your coding ...
by IncRnd on Tuesday September 26, 2017 @07:00PM
(#15343374)
That's perfectly reasonable. I interview candidates to let them shine not to fail them.
Re:Technical and non-technical tips for rocking your coding ...
by eradicatethots on Tuesday September 26, 2017 @09:18PM
(#15344138)
In the real world people like to tell you useful things that you’re genuinely interested to hear.
Re:Technical and non-technical tips for rocking your coding ...
by IncRnd on Wednesday September 27, 2017 @05:06AM
(#15346044)
> In the real world people like to tell you useful things that you’re genuinely interested to hear.
Exactly :)
Re:Technical and non-technical tips for rocking your coding ...
by rimliu on Wednesday September 27, 2017 @04:03AM
(#15345731)
You deal with BGP and ARP as often in frontend as you do with hardware interrupts.
Heartbleed and co. may or may not be your concern depending how much that frontend is into devops.
Re:Technical and non-technical tips for rocking your coding ...
by IncRnd on Wednesday September 27, 2017 @04:51AM
(#15345975)
Heartbleed should be understood by frontend devs. In 2017 there is a minimum set of knowledge that frontend devs really need to have. That includes pki, client and server certificates, routing, network caching, and a whole host of other topics. Layers of the stack interoperate, and lack of knowledge of the stack leads to security vulnerabilities.
Re:Technical and non-technical tips for rocking your coding ...
by rimliu on Wednesday September 27, 2017 @04:00AM
(#15345719)
Good first follow up question would be "I am typing this URL on the mechanical keyboard, bluetooth keyboard or touchscreen?" I think the whole time for the interview could be used to discuss what happens inside the keyboard without even reaching the OS :)
Many of these questions are very vaguely scoped which gives the confident and familiar plenty of room to show how clever they are, but also makes it more intimidating for those who haven't seen them before.
Or, to put it another way, the linked site looks like a great way to make yourself look like you have a junior-to-mid-level understanding of a lot of different areas. But the process it's optimizing for starts to break down the more senior a developer you either (a) are or (b) are trying to hire.