Actually, given those previous jobs it sounds like you really have never worked on a large project which was the "bread and butter" of a company. I mean a project which was sold stand-alone for cash, had a well defined shipping date and if it missed that date then the company (or at least dev team) was all likely to be out of a job.Programmer by profession for more than 10 years (yes that was after graduating from a 4 year college with a degree in Computer Science) with work experience on a vast many projects of various sizes including Military planning projects (used by joint ops strategic planning), scientific supercollider data analysis projects (silly little place called fermilab), web application design (mostly financial analysis systems & news distribution) ... but this isn't a resume. I honestly believe that I am qualified to have a professional opinion ... and that is that VI is slothful, ineffecient, and has poor implementation in the best of cases. I've seen dogs who put more planning and forethought into sitting down than VI puts into some patches.
Having worked for public service development jobs (ie military and government), utility jobs (where the project wasn't the core business of the company) and real world off-the-shelf applications I can see where you get the misapprehension that Verant is sloppy etc.
Fact is, when you make promises that can't be broken at the risk of your job then silly little things like testing and bugs tend to come second to more important things like food on the table for your family. No amount of experience in government or utility jobs can really prepare you for that reality.
Having said all of that, I think Verant does cut corners occasionally but on the whole is pretty much on par for bugs in the product with every other commercial software develpor out there.