One thing to remember is an operating system is just another computer program.

Security is hard and there are no easy solutions. People often do not know they have been hacked or even know if a computer on their network has been hacked. Also, it is often not easy to determine if traffic is legitimate, illegal, malicious, or abusive.

1. According to Rapid Development or Code Complete (I can't remember which book said this), for most people, working more than 40 hours a week does not increase productivity in the long term. Basically, you can spend more time at work but you will not get more done. There are a few people who this is not true for but those people are rare and they usually are extremely driven because there is something about the project is really really interesting to them.

2. I strongly suspect most humans are just not built to work all of the time. It's not that there is something wrong with them, they just can't deliver more than about 40 hours a week of work. This isn't because they aren't committed, don't care, are lazy, etc. They just can't do it. I think this has to be accepted.

3. I have tried for decades to make the live at work lifestyle work and I have failed. I have repeatedly burnt out. It has taken me decades to realize that it is not a question of what you want to do, it is a question of what you can actually do and what is sustainable. Basically, you or your boss may want you to work 60 hours a week for months on end but that is probably impossible and it's better to accept reality than to keep on trying to do something which does not work.

Note that when I hear employers demanding crunch time, it tells me the leaders do not understand how people work because they don't understand that 99% of their employees probably cannot given them any more than they are already giving. This means crunch time does not improve productivity, but it does make everyone on the team more miserable because they are spending too much time at work and they are wondering why they can't seem to force themselves to get more done.

  I think you under estimate the value of anti-virus.  Anti virus software is a good second line of defense.  It’s not perfect but it will stop a lot of known malware.  This has value.

0. A strong desire to solve the user's problem and the organization's problem.

1. Knowledge of a major programming language like JavaScript, Java, Python, C/C++, C#, etc.

2. Knowledge of how to use an SQL database or maybe a no SQL database.

3. Knowledge of how to debug the build process and write scripts in Bash, PowerShell, etc.

4. Knowledge of at least 1 major framework.

5. Knowledge of Linux, MacOS, or Windows.

6. An ability to read documentation and learn.

7. An ability to debug large programs and fix bugs without introducing more bugs.

8. A desire to think critically and choose the appropriate technology for the problem (very hard, takes a lot of experience).

9. An ability to write clear code which others will understand.

10. The ability to write, argue, and persuade others.

11. A good person who works well with others, puts the product before himself, and is honest.

Almost all of these things are not taught to computer science majors. At best, a person will learn 1 to 2 languages and maybe Linux. Expecting computer science programs to produce good software engineers is crazy because software engineering and computer science are two different things.

The company will not tell us more until it has a product which is ready for the public.