2026-05-24
Source: HN Who is Hiring
Posted by: jrudolph
Of the ten postings, meshcloud's is the most revealing because its stack choices are unusually specific and its product thesis — multi-cloud governance for enterprises managing "thousands of AWS Accounts, Azure Subscriptions and GCP Projects" — sits at exactly the friction point that defines mid-2020 enterprise cloud adoption.
The stack tells a story. Kotlin + Spring + Angular + TypeScript is a classic JVM-enterprise pairing — boring in the best way, optimized for hiring senior engineers out of the German/EU enterprise talent pool rather than chasing trendy frameworks. But the outlier is RavenDB. Picking a niche .NET-origin document database over MongoDB or Postgres is a deliberate bet: RavenDB's strengths are ACID multi-document transactions and complex indexing — exactly what you need when you're modeling deeply nested IAM policies, account hierarchies, and audit trails across three cloud providers. The choice signals they're solving a data-modeling problem, not a scale problem.
What it reveals about the company. They're hiring three roles simultaneously — Fullstack, Frontend (with ngrx, implying complex client-side state), and Cloud Engineers spanning all three hyperscalers plus Kubernetes. That breadth says they're past prototype stage and building out a real platform team, but small enough that one posting covers everything. The product pitch — "DevOps Teams can enjoy private & public clouds without obstructions" — is selling to platform/security teams who are the obstruction. That's a sophisticated buyer.
Skills and trends highlighted:
Green flags: Onsite and remote offered (rare for a Frankfurt company at this date — the post lands just as COVID forces the issue). Honest, specific stack listing rather than buzzword soup. Clear customer profile ("largest enterprises in the world").
Red flags: No mention of funding stage, team size, or comp. "Thousands of accounts" customers usually means long enterprise sales cycles — engineers should expect slow feedback loops from real users. RavenDB expertise is genuinely scarce, so onboarding will be steep, and you're betting on a vendor whose community is a fraction of Postgres or Mongo.
