All work
Simplifying API Security for Developers
Building 0-1: Repositories and AI Insights for API security testing at StackHawk.
Company
StackHawk
Role
Senior product designer
focus
0-1 Product design, developer experience, AI, product strategy, user research
year
2025

At StackHawk, I led the design of a new API Discovery experience that helped security teams understand which applications and APIs were being developed, what was being tested, and where security gaps remained.
The opportunity was significant. As companies developed APIs faster, security teams struggled to maintain visibility into their growing attack surface.
For StackHawk, solving this problem also represented an opportunity to increase product engagement, attract enterprise customers, and demonstrate greater value to existing customers.
Working closely with my product manager and engineering team, I owned the design exploration from early research through iterative releases, helping turn an ambiguous concept into a product that customers could use and the sales team could bring to market.
The challenge wasn't just simplifying complex security data. It was deciding what to build, when to build it, and how to deliver meaningful value under competing priorities.
Making complex information actionable
Security teams need to understand the applications and APIs their organizations are developing so they can identify vulnerabilities before those applications reach production.
But as development accelerated, maintaining that visibility became increasingly difficult.
Conversations with current and prospective customers revealed a growing disconnect between the pace of API development and the ability to test those APIs effectively.
We saw an opportunity to help security teams answer four fundamental questions:
Do we have a complete inventory of our APIs?
How much of that inventory is being tested?
Are we testing frequently enough?
Is our overall security posture improving?
Answering these questions would help customers understand their security coverage while making StackHawk's value more tangible.
Our design challenge: How might we turn complex application security data into clear, actionable insights that help teams prioritize what needs attention?
Turning ambiguity into a product direction
When I joined the initiative, leadership wanted to move quickly.
The team was exploring how AI could identify potentially testable applications by analyzing code repository information. Engineering was simultaneously working to improve the accuracy of that detection.
Meanwhile, leadership wanted something compelling enough to demonstrate to prospective customers at upcoming security conferences.
There wasn't a fully defined product experience to work from.
I partnered closely with my PM to translate these competing needs into an actionable design direction, working through high-fidelity concepts, customer feedback, and engineering constraints in parallel.
Rather than treating the experience as a single large release, we needed to determine which capabilities would deliver enough value to justify each milestone.

From API inventory to meaningful security coverage
Our earliest concepts focused on giving security teams visibility into their code repositories.
This addressed an important question: What applications and APIs might exist across the organization?
Initial feedback was positive. Customers appreciated having a clearer inventory and a simpler way to navigate their repositories.
But an inventory alone didn't tell users whether those applications were actually being tested.
Knowing what exists is useful. Knowing what's unprotected is actionable.
Working with my PM and stakeholders, we expanded the first milestone to include attack surface coverage, helping users understand the proportion of their repositories connected to StackHawk applications.
This introduced a more meaningful way to assess progress and identify gaps.
As I iterated on the interface, I focused on reducing unnecessary information while keeping the details users needed to take action.
The result was an experience that brought security coverage into focus and helped users identify repositories that still needed attention.
We released the initial experience to GitHub users in beta before expanding support to other repository providers.

Using research to guide the next iteration
Following the initial release, I conducted and synthesized feedback from 19 customer interviews across GitHub, Azure Repos, and Bitbucket users.
The research helped us understand both the value customers were finding and the friction that remained.
What was working
Customers appreciated the visibility into previously unknown repositories and APIs, the ability to identify testing gaps, and the opportunity to communicate security coverage to leadership.
What needed improvement
Users wanted clearer repository management, more filtering options, additional context, and a simpler way to connect repositories to applications.
These findings helped inform our next priorities while reinforcing the importance of making security coverage understandable at a glance.

Turning security data into a story leaders could act on
As API Discovery evolved, leadership introduced another challenge: helping customers understand the health of their application security programs over time.
Identifying repositories and testing coverage was only part of the story.
Security leaders also needed to know whether applications were being scanned frequently enough and whether their teams were making progress addressing vulnerabilities.
I began exploring how we could bring this information together in a more comprehensive Application Health experience.
Designing for different levels of understanding
I studied existing security dashboards and data visualization patterns to understand how technical teams interpreted complex metrics.
I also explored which information would be most useful for day-to-day monitoring versus communicating progress to leadership.
The experience needed to support two related goals:
For security teams: Quickly identify failed scans, untested applications, and vulnerabilities requiring attention.
For leadership: Understand security coverage, testing activity, and overall program health without navigating individual scan results.
This meant balancing detailed technical information with a high-level view that could be understood and shared.

Data viz exploration
Balancing user needs with business realities
This was one of the most challenging parts of the project.
Customer feedback pointed toward simpler visualizations, clearer information hierarchy, and stronger emphasis on actionable security issues.
At the same time, leadership had specific expectations for how the product should communicate value to prospective enterprise customers.
Those priorities didn't always align.
I explored multiple directions, tested concepts with users, and worked through the tradeoffs with my PM and engineering partners.
Some decisions were guided primarily by usability findings, including improving color distinctions, making important vulnerabilities easier to identify, and refining how scan activity was represented.
Others reflected business priorities, including emphasizing scan frequency and retaining certain visualization patterns that leadership considered important.
I learned that advocating for users doesn't always mean getting every preferred design decision into the first release.
My responsibility was to preserve the essential user experience while helping the team deliver a commercially viable product within our constraints.
That required understanding which tradeoffs users could reasonably navigate and which improvements could be prioritized for future iterations.

My propsed application health design
Results: Delivering value for users and the business
The work resulted in new API Discovery and Application Health experiences that helped customers better understand their application security coverage.
Users could identify repositories, understand which were under test, monitor scan activity, and review vulnerability findings across their applications.
The initiatives also contributed to StackHawk's broader commercial efforts.
~300 customers and prospects were using the feature within its first three months, as the team worked toward a goal of 1,000.
During this period, StackHawk also reported:
$2.2M in sales pipeline
137% improvement in Stage 1-to-2 sales progression
An $82K enterprise deal for which the sales team specifically credited the GitHub integration work as an important contributor.
These outcomes demonstrated the commercial relevance of the initiative, although they shouldn't be interpreted as revenue directly attributable to my design work.
51
Sales
$2.2M
In pipeline
+137%
Stage 1 to Stage 2

Final product experience
What I took away
This project changed how I think about designing within constraints.
At a fast-moving startup, the ideal user experience isn't always something you can deliver in a single release. Requirements evolve, technical capabilities change, and business priorities can influence which problems need to be solved first.
I learned to approach those tensions with more flexibility, working closely with product, engineering, and leadership to distinguish between what was essential now and what could evolve later.
Most importantly, I learned that strong product design isn't just about advocating for the best possible experience. It's about making thoughtful tradeoffs that move the product forward without losing sight of the people using it.