ShiftLeft

ROLE

Senior UI Engineer & Design Lead

Timeline

2017 — 2020

The technology was groundbreaking, a code graph that enabled proactive vulnerability scanning, but the interface buried its potential. Users faced an overwhelming wall of findings with no clear path forward. I redesigned the experience to surface what matters: clear priorities, actionable insights, and obvious next steps.

Key Contributions

Owned

UX

Design

Owned

Visual

Design

Collaborated on

UI

Implementation

Authored

80k+

LOC

Technologies

React
React
TypeScript
TypeScript
Redux
Redux
Immer
Immer
Node.js
Node.js
[01]

Dashboard

Challenge

Users were overwhelmed by a long list of vulnerabilities with mixed severities and no clear starting point.

Approach

Provide a high-level overview with severity counts and trends, and make each metric an actionable entry point.

Solution

  • Severity counts for critical, high, moderate, and info findings.
  • 'New' vs preexisting findings to highlight what changed since the last scans.
  • Type/category breakdown to understand distribution by vulnerability type.
  • Clickable counts that take users to filtered lists for focused action.

Outcome

Turned overwhelm into an at-a-glance overview with clear priorities and actionable entry points..

Analysis Summary
View
[02]

Vulnerability Triage

Challenge

The previous flow forced page-to-page navigation (list → details → back), and many vulnerabilities had similar names across types, making triage and communication difficult.

Approach

Adopt a master-detail layout to preserve context and speed up triage.

Solution

  • Master-detail UI: left-side list of vulnerabilities with right-side details that update on selection.
  • In-page side navigation to jump between sections within the details view.
  • Sidebar filters to narrow by severity and other criteria.
  • Assign a unique numeric identifier to each vulnerability to make referencing and communication unambiguous.

Outcome

Enabled fast, continuous triage without losing context and made communication unambiguous via unique IDs.

Security Findings
View
[03]

Self-Serve Onboarding

Challenge

Sign-ups previously required an account manager; we needed a self-serve path.

Approach

Provide GitHub authentication with a repo selector and an instant demo option.

Solution

  • Authenticate with GitHub; automatically list repositories for selection.
  • Choose a repository and start a scan immediately.
  • Or launch a demo project to explore the UI before scanning a real repo (no setup required).

Outcome

Users could authenticate, scan a GitHub project, or try a demo first, seeing value in minutes.

Onboarding Flow
View
Next Project

Mixtab