Big companies assume software projects will be failures, and treat their employees accordingly. Then they get what they expect.
(Hire a bunch of good programmers with good management, and you can get amazingly reliable software from a team of two. Hire a bunch of bad programmers, though, and a team of 100 produces something worse than most kids' intro-to-java app. But nobody but the best programmers understand this, and it looks better to the business to pay 10 people each $60,000 a year instead of paying 2 people $200,000 a year. When a big company "gets this", their software becomes a lot better.)
The question is, tho', "at what"? Oracle's product offering is VAST. And most of it is technically quite simple; it just does an awful lot. You can't use clever Lisp macros to do stuff like this: http://c2.com/cgi/wiki?WhyIsPayrollHard You just have to chuck people at it.
From where I stand, the cost of poor quality software goes beyond the production. It's more in maintenance, licensing, lost opportunities, and poor adaptability to changing business needs.
I can't be a senior engineer because developers can't be engineers at all - and only engineers are allowed to supervise staff.
So Gosling's boss would be a 21 engineer-in-training.
Every large company is a software company, whether they know it or not. Failure to provide a career path for software engineering professionals on the technical side of the fence is a poor strategy, period.