Vantaggi
- Full-remote from here on out. - Health insurance premium is 100% paid for by ISF. - MSDN/Visual Studio subscription ($150/mo Azure credit, free product keys, etc.). - $5k/yr bonus for being AZ-204-certified. - I have never felt like I had to work more than 40 hours per week, even with critical + overdue items yet to be completed. - You get a 6-core, H-series CPU in your dev machine. - Hardly any meetings and hardly any spam emails coming into your inbox.
Svantaggi
- 401(k) vests 20% per year, but would be below-average even if it vested 100% immediately. It caps at something like $2,500/year. Like damn fellas. - Only health insurance option is PPO so you are not eligible to contribute to an HSA. In other words, the health insurance caters to older employees rather than younger employees who just want to save up for when they're older. - Leadership treats software development like an assembly line/sweatshop and seems to think we're all lazy/cheating the company out of our time. Ironically I believe this is costing the company a lot of money. Timekeeping for example is a huge time suck. - Nothing is being done to restore team cohesion lost by being remote for over a year. You can tell morale is not good but ISF would probably fire an entire team before allowing them a team-building activity on ISF's dime. - Timekeeping. Contractors and FTEs alike must account for 8 hours every day. Off-topic conversations are virtually nonexistent because everyone feels under the gun so much that they can't spare 15 mins to talk about *whatever*. - Leadership does not support the growth/development of their developers. Wanna learn about C# 9? Do it on your own time. Their stance seems to be "what if we train them up and they leave", but as that Dilbert cartoon goes: "what if we don't train them up and they stay?" I don't know whether it's the company's fault for refusing to invest in their talent, or the devs' fault for not leaving for another company after ~2 years. Either way, it hurts to see this. Obviously the thing to do is learn on company time anyway and not be vocal about it, but it's often impossible to do this since I am usually trying to keep a deadline (as is everyone). - Not Agile and probably not going to be Agile until there's leadership shuffling. - I feel like we create about as much technical debt as we fix. No one really reviews PRs so bugs/bad code gets through often. The problem is we're supposed to like... log that to a bucket for timekeeping, but there isn't a bucket for "code review" (in other words, leadership does not understand how software is written). All of these issues are beyond my team and my boss's control. It all falls on middle/upper management, none of whom are all that familiar with software development, if we're being honest.