i'm a developer. i have multiple games released on steam. i know what game development on a scale equal to, below, and above this entails. i also know what constitutes good game design, good UX, and what generally maximizes virality/sales/reception/etc.
hopefully that will make you actually listen to my feedback and take it seriously, but i consider that unlikely.
1. no mute button or volume controls or even any kind of options/settings for saving/exporting/etc. is unforgivable. and hitting escape and reaching an overlay that is clearly not integrated with the game (it's very clear that it's a disjointed feature and not integrated into the game's organic UI) doesn't count. that's actually worse in some ways than having no menu at all.
2. clicking ANYWHERE to switch to the simulation view is weird. misclicks will be VERY annoying. you already have the camera button in the upper left. that is enough. this is a particularly annoying UI choice on your part because when something pops up, the player's usual instinct is going to be to rapidly click off it to close it, and because of your weird UI choice, that action won't close it but rather open up the simulation/camera view.
3. i don't like the boss guy's dialog popping up every time i claim the reward for completing a quest. the quest card already contains the information about it. and the popup for the reward is also plenty. it's just spam and annoys the player. if you want, you could have the guy show up and say his dumb bit and have the quest reward text included in what he says so that there aren't two popup texts.
4. it does not make sense that automation of intern hiring is in the research tree. that is an HR task. i.e. the bottom tier HR worker should not promote interns. they should be hiring them. that is kind of obvious imo.
I made some further notes. If you implement these needed fixes/improvements, then I'll provide more feedback. My experience has been that when devs give solid feedback to devs, newer devs tend to have an arrogance that precludes acceptance of said feedback so I tend to wait to provide the meat of feedback until I've determined that's not the case.