The problem I was hired to solve
As AI coding tools moved from novelty to standard practice, Sonar faced a strategic question: where does a code quality and security platform fit in a world where developers increasingly write less code themselves? The team needed a clear point of view to inform both the CLI roadmap and the longer-term IDE strategy — and to communicate it credibly to customers and to the C-suite.
What I did
- CLI research plan: Designed and initiated a research programme combining internal surveys, qualitative interviews, and competitive analysis to understand how developers use CLI tools today, what makes them stay loyal to their existing tools, and what they'd expect from a Sonar CLI that integrated with an LLM of their choice.
- IDE vision and SDLC strategy: Contributed to the IDE vision brief and the Future of SDLC deck — a strategic document shared with C-suite that covered the shift from manual implementation toward orchestration, planning, review, and validation as AI takes on more direct coding work.
- IDE Labs participant recruitment: Proposed a non-intrusive in-product recruitment mechanism to engage connected-mode SQ-IDE users directly inside the IDE — building a standing feedback panel of high-value early adopters to reduce discovery lead time across squads.
- Next-generation IDE experience framing: Contributed to a Short Prime Review presented internally on how environments like Cursor are reshaping developer expectations — and what that means for where Sonar needs to show up and how it needs to behave.
- Sales enablement: Built a CLI-focused sales asset using Claude to help customer-facing teams answer product questions about the CLI clearly and consistently during customer conversations.
What I found
- Developer value is no longer located in isolated product moments. Developers increasingly expect quality, security, and agent support to be present where they already work: IDE, CLI, SCM, CI, PR flow, and increasingly, inside agent interfaces.
- The strategic implication wasn't simply "build a CLI" or "improve the IDE plugin." It was that Sonar needs to operate as an always-available quality layer inside AI-native workflows — including prompt-oriented and agent-orchestrated ones.
- Developer experience is on a trajectory from legacy environments toward augmented and more autonomous modes of development. Sonar's visibility and usefulness needs to hold across that entire spectrum — not just at one point on it.
- Connected-mode IDE users are disproportionately valuable as research partners. The recruitment mechanism we proposed was itself a product capability — a way to learn faster from the people most likely to push the product forward.
The decisions this enabled
- Gave the product and leadership teams a shared vocabulary for discussing AI adoption levels and what they mean for product strategy — across now, next, and later.
- Repositioned Sonar internally from a scanner or dashboard to infrastructure for AI-native development — a framing that held up in C-suite conversations and informed roadmap prioritisation.
- Grounded the CLI roadmap in real workflow questions: command language, discoverability, LLM integration expectations, and how to build ongoing feedback loops with early adopters.
- Created a sales enablement layer that reduced the gap between product reality and what customer-facing teams could confidently explain to prospects.