4 ms·
> So I can't fault people for trying to avoid this mess. Ex-Amazon here. Being deeply familiar with OS fundamentals and internals, "low level" tools, and so on
by ex_amazon_sde 5y ago
> So I can't fault people for trying to avoid this mess.
Ex-Amazon here. Being deeply familiar with OS fundamentals and internals, "low level" tools, and so on is crucial.
A lot of candidates show to interviews with CVs filled with names of popular frameworks and fancy devops tools and often don't understand what really happens behind the curtain.
People are becoming less familiar with the basics and tend to reinvent the wheel. In many teams this does not get you hired.
- mtberatwork 5y agoI'm not saying you are wrong but this sounds like it is in part a hiring problem. > Being deeply familiar with OS fundamentals and internals, "low level" tools, and so on is crucial. ...needs to be front and center on the job description then. Far too often these kinds of things are hidden on the initial job descriptions and it just wastes everyone's time. I get that HR/recruiters want to throw a big net but vague job descriptions are often part of the problem.
- ex_amazon_sde 5y agoI cannot generalize for the whole company. When writing jobspecs in my team we never made lists of the "popular frameworks of the month".