|
|
|
|
|
by ckinsey
4439 days ago
|
|
The filter is not there yet, but it will be soon. We've got a proprietary algorithm in development that identifies the scope of both a candidates skills and the skills required by a position. Without divulging too much secret sauce, we'll be filtering out positions that do not meet our definition of "full stack" and we'll also be conveying to candidates just how "full stack" each position is with a rating system. |
|
Technically the "generic OSS based web" stack starts at debugging Linux kernel code (and sys admin coughDevOpscough), up through the OSI layer (with particular stops at the application(?)/HTTP-serving layer (and supporting code! aka: breaking out C to write a faster Rails router) and then again at the WebKit/Blink rendering engines, plus v8/JavascriptCore-whatever-Safari-names it, through CSS (Safari's CSS JIT work anyone?) through behaviors of said implementations. Plus add a stack of project management, requirements analysis, business analyst, and product design/UX.
To make this problem worse that's just one of many stacks. The native app development stack. The good boys and girls doing work with custom hardware (robotics, waldos etc) with realtime hardware requirements for example. A "generic MS based stack" which behaves similar in parts with very noticeable differences in places. Etc.
How-some-ever I suspect most, if not all of your employers will be looking for some sliver of the "full stack". Like the employer I mentioned earlier, whose definition of full stack is "Mostly Server-side Python but you should be OK at simple HTML/JS/CSS too". Or the new startups looking for people who can "write Javascript on the serverside too!"