- Development job that's mostly responding to customer issues in some way ("customer focused"). It can be a drag, but it's essential for the niche that Verimatrix's products operate in.
- Teams are small which can be difficult for junior developers if they have a clash with a senior developer.
- Internal documentation lacking for major parts of the codebase (and what little does exist uses in-house terminology that you need to review literature to demangle).
- I was intrigued by job posting due to mention of LLVM, but this was merely stated as background information. No part of the my responsibilities required any compiler-related background (much of the product doesn't use this either, and uses ad-hoc solutions, written by people no longer at the company)
- The agile development methodology quickly removes all desire for a well engineered solution, in favour of a band-aid that one can complete a JIRA ticket for the day.
- The team I was on seemed constantly at the mercy of one of app platforms that we did software protection for, this made my job security feel kind of uncertain at times (I eventually left the company for unrelated - personal - reasons).
That said, many of the cons are typical of most software engineering places and not exclusive to Verimatrix.
