Angular2 is a special case, in that a lot of the frustrations you're feeling are probably not far off from the frustrations that Angular1 developers are feeling

Angular2 is a special case, in that a lot of the frustrations you're feeling are probably not far off from the frustrations that Angular1 developers are feeling. The decisions they made going from Angular1 to Angular2 are a big reason I've never really bothered with Angular. Just on a base level, if a system isn't properly documented, that does make a case for finding someone with indepth knowledge. But a company using a system that is very poorly documented as their core technology is a big red flag for me.