Build the stack mobile teams run themselves.
grovs is a small, senior team in Cluj-Napoca. We build deep links, analytics and engagement that run in our customers' own clouds, used by apps with millions of people.
Open roles
None listed right now.
We hire when the right person shows up. If you'd be good at one of the things below, write to us anyway.
Cluj-Napoca
Where we're based
MIT
Open-source core
10M+
End users of apps on grovs
Small
Senior team, no layers
What you'd work on.
One product, from the SDK in someone's app to the server in their cloud.
Mobile and web SDKs
iOS, Android and web SDKs that open links, record events and show messages. They run inside other companies' apps, so they have to be small and never crash.
Backend
Link resolution, event ingestion and message delivery, on Postgres, ClickHouse and Redis. Built to scale out across many instances.
Dashboard
The app marketing, product and data teams use every day: links, journeys, push, segments and revenue.
Self-hosted delivery
Docker images, Terraform, Helm and runbooks that let hospitals, banks and telcos run grovs in their own cloud.
How we work.
We sell to regulated companies, so we care about getting things right more than shipping fast for its own sake.
Small and senior
A few experienced people, each owning real parts of the product. No layers between you and the decision.
Close to customers
We talk directly with the engineers who run grovs at large companies, and build what they need.
In the open
The core is MIT-licensed on GitHub. A lot of what you write, anyone can read.
Shipped, then measured
We ship in small versioned releases and check what changed, the same way our customers do.
Who we'd like to hear from.
No fixed list of roles. These are the kinds of people who would fit.
Mobile engineers
Swift or Kotlin, and an interest in how an SDK behaves inside someone else's app.
Backend engineers
Systems that take a lot of traffic, and databases like Postgres and ClickHouse.
Infrastructure engineers
Containers, Kubernetes, Terraform, and making software easy for other teams to run.
Developer-facing roles
Docs, examples and support for the engineers who integrate grovs.
How it goes.
Short and direct. We reply within 2 business days. Not sure you fit? Write anyway.
- 1
Write to us
A few lines about you, what you've built, and links to your work or GitHub.
- 2
A first call
Around 30 minutes, with someone from the team, about your work and ours.
- 3
A look at real work
We talk through something you built, or a small piece of grovs together.
- 4
A decision
We tell you either way, and why.