> What?! If you're specialising in Qt then your skills are tied to Qt and you are tied to the health of the Qt job market.
This isn't how it shakes out in practice, though. If you're "specializing in Qt", what you really become is a GUI systems engineer who in the course of their career will learn the fundamentals of many of the things this entails. You'll be the person that knows how the browser works and how to write it, not the person who is beholden to its crummy abstractions on top of better APIs. Case in point - the Chromium/Blink engine used by Electron was originally a Qt codebase (KHTML).
Most Qt engineers I know have a lot more fundamental, transferable knowledge than the web engineers I know.