The ‘Building in Public’ Shift: From Side Project to Professional Strategy
Rohit Ghumare doesn’t hide the scaffolding. As a Founding Developer Relations Engineer at iii and CNCF Marketing Committee Chair for 2025/26, he explicitly frames his current work as “building another open source project in public” — a deliberate choice to make the construction process visible rather than polishing only the finished result.
This transparency carries real costs. Ghumare’s GitHub Sponsors page itemizes his monthly community investment at $1,759: $800 on community events, $600 on AI tools, $240 on domains and infrastructure, $79 on website hosting, and $40 on content creation. Publishing that breakdown is itself an act of building in public — it converts financial exposure into credibility, showing the community exactly what sustaining this work requires.
That move reflects a broader professional shift happening across developer advocacy. The traditional model separated roles cleanly: you were either a practitioner who built things or an educator who explained them. Ghumare holds credentials on both sides simultaneously — Google Developer Expert for Google Cloud and AI/GenAI, Docker Captain, CNCF Ambassador, AWS Community Builder — and the point is that the distinction no longer holds. The audience learns because they watch the build happen, not after it’s complete.
For anyone outside the tech industry watching this pattern, here’s what it means practically: the most influential voices in open source are no longer people who achieved expertise and then began teaching. They are people whose teaching is the process of achieving expertise, conducted in front of an audience that participates, critiques, and contributes. The project becomes a community artifact before it’s ever finished.
That collapses the boundary between personal portfolio and professional output. When Ghumare builds in public, the GitHub commit history, the sponsorship page, the event spending — all of it becomes a living resume. No interview question about “real-world experience” applies, because the real world is already watching.
What It Actually Means to Hold Five Community Titles at Once
Rohit Ghumare holds five community titles simultaneously: Google Developer Expert for Google Cloud and AI/GenAI, Docker Captain, CNCF Ambassador, AWS Community Builder, and CNCF Marketing Committee Chair for 2025 and 2026. Most profiles treat this list as a credential stack — a longer-is-better trophy case. That reading misses the actual architecture of what Ghumare has built.
Each title belongs to a distinct vendor ecosystem. Google, Docker, CNCF, and AWS are not natural allies. They compete for developer mindshare, cloud spend, and platform loyalty. Holding recognized standing inside all four simultaneously creates something none of those programs individually confer: vendor-neutral credibility. A developer who trusts Docker’s Captain program and a developer who trusts Google’s Expert designation both have a reason to treat Ghumare as a legitimate voice. The portfolio functions as a trust bridge across ecosystems, not a collection of badges from a single sponsor.
The CNCF Marketing Committee Chair role sharpens this point. CNCF — the Cloud Native Computing Foundation — hosts projects like Kubernetes, Prometheus, and Envoy that run infrastructure for much of the internet. The Marketing Committee shapes how those projects are described, positioned, and communicated to practitioners and enterprises worldwide. Placing a community builder, rather than a vendor employee, in that chair is a structural statement about who gets to define cloud-native’s public narrative in 2025 and 2026.
Ghumare also self-reports spending $1,759 per month of his own money to sustain this work — $800 on community events alone, $600 on AI tools, $240 on domains and infrastructure. That figure matters because it reframes the titles. These are not passive recognitions granted for past contributions. They require active, ongoing investment to maintain. The community programs that award these titles expect continued output: talks, content, project contributions, event participation. Five programs running concurrently means five sets of expectations being met at the same time, funded largely out of pocket.
The combination — cross-vendor authority, a formal governance role at CNCF, and documented personal financial commitment — describes a career strategy that has no clean precedent in traditional software engineering tracks.
Developer Relations as a Discipline: Still Underestimated, Increasingly Critical
Startups rarely hire a “Founding Developer Relations Engineer” unless they view DevRel as load-bearing infrastructure. The company identified as “iii” made exactly that bet with Rohit Ghumare, signaling that developer trust is a product decision, not a post-launch marketing task. That title — founding, not just senior — puts DevRel in the room where architecture decisions happen.
The field still gets misread as glorified evangelism. Ghumare’s actual work contradicts that flatly. His focus spans cloud-native technologies, DevOps, and AI/MLOps — technical domains where adoption fails not because the software is bad, but because developers can’t operationalize it. The bridge he builds runs between engineering reality and community adoption. That’s a distinct discipline requiring both hands-on technical depth and the ability to translate complexity at scale.
The numbers behind his community work make the investment tangible. He spends $800 a month on community events, $600 on AI tools and applications, and $240 on domains and infrastructure — $1,759 in total monthly personal expenditure to sustain the ecosystem around his work. That’s not a marketing budget. That’s a practitioner funding the infrastructure of trust.
His credential stack — Google Developer Expert for Google Cloud and AI/GenAI, Docker Captain, CNCF Ambassador, AWS Community Builder, and CNCF Marketing Committee Chair for 2025 and 2026 — spans every major layer of the cloud-native stack. Each credential represents a community that validated his technical judgment, not his job title.
The AI dimension sharpens why this matters now. As code-generation tools lower the barrier to writing functional software, the scarcest resource shifts. Any developer can produce a working Kubernetes operator or MLOps pipeline with the right prompt. What they can’t generate is community trust, documentation written from real debugging experience, or the institutional knowledge of why a tool was designed the way it was. The human layer — education, credibility, community — becomes the actual competitive differentiator for open source projects competing for adoption. DevRel practitioners who understand both the technical substrate and the community dynamics sit at exactly that intersection.
The Missing Context: Why AI/MLOps + Cloud Native Is the Convergence Nobody Is Fully Explaining
The loudest conversation in tech right now circles around AI models — which foundation model is bigger, which benchmark it broke, which company just raised another billion dollars. Almost nobody is talking about what happens after the model exists: the infrastructure layer where Kubernetes clusters, Docker containers, and cloud platforms actually serve that model to millions of users without falling over.
Rohit Ghumare sits exactly at that intersection. His stated passions — cloud-native technologies, DevOps, and AI/MLOps — map directly onto a structural shift that the industry is mid-stride through but underreporting. The Kubernetes-era tooling that engineers spent the last decade mastering is being rewired to handle GPU scheduling, model serving pipelines, and vector database deployments. The skills are adjacent but not identical, and the operational complexity is significant.
Practitioners who genuinely straddle both domains are scarce. Ghumare holds recognition from three major cloud ecosystems simultaneously — Google Developer Expert for Google Cloud and AI/GenAI, Docker Captain, and AWS Community Builder — which signals fluency across vendor boundaries rather than deep allegiance to one platform. That cross-stack perspective matters because AI workloads in production rarely live inside a single vendor’s ecosystem.
Neither AI companies nor cloud vendors have filled the educational gap this convergence created. AI companies publish research papers and model cards. Cloud vendors publish documentation. Neither produces the ground-level operational content that tells a mid-career DevOps engineer how to adapt what they already know to run LLM inference at scale on the infrastructure they already manage. Ghumare’s educational output — content he describes as helping thousands of developers worldwide — targets exactly that practitioner audience.
The gap is real and measurable by its absence. Search for Kubernetes and MLOps together and the results thin out fast compared to either term alone. The developer who understands both the orchestration layer and the model deployment layer represents a profile that the industry needs but has not yet produced in volume. Ghumare is building in that white space, and the educational content he creates is filling a curriculum that no formal institution or major vendor has yet assembled in a coherent form.
GitHub Sponsors and the Economics of Open Source Advocacy
Rohit Ghumare’s GitHub Sponsors profile puts concrete numbers behind what community advocacy actually costs. His breakdown lists $240 monthly on domains and infrastructure, $600 on AI tools and applications, $79 on website hosting, $40 on content creation, and $800 on community events — a total of $1,759 every month that he asks the community to help fund directly.
That transparency is deliberate. By publishing the ledger, Ghumare frames sponsorship not as a tip jar but as a co-investment in shared infrastructure — educational content, open source projects, and events that benefit developers who never pay a cent. The model bypasses employer reimbursement structures entirely, placing the funding decision in the hands of individual developers and companies who consume the work.
This sits inside a much older and unresolved argument: who bears the cost of open source maintenance and advocacy? The GitHub Sponsors platform operationalizes one answer — the community pays — but the economics remain fragile. A $1,759 monthly target is modest against the cost of a full-time technical role in any major tech hub, and the gap between that figure and a market salary gets quietly filled by Ghumare’s corporate position at iii and his roster of recognized titles: CNCF Marketing Committee Chair, Google Developer Expert, Docker Captain, CNCF Ambassador, AWS Community Builder. Those affiliations provide legitimacy that attracts sponsors, but they also reveal the structural reality: the sponsorship model functions as a supplement, not a foundation.
That distinction matters for anyone watching developer advocacy as a career path. Building in public generates visibility, credibility, and community capital — assets that translate into job offers and conference invitations. But the developer advocates who can afford to produce free educational content at scale are, almost without exception, the ones already drawing a corporate salary. GitHub Sponsors signals intent and surfaces costs, but it does not yet close the gap between community contribution and financial independence. Until it does, the “build in public” model rewards those who need the income least.
What Ghumare’s Model Predicts About the Next Generation of Tech Careers
Ghumare’s career stack — Founding Developer Relations Engineer at iii, CNCF Marketing Committee Chair, Google Developer Expert, Docker Captain, CNCF Ambassador, AWS Community Builder — reads less like a résumé and more like a blueprint. Each credential represents a different trust network, and together they describe a compounding influence structure that no single job title can replicate. The framework underneath it is simple enough to be reproducible: learn a technology deeply, build something visible with it, then ship that knowledge outward to a community that can actually use it.
That sequence matters more now than it did five years ago. AI tools are collapsing the time it takes one developer to produce working code. The bottleneck is no longer writing the function — it is knowing which function matters, why it matters to a specific community, and how to explain that clearly enough that others adopt it. That is precisely the skill set multi-platform advocates develop by necessity. Ghumare personally invests $1,759 every month across infrastructure, AI tooling, community events, and content creation to sustain that work. The dollar figure signals something structural: this is not a side project, it is a career operating system with a budget.
Tech career coverage still defaults to the lone genius narrative — the engineer who ships the breakthrough, the founder who scales to a billion users. That framing misses where leverage is actually accumulating. The next generation of influential tech figures will not be defined by lines of code written in isolation. They will be defined by ecosystem fluency: how many communities trust their judgment, how quickly they can contextualize a new tool for a specific audience, how effectively they turn individual learning into collective momentum.
Ghumare’s model predicts that the developers who build durable careers in the AI era are the ones who treat community as infrastructure — something you invest in consistently, maintain publicly, and scale deliberately. The “build in public” approach is the mechanism. The trust network is the asset. And the career that results is harder to automate than anything a single engineer ships alone.
