Tali Neiman (she/her) [1991]
Product designer with 5+ years across SaaS, developer tools, and creative projects. At Front, I owned design for the Developer Platform — API flows, integrations, and AI-powered features. Before that, I've designed MVPs from scratch, redesigned university platforms, and built visual identities for cultural projects in Berlin.
Tali Neiman (she/her) [1991]
Product designer with 5+ years across SaaS, developer tools, and creative projects. At Front, I owned design for the Developer Platform — API flows, integrations, and AI-powered features. Before that, I've designed MVPs from scratch, redesigned university platforms, and built visual identities for cultural projects in Berlin.
I designed a new dashboard to help technical users better understand and manage their infrastructure usage, reaching 150+ companies, ~200 active users, and generating 500–1,000 weekly visits.
As the sole Product Designer on the Developer Platform squad, I led the feature end-to-end — from dashboard architecture and data modeling to introducing a new visualization pattern into the design system.
Exploring different visualization approaches to balance spike detection, rate-limit clarity, and upgrade context.
Customers were hitting API rate limits without any visibility into:
→ When limits were being reached
→ Why workflows were failing
→ Which integrations were responsible
This lack of transparency created frustration among technical teams and support escalations.
The final design was a stacked bar chart because it made volume and distribution easy to compare at a glance. I then formalized it as a reusable component in the design system to support similar use cases across the product.
The interface surfaces total volume alongside a clear distribution between successful, failed, and rate-limited calls, making anomalies instantly visible.
Within weeks of launch, the dashboard was generating 500–1,000 weekly visits across ~150 companies and ~200 technical users. For a developer-focused infrastructure feature, this level of engagement indicates strong adoption among the teams most impacted by rate limits.
I designed a new dashboard to help technical users better understand and manage their infrastructure usage, reaching 150+ companies, ~200 active users, and generating 500–1,000 weekly visits.
As the sole Product Designer on the Developer Platform squad, I led the feature end-to-end — from dashboard architecture and data modeling to introducing a new visualization pattern into the design system.
Customers were hitting API rate limits without any visibility into:
→ When limits were being reached
→ Why workflows were failing
→ Which integrations were responsible
This lack of transparency created frustration among technical teams and support escalations.
The final design was a stacked bar chart because it made volume and distribution easy to compare at a glance. I then formalized it as a reusable component in the design system to support similar use cases across the product.
Exploring different visualization approaches to balance spike detection, rate-limit clarity, and upgrade context.
The interface surfaces total volume alongside a clear distribution between successful, failed, and rate-limited calls, making anomalies instantly visible.
Within weeks of launch, the dashboard was generating 500–1,000 weekly visits across ~150 companies and ~200 technical users. For a developer-focused infrastructure feature, this level of engagement indicates strong adoption among the teams most impacted by rate limits.