Bloomberg · Design Challenge
An intelligent alert system for traders — designed solo in 4 days
Quick Brief — for the hiring manager
Problem
Traders track thousands of securities and miss critical price events. Design a complete Alert system for the Bloomberg Terminal — field-value and field-field comparisons — from a blank screen in 4 days.
My Role
Solo interaction designer. Owned every phase end-to-end: scoping, competitive research, persona development, user flows, wireframes, alpha testing, and iteration to V2. Zero external support.
Impact
Production-quality interaction design for 5 complete alert screens delivered in 4 days. Alpha testing with real traders surfaced 4 key improvements incorporated into V2.
Approach
Scoped complete alert workflow into 5 screens. Competitive analysis across 10 trading platforms. Designed for 2 trader archetypes. Keyboard shortcut (Ctrl+Shift+A) integrated into Terminal conventions.
Outcomes
V2 incorporated real alpha feedback: "Dismiss All", alert cloning via shortcuts, watchlist-based alert creation. Full interactive prototype and interaction spec delivered within 4 days.
Learnings
Designing for an unfamiliar platform under pressure requires prioritizing conventions over creativity. Mathematical complexity in alert logic demands tight alignment with data teams before committing to interaction models.
Duration
4 days
Screens Designed
5 complete screens
Versions
V1 + Alpha-tested V2
Who
I am solving a design problem given by Bloomberg for Experienced Interaction Designer position.
What
Creating an Alert System for Bloomberg Terminal.
Why
To draw users' attention to securities when certain data events happen.
How
By allowing them to use arithmetical and logical parameters in multiple combinations for their Alert notifications.
The Challenge
Four days. A blank terminal screen. A brief requiring an alert system that handles nested logical operators for traders who live and die by price movements. The constraint wasn't just time — it was designing for a platform, audience, and interaction paradigm I had to fully absorb before I could create for it.
Bloomberg Terminal is a world unto itself — keyboard-first, information-dense, used by professionals who have spent years building muscle memory around its conventions. Any design that ignored this would fail before it shipped.
Two Alert Types
Field-Value: "Apple Last Price exceeds $600"
Field-Field: "S&P 500 Last Price falls below S&P 500 52-week Low"
Field-Field: "S&P 500 Last Price falls below S&P 500 52-week Low"
Design Process
Research & Insights
Day Traders vs Passive Traders
Two distinct user types with different alert behaviors. Day traders need instant, granular alerts. Passive traders need broader, less frequent signals. The UI had to serve both without complexity.
Keyboard-first is non-negotiable
Bloomberg Terminal users have years of keyboard muscle memory. Any alert creation requiring mouse-heavy interaction would be a dealbreaker. Ctrl+Shift+A became the primary entry point.
5 screens for the complete workflow
Alert Sources (create CTA), Setup Screen, Notifications Screen, Alert Display (popup), and Edit/Delete. Every path through the alert lifecycle had to be explicitly designed.
Key Design Decisions
01
Keyboard shortcuts as primary UX
Ctrl+Shift+A to create an alert anywhere. Duplicate alerts with a single keystroke. Dismiss All with one action. Every interaction was designed to match the muscle memory of experienced Terminal users — not fight it.
02
Grouping notifications by security
Alpha testing revealed users were frustrated by scattered notifications across securities. V2 introduced grouped notifications — all alerts for AAPL together, all alerts for IBM together — dramatically reducing cognitive overhead during high-volume sessions.
03
Clear All vs Dismiss All as distinct actions
A subtle but critical distinction surfaced in user testing. "Dismiss" removes from view; "Clear" deletes permanently. Traders needed both — temporarily clearing noise during a session without losing their alert history.
Outcomes & Impact
4 Days
Complete interaction design — scoped, researched, designed, tested, and iterated
5 Screens
Full alert lifecycle: Create → Setup → Notify → Display → Edit/Delete
V1 → V2
Iterated based on real alpha testing with Bloomberg Terminal users
10 Platforms
Competitive analysis: Robinhood, TradingView, Zerodha, E-Trade, and 6 others
Learnings
Constraints breed clarity. Four days forced ruthless prioritization — what must work perfectly vs what can be deferred. That discipline produced a cleaner design than an open-ended brief would have.
Platform fluency is a design skill. Understanding the conventions, mental models, and muscle memory of Bloomberg Terminal users was as important as any visual or interaction decision I made.
Mathematical complexity demands early alignment. The nested logical operators in alert conditions required a level of data model clarity that should have involved a data analyst from day one.