Companies that use Gemini CLI

Source: Analysis of job postings that mention Gemini CLI (using the Bloomberry Jobs API)

My analysis shows that Gemini CLI purchasing decisions are being driven by engineering leadership and AI platform teams. Engineering Managers and Directors (9%) are responsible for tooling decisions, with strategic priorities centered on accelerating development velocity, building AI-native products, and transforming legacy development workflows. These leaders are hiring for teams that explicitly integrate AI coding tools into daily practice, not as experiments but as core infrastructure.

The primary users are individual contributor engineers, with Software Engineers (35%) and Senior Software Engineers (22%) representing over half of all mentions, followed by specialized AI Engineers (15%) and Data Engineers/Analysts (10%). These practitioners are using Gemini CLI alongside other agentic coding tools for full-stack development, API design, testing automation, and rapid prototyping. The job descriptions reveal that AI-assisted coding is becoming table stakes, with multiple postings stating requirements like "fluently use coding agents as a core part of their daily workflow" and "AI tooling to accelerate development is not optional, it's foundational."

The pain points are clear: companies need to move faster while maintaining quality. I noticed recurring phrases about "velocity," "rapid prototyping," "accelerate development," and "AI-native" approaches. One posting explicitly stated the goal of "speed-to-market is our most important KPI," while another emphasized "operating at the code level" with AI to "ship working features" quickly. These organizations are betting that AI-assisted development will compress timelines without sacrificing engineering rigor.

Source: Analysis of Linkedin bios of 602 companies that use Gemini CLI

I noticed that Gemini CLI users fall into three distinct camps. The first are developer tools and infrastructure companies building platforms for other developers: companies like E2B creating "machines for AI agents," Pydantic offering an "AI engineering stack," and Prisma making "working with databases easy." The second group consists of technology services firms and consultancies, from Vacuumlabs doing fintech engineering to StackHPC specializing in OpenStack deployments. The third are companies building blockchain and Web3 infrastructure, like Vocdoni's digital voting platform or Tatum's blockchain development tools.

These companies span the full lifecycle spectrum, though they lean heavily toward growth stage. I see plenty of early-stage startups (Twill at pre-seed with 5 employees, Knitli as a solo founder project), a substantial middle tier of Series A and B companies with 30-200 employees (PostHog, Endor Labs, Prisma), and a handful of massive enterprises like Thales with 64,000+ employees or NetApp at 12,000+. The sweet spot appears to be companies with 11-200 employees who have achieved product-market fit and are scaling.

Source: Analysis of tech stacks from 602 companies that use Gemini CLI

I noticed that Gemini CLI users are distinctly developer-focused companies that have built their entire workflow around automation, security, and AI-assisted development. The extreme correlation with CI/CD tools like CircleCI (4060x more likely) and GitHub Actions (1298x more likely), combined with automated dependency management through Dependabot (2022x more likely), tells me these are engineering-first organizations that prioritize developer productivity and code quality above almost everything else.

The pairing of AI coding agents (991x more likely) and Claude Code (678x more likely) alongside Gemini CLI is particularly revealing. These companies aren't just experimenting with AI tools, they're layering multiple AI assistants into their development process. They're clearly early adopters who believe AI will fundamentally change how software gets built, and they're willing to integrate several tools to find the right combination. The presence of GitHub Advanced Security (2385x more likely) alongside all this automation suggests they're mature enough to understand that moving fast requires robust security guardrails.

My analysis shows these are product-led companies, almost certainly in growth or scaling stages. They're not sales-led because their stack investment is entirely focused on internal developer efficiency rather than CRM or sales automation tools. The emphasis on CI/CD, automated testing, and security scanning suggests they're shipping code frequently, probably running some form of continuous deployment. These companies likely have strong engineering cultures where developers have significant autonomy to choose their tools.