Used to work there due to acquihire (throwaway acct since regular can out me).
Engineers were walked through how to interact with clients; don’t say this or that because of laws and treaties. But also to listen for customer language that suggests a customer is cheating Oracle; let Oracle know and they will send the lawyers.
Many many years ago I was working on making a phone OS (no not that one, this was for VoIP handsets, no not Cisco's) where we built an app suite on a Java VM. We wanted to use a Sun VM, I forget the acronym, that was bigger than J2ME but smaller than SE for which Sun, as far as we could tell, had no actual customers. You'd think they would be happy to have customer interest, but we got a total horseshit runaround on pricing. We could not base a product on something for which we had no idea of pricing. We used an open source Java which turned out to be adequate, but only just - no JIT, for example.
I only stayed long enough to migrate the service to Oracle infrastructure. Looks like they still offer it but when I left work was underway to roadmap decoupling what was then a OOP heavy Java monolith. I want to say primarily to move the UI/UX to Oracles internal standards and tech stack for such, but this was 2015; uuuuh I forget man.
My anecdote was based on interactions with sales, product, and senior engineering professionals. Internal culture seemed very forward thinking; work from home/anywhere Oracle had a business presence. Solid benefits, new parent leave, yoga/that kind of thing stipends. Though that may have been due to contractual obligation of the aquihire, and applied to my team only at that time. :shrug: The “problems” I saw were very much “first world problems”
And if they can’t say that (ie when it’s not true), they will intimate that you might be out of compliance, and hope you’re worried enough to just pay more anyway.
