Josh Knowles

Josh Knowles runs a company built on a simple, stubborn idea: engineering leaders deserve real evidence about how their teams build software, not gut feel and vanity charts. As CEO of Code Climate, he leads Velocity, a software engineering intelligence platform aimed at the technology leaders inside large, complex organizations, the kind of places where a single dashboard has to hold up under questions from a Fortune 100 VP of engineering.

It is a role he grew into rather than founded. Knowles joined Code Climate in 2022 as VP of Strategy and Operations, moved into a General Manager seat, and took the CEO title as the company made one of the harder decisions a two-product business can face. Code Climate spun its long-running code-quality tool out into a separate company, Qlty Software, and pointed everything that remained at software engineering intelligence. Knowles took the part that scales into the enterprise.

What makes his fit for that mission unusual is that he is not a career executive who wandered into developer tools. He is a working software developer who spent more than two decades in the field before the corner office, and he still talks like one.

A developer's climb

Knowles came up through the Ruby and Ruby on Rails community during the years when that world was small enough that everyone seemed to know everyone. His early resume reads like a tour of a certain slice of New York and startup engineering: senior developer roles at Lime Wire, at the Ruby on Rails consultancy Integrum Technologies, and at Next.it, plus engineering and software leadership stints at weplay and Gilt Groupe.

He was also a fixture of the community around that work. For years Knowles volunteered as an organizer for GORUCO, the Gotham Ruby Conference, New York's premier regional Ruby event, leading the organizing committee across multiple years and sitting on the program committee in 2008 and 2010. It is a small detail, but a telling one: long before he managed engineers, he was doing the unglamorous work of running the room they gathered in.

The Pivotal years

The chapter that most shaped Knowles as a leader was Pivotal. Starting around 2013 at Pivotal Software, he helped build and run Pivotal Labs, the consultancy famous for pair programming, test-driven development, and a near-religious commitment to agile practice. He served as VP for Pivotal Labs across EMEA and the East, work that included helping stand up the firm's European operations and manage client engagements with major enterprises across the continent.

Running a consulting practice teaches a specific discipline. You cannot hide behind a product roadmap; you are judged on whether real client teams ship better software after you leave. That perspective, of measuring effectiveness by outcomes rather than activity, sits close to the center of what Code Climate now sells.

When VMware acquired Pivotal, Knowles carried on inside the larger company, holding roles that included Senior Director of Application Services within Tanzu Labs and VP of Global Application Services. He had gone from writing Ruby in New York to running application-services teams at a global scale.

What Velocity is trying to do

Software engineering intelligence, or SEI, is one of those industry terms that can sound like a buzzword until you sit with the problem it names. Executives at large organizations spend enormous sums on engineering and often have almost no reliable way to answer basic questions: where is work getting stuck, which teams are thriving, whether a new process actually helped. Velocity, the platform Knowles leads, exists to turn the raw exhaust of software development, the commits, pull requests, and delivery data, into something leaders can reason about.

Knowles' framing consistently pushes against the crude version of that idea. The danger with engineering metrics is that they curdle into surveillance, a leaderboard of commit counts that measures motion instead of value. His pitch is the opposite: data that a real engineer would trust, used to coach individuals and improve teams rather than rank them. It is a harder product to build and a harder product to sell, which is arguably why a former practitioner is the right person to lead it.

From sprint boards to boardrooms

That instinct to apply engineering rigor everywhere shows up in his speaking too. At a San Francisco CTO Summit, Knowles gave a talk with the deliberately provocative title "eXtreme planning: Applying XP principles to annual operating plans," arguing that the same iterative, feedback-driven habits that make software teams effective can improve the corporate ritual of annual planning. At a later West Coast CTO Summit he spoke on "What your First Team needs from you," a leadership talk about the obligations an executive owes their peer group rather than their direct reports.

The quiet operator

There is no dramatic founder origin story here, and Knowles does not seem to want one. His path is the less-told kind: a long apprenticeship in how software actually gets made, followed by a steady climb from senior developer to VP to GM to CEO, each rung earned rather than granted. In an industry that lionizes the twenty-something who drops out to start a company, he is a reminder that operators who have done the work still reach the top job.

The small biographical details fit the pattern. He holds GitHub user ID 48, marking him as one of the platform's earliest members, from the era when the whole thing was a scrappy tool for a handful of Ruby developers. He keeps a personal site at joshknowles.com and posts on X as @joshknowles. And he runs a New York headquartered company from Austin, Texas, a distributed arrangement that would have seemed exotic when he started and is now simply how modern software companies operate.

The bet ahead

Code Climate's decision to spin off its quality product and concentrate on Velocity is, in effect, a bet on Knowles' worldview: that the biggest opportunity is not another linter or coverage report, but giving enterprise engineering leaders a trustworthy read on their own organizations. It is a crowded and skeptical market, full of executives who have seen metrics oversold before. Winning it will require exactly the credibility Knowles brings, the sense that the person selling you the dashboard has actually sat in the chair of the engineer whose work it measures.

For now, that is the work: taking two decades of hands-on experience in how teams build software and turning it into a platform that helps the largest organizations do it better. It is a mission perfectly matched to a career that has always been less about the spotlight and more about the craft.