None that I can think of.
Toxic and selfish upper-level management who only care about using you as a tool to hit their metrics and make themselves look good. It's a good ol' boys club here.
They could care less about you as a person or take any real interest in you or your development as long as work is getting done and they're hitting their numbers to line their own pockets. Meanwhile, the pay for engineers is way below market average.
Things are often heavily delayed and bogged down over-engineered processes and painfully laborious manual testing, but you will get blamed and thrown under the bus for why things aren't getting done. Middle management are also huge micromanagers while ironically claiming they hate to micromanage.
Priorities constantly shift like sand on a weekly basis, and you will never bring a project to full completion. This is due to them having a huge lack of knowledge about any modern technologies that aren't Nessus and a complete lack of cohesive vision from senior leadership.
Only a very select few good ol' boys get to come up with (terrible) product ideas - even though their skill sets are completely antiquated from working on a legacy scanner product for decades. Senior management then puts the pressure on to release it to act like something is getting done, and all the pressure is put on the engineers at the ground floor who had zero say in the "design" phase (or complete lack thereof).
This leads to half-baked product design ideas that get prematurely shipped to production and inevitably scrapped when the obvious shortcomings, redundant data, and poor infrastructure designs come to surface. Rinse and repeat.
In turn, this brings a ton of operational overhead and tech debt that is a complete waste of time dealing with. Imagine always troubleshooting someone else's mess who has way less domain knowledge than you, but getting constantly rejected by said people when trying to build it better.
Regardless of your expertise/knowledge in more modern technologies, you will never get to use it. As a result, most engineers inevitably get funneled into doing menial labor on their legacy Nessus scanner. It is written in their proprietary 20+ year old NASL language, which is an atrocious mess with zero documentation.
You won't be able to use this skill anywhere outside of Tenable, so your actual skill set in modern/relevant technologies will rust and they will squeeze whatever they can out of you. So much for all that "innovative career growth". eye roll
They had one decent product a generation ago and are riding the now relevant topical "cyber security" coattails of today's digital society to sell junk products. No one is actually doing anything meaningful or innovative here. It is a 20-year-old company operating like they're still a startup living in the past.
There is also a large presence of veteran 10+ year employees who have clearly only worked on one thing for way too long. They strong-arm everyone and don't let the recent hires with actual skills in newer technologies utilize their knowledge. I have talked to countless engineers who have joined in the last five years who all voice this concern.
If you don't align with them or blindly do things their way, you will be made an outcast and even have your job security threatened. It is a completely toxic and miserable environment. It feels like a really weird clique/cult.
These people are often condescending and tribal about their product knowledge, and they're the only ones that get promotions. If you're an outside new hire and not one of the good ol' boys from the glory days, there is absolutely zero career growth here.
Do yourself a favor and never work here. Take the recent bad reviews seriously; they are completely accurate. Everyone here is interviewing or working on an exit plan, myself included. Avoid this sweatshop at all costs.
Treat your employees with dignity and like human beings, not just battery packs to accomplish your own verticals within the company.
Recognize your own faults in your antiquated tech stacks and wasteful processes.
At this rate, you will undoubtedly continue to lose talent, make half-baked products, and fail miserably at keeping up with the current market.
Typical interview with two questions, one of which was quite difficult and unique. Then, I was given a home task, which I had the weekend to complete and was then reviewed on.
Had the recruiter reached out to me almost immediately after I applied to set up an initial call, I would have responded back. However, it took the recruiter about a week to eventually get back to me, stating he was away unexpectedly. I finally had
A coding task followed by two short, back-to-back interviews. Most of the questions were about my previous experience. There was no follow-up on this process. There were some questions about how to store and analyze a stream of events, as well as qu
Typical interview with two questions, one of which was quite difficult and unique. Then, I was given a home task, which I had the weekend to complete and was then reviewed on.
Had the recruiter reached out to me almost immediately after I applied to set up an initial call, I would have responded back. However, it took the recruiter about a week to eventually get back to me, stating he was away unexpectedly. I finally had
A coding task followed by two short, back-to-back interviews. Most of the questions were about my previous experience. There was no follow-up on this process. There were some questions about how to store and analyze a stream of events, as well as qu