Product foundations
Defining the product structure, interaction patterns, and visual direction as Code Inspector became Codiga, bringing the brand, website, and product into a more coherent system.
Designing a developer tool from the ground up.
As Codiga’s founding product designer, I shaped the product across web, IDE, and desktop experiences: turning static analysis, code quality, and reusable code into workflows developers could understand and use where they already worked.
Codiga workflowFrom editor to review
WRITEIDEReal-time analysis
→FIXCode qualityIssues & autofixes
→REVIEWPull requestAutomated checks
→LEARNDashboardQuality over time
THE PROBLEM
Code quality only works when it fits the way developers work.
Static analysis can expose a huge amount of technical information, but developers do not want another destination to monitor. The product had to surface the right signal at the right moment: while writing code, reviewing a pull request, or understanding quality across a project.
When I joined, the product was still evolving from Code Inspector into Codiga. The challenge was broader than a visual redesign: the brand, marketing site, web application, IDE extensions, and emerging developer workflows needed to feel like parts of the same product.
My role was to give that system a coherent product language across very different surfaces while the existing product was already serving more than 10,000 developers and 600 organizations.
Designing while the product and company were growing.
20K+users by September 2022
Codiga grew from more than 10,000 developers during the redesign to more than 20,000 users later that year.
600+organizations worldwide
$2.1Mseed round · February 2022
12+languages supported
2022acquired by Datadog
One product across every place developers write code.
Static analysis
Making code violations, security findings, severity, and suggested fixes readable enough to move quickly from detection to action.
IDE experiences
Bringing analysis and fixes into developer workflows across editors so feedback could happen while code was being written.
Automated code review
Designing how analysis appeared around pull requests and repositories, connecting individual findings with the broader quality of a codebase.
Code snippets
Exploring ways to create, discover, organize, and share reusable snippets from the product and directly from development environments.
Design system & implementation
Building a reusable interface language and working close to implementation so patterns stayed consistent across a fast-moving startup product.
user-service.tsStatic analysis · 2 findings
01import { logger } from './logger'0203export const getUser = (id: string) => {04 return api.users.find(id)05}
Unused importRemove logger
Quick fix availableDESIGN APPROACH
Keep the tool close to the code.
The interface had to translate analysis into something immediate: what happened, why it matters, and what the developer can do next. That meant reducing ceremony and keeping context attached to the code rather than asking users to interpret a separate reporting system.
As Codiga expanded beyond web-based code review, that same product language had to survive across VS Code, JetBrains products, repository workflows, and CI/CD. The interface could adapt to each environment without making each integration feel like a separate product.
Working in a small startup also meant design could not stop at polished screens. I worked close to the product and implementation, using reusable patterns to keep the experience coherent while we shipped quickly across surfaces.
01
Meet developers where they work.
Put useful feedback in the IDE, repository, and review flow instead of creating another place to check.
02
Turn findings into actions.
A violation is more useful when the interface explains it and makes the next step clear.
03
Build the system while building the product.
Reusable patterns let a small team move faster without letting every new surface become its own design language.
During my time there, Codiga expanded from web-based code review into a broader developer platform spanning static analysis, automated reviews, security analysis, custom rules, and code snippets across IDEs and CI/CD. The company raised a $2.1M seed round in 2022 and grew to more than 20,000 users before being acquired by Datadog. The static-analysis technology continued inside Datadog Code Analysis.