Companies that use AI coding agents

Source: Analysis of job postings that mention AI coding agents (using the Bloomberry Jobs API)

I analyzed 70 job postings and found that 17% are leadership roles (Directors, VPs, Heads) responsible for buying decisions, while 83% are individual contributors who will actually use the tools. Backend Engineers dominate at 39%, followed by Product Managers at 7%, Vice Presidents of Engineering at 6%, and Machine Learning Engineers at 6%. The buyers sit in engineering leadership and product management, focused on accelerating delivery and scaling teams without proportional headcount growth.

The daily users are predominantly software engineers across the full stack, with strong representation from backend, ML/AI, site reliability, and infrastructure roles. These practitioners are expected to use AI coding agents as core productivity tools, not optional assistants. One posting explicitly states engineers should "fluently use coding agents (e.g., Cursor, Claude Code, Copilot, Gemini CLI) as a core part of their daily workflow" and another notes "the ability to leverage AI tooling to accelerate development, prototyping, and problem-solving is not optional, it's foundational."

The unifying pain point is velocity at scale. Companies want to "ship faster" and "move from prototype to production" without traditional engineering bottlenecks. I saw phrases like "AI agents are first-class contributors," "turn ideas into production-ready code in hours instead of weeks," and "maximize throughput and code quality." Organizations are explicitly building for an "AI-first" operating model where human engineers function as architects and reviewers while agents handle implementation, testing, and documentation.

Source: Analysis of Linkedin bios of 8,022 companies that use AI coding agents

I noticed that companies using AI coding agents fall into two distinct camps. The first is technology companies building developer tools, data platforms, or infrastructure products. These include companies like JetBrains, Databricks, DBeaver, and Directus who are creating tools that other developers use. The second camp is software development agencies and consultancies like DevSquad, datarockets, and Equal Experts who build custom solutions for clients. What unites them is that they're all in the business of writing code, whether as their product or their service.

These companies span the full maturity spectrum, but cluster in interesting ways. Many are well-funded growth-stage companies (Series A through Series J), suggesting AI coding agents appeal to companies with resources to invest in developer productivity. However, there's also a significant presence of bootstrapped, profitable companies like Doist and smaller teams under 50 people. The larger enterprises here, like Daimler Truck and UK Civil Service, are outliers, with most companies employing between 11-200 people.

Source: Analysis of tech stacks from 8,022 companies that use AI coding agents

I noticed that companies using AI coding agents are deeply technical, developer-first organizations that treat their engineering teams as core to their competitive advantage. The presence of multiple AI coding tools alongside Discord and Common Room suggests these are companies building for developers or technical audiences, where the product team itself is the primary user and often the target customer.

The pairing of Claude Code, Github Copilot, and Cursor together is particularly revealing. These companies aren't just experimenting with one AI coding tool. They're adopting multiple solutions simultaneously, which tells me their developers have autonomy to choose their own tools and the company prioritizes engineering velocity above standardization. The extremely high correlation with Reo.dev, despite its smaller absolute numbers, suggests these are early adopters willing to try emerging developer tools before they hit mainstream adoption.

Discord's presence is especially interesting because it signals a community-oriented approach. These companies likely run developer communities, participate in open source discussions, or use Discord for internal team collaboration in ways that mirror how their customers work. Common Room appearing in the stack confirms they're actively nurturing and measuring community engagement, treating community as a growth channel rather than just a support function.