MongoDB reported strong growth across both its Atlas cloud platform and its Enterprise Advanced self-managed offering. The company’s positioning around ‘run anywhere’ is resonating with enterprises that want to keep AI workloads closer to their own infrastructure rather than defaulting to public cloud for everything.
A manufacturing client in Stuttgart recently rewrote a data engineer specification three times before settling on what they actually needed: someone who could work across both cloud-native and on-premise MongoDB deployments, with enough architectural judgement to advise on which workloads belong where. That profile took longer to fill than a pure cloud role would have.
The split infrastructure model creates a specific kind of complexity. Companies running hybrid deployments need engineers who understand performance trade-offs, data residency requirements, and the operational overhead of managing database clusters in environments they control. These are different skills from spinning up managed services and trusting the vendor to handle the rest.
For candidates with MongoDB experience, the premium now goes to those who can articulate why a workload should stay on-premise versus migrate to Atlas. IT policy used to answer that for them. Now they need to weigh latency, compliance, cost, and AI inference requirements against each other and make a recommendation.
Hiring managers in our Data & Digital practice are asking for this architectural fluency more often. The ‘run anywhere’ pitch works for vendors because it matches how enterprises actually want to operate. Pure-cloud database specialists face more competition from candidates who can work both sides of that split.
Prompted by reporting from Diginomica.