I think that’s great effort, really! But you seem very focused only in one kind of workplace... which looks quite like deep into the programming/algorithm part

I think that’s great effort, really! But you seem very focused only in one kind of workplace... which looks quite like deep into the programming/algorithm part of CS... If you would like to compare to software engineers as we know then in Europe you would need to have also some knowledge of physics (a general overview), mathematics (including statistics, discrete mathematics, algebra, ...) basics of economy (it is very common to have at least a subject or two) and then a fast overview of some domain specific technical areas such as databases (formal SQL92), artificial intelligence (an overview on the common algorithms and story of AI), operating systems (I remember to have read the code from a small Unix, also made a kernel module), the architecture of a computer (von Neumann) and understand the basics of Hardware programming (including some assembly and an overview how the CPU registers work, and so on...) and compilers. Also do not forget things like classic software engineering, specification modelling and definition of problems in formal languages. And then comes the actual specialisation (web programming, deeper in databases, graphics programming, ...). I have the feeling I forgot half subject of every area I mentioned... but as you see an software engineer knows a bit of every area, not to deep in the ones he/she did not specialise, and a bit of the surrounding careers; and very often after complete the basic degree is common to specialise deeper in some of those areas or go deeper in them as part of your professional life. P.S. and for sure the final project of the career... which not many students take it serious but it could be compared to some side projects/per projects which you see from time to time in HN.