When I started at Synack, the company had gone over a year without a Product Designer onboard. No one working side by side with engineering, and when you looked at our platforms, you could tell.

Synack has three platforms:

  1. The customer-facing Client Portal where customers log in to launch tests and view their reporting and analytics.
  2. The SRT Portal (Synack Red Team) – this portal is where Synack’s ethical hackers log in to pick up tests and engage with the community.
  3. An operations platform called BOSS – this portal is the middle man between the Client Portal and the SRT Portal, operational team members log in to BOSS to launch tests for clients, validate SRT findings and manage many other things.

One of the first things I did was an audit across all three platforms to see when and where we were using shared components and assess if any design language existed.

I found that these three platforms didn’t share any components or styling and that the platforms themselves needed some major TLC.

I worked with engineering to see what changes might be possible and where we could align on specific components – we came up with a short term and long term plan, and I got busy building out our new Design System.


Our short term goals were to first work from our Client Portal, outlining our desired components, and then having developers work to make the necessary UI changes by coding the design system into our backend. From there, we then exposed the components to the other teams to utilize in their portals.