Good people, interesting products, certainly the strongest player in the vulnerability management space. Good work/life balance most of the time.
Tenable's biggest problem is that it doesn't know what it wants to be. There is no sense of what the culture is, and large swaths of the company get top-down reorganizations every few months. There is no coherent culture; there is no sense of "us." Every team exists in their own little bubble, does their own thing, and doesn't know how to talk to other teams in meaningful or effective ways.
There have also been large changes in product offerings over the past few years; they don't seem to know what kind of company they want to be.
A lot of good people have left post-IPO.
Too many people get too emotionally attached to what they work (or have worked) on.
Micromanagement, usually sitting on the heels of incomplete or incorrect information, is a huge problem at many levels in this company.
Management is also way too willing to determine deadlines before engineers can actually figure out how long something will take, leading to massive death marches to get things out the door. It happens less than it used to, though.
They've gotten hesitant about remote hires, and it seems counterproductive to artificially limit your hiring pool.
Post-IPO, they've started pinching pennies. Salaries lagging behind other largely remote companies and pretty unremarkable raises have been the result.
Figure out what you want the company to be and get rid of toxic managers.
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
HackerRank type interview. Take home. Plenty of time to thoroughly review test cases, etc. Some of the test cases on the coding exercises were hidden, so you had to be sure to cover all your corner cases.
Home test in Codility: 1. LeetCode style question 2. Frontend: React/Angular 3. Backend: Node.js HR phone call interview: * Asked about myself Interview with two company engineers
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
HackerRank type interview. Take home. Plenty of time to thoroughly review test cases, etc. Some of the test cases on the coding exercises were hidden, so you had to be sure to cover all your corner cases.
Home test in Codility: 1. LeetCode style question 2. Frontend: React/Angular 3. Backend: Node.js HR phone call interview: * Asked about myself Interview with two company engineers