Contributor Spotlight: Atharva Mhaske

Some contributors show up with production scars. Atharva Mhaske showed up with questions — the kind that don’t leave you alone until you go read the code.

He’s a pre-final year engineering student at Pune University, working primarily in Go, and a Google Summer of Code 2026 contributor at Open Science Labs.

The rabbit hole started with Go

“I picked Go as my main language about a year ago and just stuck with it,” Atharva says. “The more backend stuff I built, the more I kept running into the same wall: my services were fine, but the moment a database was involved, I had no real idea what was happening underneath.”

So he went looking. Build Your Own Database From Scratch in Go became regular evening reading, followed by engineering blogs from teams running databases at scale, and a lot of time in threads arguing about WAL designs and replication. Disaggregated databases and key-value storage systems became the specific itch — not because they’re trendy, but because they force you to think about storage and compute as two different problems.

How he found OpenEverest

Atharva applied for LFX Mentorship Term 1, 2026 at a different CNCF project and didn’t get in. Rather than wait for the next cycle, he went looking for projects where the work itself was interesting enough to contribute to regardless of whether a mentorship slot came with it. OpenEverest turned out to be a better fit than the original plan.

“What pulled me in was that it doesn’t treat database operations as separate problems for each database. It tries to build consistency across the whole space,” he says. “That matched everything I’d been reading about, except here I could actually go read the code and open a PR against it.”

From reading issues to giving talks

He started the way most people do: reading issues he didn’t fully understand, asking questions in Slack, slowly figuring out where the hard problems lived. Pull requests came next, then regular attendance at community meetings.

Earlier this year, Atharva spoke about OpenEverest at a CNCF Pune meetup, and last month he gave a talk diving into the OpenEverest v2 spec. “Walking through the specification details forced me to actually understand the architectural decisions, the reconciliation patterns, the failure modes.” A few weeks later, he was on booth duty at KubeCon + CloudNativeCon India 2026. “Reading a GitHub issue is one kind of understanding. Standing at a booth while a platform engineer asks a pointed question about reconciliation behavior, with no time to go look it up, is another kind entirely.”

In parallel, his GSoC project — building a Docker Swarm plugin in Go with HashiCorp Vault and OpenBao integrations — keeps rhyming with the work here: how do you manage state safely, how do you make infrastructure declarative, how do you make sure things recover correctly when they fail.

Welcome to the OpenEverest community, Atharva. Connect with him on GitHub, LinkedIn, or X.

To get involved with OpenEverest yourself: