Ed Chen

Product designer for regulated financial systems — institutional infrastructure, compliance architecture, and trading platforms where every interface decision carries legal weight.

150+
Components
100K+
Traders Served
40+
Jurisdictions
5
Product Lines, One System
Regulatory Experience ASIC AU FCA UK MiFID II EU Dodd-Frank US

Selected
Projects

Institutional clients don't tolerate UI ambiguity. A misplaced margin call, a missing disclosure, an unclear risk statement — each can trigger regulatory audit. These projects exist in that environment.

Shipped Live client work — production deliverable
Concept Research concept — built on real production experience
01
ACY Securities — Enterprise FinTech Design System
Shipped · 4 Years · Live Product

ACY Securities

Enterprise Design System · 5 Live Platforms · Regulated Finance

Lead designer for five product lines at a 150-person regulated broker. 4 years, cross-functional with C-suite, Legal, and 3 engineering teams. The design system (150+ components, self-serve governance docs) lets teams ship autonomously. KYC drop-off: 73% → 45%. Eight regulatory updates absorbed without structural rework — a week instead of a month.

ASIC · FCA · MiFID II KYC 73% → 45% Drop-off 5.0★ App Store 3 Engineering Teams

Four years and counting: The design system has survived 8 regulatory updates, 3 engineering team changes, and expansion to 40+ countries. That durability is the ROI of governance-first architecture.

2024 — team restructured: After the design team downsized, I maintained delivery across all 5 product lines by integrating AI into the workflow — copy variants, asset resizing, code scaffolding. The system's self-serve documentation made this sustainable.

02
Christie's International Real Estate
Shipped · Live Client · 9 Months

Christie's Real Estate

Editorial Platform — I handled design, development, and product decisions

Design, development, and product ownership for Christie's International Real Estate editorial platform. Nine months. The audience: $5M–$80M property buyers across NYC, London, Tokyo, HK, and Taipei. The challenge: bringing a 250-year-old luxury brand online while keeping brokers central to every client interaction.

+20% Page Views 60% DB Query Reduction $5M–$80M UHNW Segment 5 Global Offices

Hired as a web engineer, ended up running the product. Design, front-end, back-end, coordinating across five offices in different time zones — full ownership over nine months.

03
ACY Connect — Institutional FIX API Documentation
Shipped · B2B Institutional · 12+ Prime Brokers

ACY Connect

Institutional FIX API Platform · Documentation System · B2B Infrastructure

Designed the documentation and onboarding system for ACY's institutional FIX 4.4 API — the protocol that connects prime brokers, liquidity providers, and institutional clients. Five different types of users (from product managers to market data engineers) all need to understand the same system differently. I designed that experience. This work later became the foundation for TradeX.

FIX 4.4 Protocol 12+ Institutional Clients 5-User Taxonomy B2B Prime Broker

Why this was hard: A misconfigured FIX message doesn't show an error on screen — it quietly creates a million-dollar position sizing mistake while the market keeps moving. The documentation had to be precise enough for developers and clear enough for business people — same system, completely different needs.

04
Finlogix — Real-time market analytics
Shipped · Live Platform · Statistical Validation

Finlogix

Real-Time Market Analytics · Modular Widget System · ASIC Regulated

Trading analytics platform handling 1,000+ real-time data points. I designed a modular widget system so traders could arrange their workspace the way they actually think. This project has my most rigorous research — controlled usability tests with real traders and statistically significant results.

Order Placement 8.2s → 2.9s 67% Custom Layout Adoption Session Duration +40% n=15 Paired Usability Study

The research behind it: Tested with 15 active traders in controlled sessions (paired within-subjects — each person tried both old and new). Order placement went from 8.2s to 2.9s (d=3.2). The large effect isn't surprising — we consolidated a 6-step flow into 2 steps. The more useful finding was identifying which steps caused the delay: confirmation modal and instrument search. That insight drove the redesign, not the aggregate number.

Research & Concept Work

Each concept extends production work into an adjacent problem space.

One System, Five Products,
40+ Regulated Markets

I designed the logged-in experience across ACY Securities — one design system that serves 5 product lines, 100K+ traders, and 40+ regulated markets. When regulations change, updates ship in days because the system was designed to handle change from the start.

ACY Securities Platform Ecosystem
Regulatory Foundation
Modular system where new regulatory requirements slot in — 2+ years of ASIC/FCA updates shipped without redesigning from scratch
Scope
Brand + Web + Platform
Business Impact
Enterprise-scale platform, 40+ countries, 5+ product lines unified
System Scalability
Design system enabled autonomous implementation across 5 product lines

Independent Evaluation

Top-Tier Platform Assessment

Independent broker review highlighting platform usability and clean interface design
— FXempire (2025)
Independent review examining ACY's multi-jurisdictional regulatory compliance framework
— FXempire (2026)

The System

150+ production components — built specifically for regulated financial products. Some handle trading data (prices, orders, charts), some handle compliance requirements (KYC, risk warnings, disclosures), and they all work across three different information density levels.

Production Components
150+
Finance-Native
9
Compliance-Native
10
Density × Theme
10
Price Display Real-time
EUR/USD
BID1.0847
2.2
ASK1.0869
▲ +0.0022 · +0.20%
Bid/ask spread · tick animation · deuteranopia-safe
Order Entry Core Flow
MarketLimitStop
Volume1.00 lot
Margin req.$2,174
FIX 4.4 OrdType mapping · margin validation
Watchlist Row Data Dense
EUR/USD▁▂▄▅▄▆▇▆ 1.0869+0.20%
GBP/USD▇▆▅▄▃▂▃▄ 1.2741−0.14%
XAU/USD▄▅▆▇▆▇▇▆ 2,318.40+0.83%
USD/JPY▃▄▄▃▅▄▃▂ 149.82 +0.03%
Bloomberg-caliber density · inline sparklines
◐ Light Mode
Trade Ticket Execution
● FILLED
InstrumentEUR/USD
DirectionBUY
Fill Price1.08694
Qty Filled1,000,000
Tag 39OrdStatus=2
FIX Tag 39 OrdStatus · execution confirmation UX
Sparkline Chart Trend
XAU/USD 2,318.40
Inline price trend · area fill · responsive SVG
Market Heatmap Overview
Sector Performance · 1D
Tech
+2.4%
Finance
+1.1%
Energy
+0.4%
Materials
0.0%
Health
−0.3%
Utilities
−2.1%
Sector performance · semantic color scale · at-a-glance

Designing Within
Regulated Constraints

ASIC says traders must see leverage exposure. FCA mandates best execution disclosure. MiFID II requires investment advice audit trails. I design these moments as the core product — not footnotes. Result: one architecture, 8+ regulatory rewrites survived, zero compliance feature scraps.

ASIC (Australia)

How do you tell users their funds are at risk without killing conversion? Leverage caps and disclosure rules forced honest hierarchy and clear copywriting.

FINRA / SEC Rules (US)

Designed suitability questionnaires to FINRA Rule 2111 and SEC disclosure standards: making required risk disclosures feel like user protection, not legal fine print.

ESMA (EU)

Inducement bans as a creativity constraint: designing engaging promotions when direct incentives are prohibited.

MiFID II Best Execution (EU)

How do you make trade execution transparency feel like a feature, not a disclosure obligation? Best execution rules forced a rethink of the order confirmation screen.

Dodd-Frank (US Derivatives)

US derivatives regulation that governs how trade data is reported and disclosed. Every confirmation I design serves two audiences: the trader who just executed, and the audit trail that regulators require.

WCAG 2.1 AA

Global accessibility standards for inclusive financial terminals.

Constraint as Brief — What It Produced

150+

Reusable Design Components

KYC flows, best execution confirmations, leverage warnings, consent gates — each built once, applied across ASIC, MiFID II, Dodd-Frank, and FCA simultaneously.

40–60%

Faster Execution on Regulatory Updates

When MiFID II Art.27 required trade execution venue disclosure (showing traders where and how their orders were filled), the update took 3 days — the pattern already existed. Compliance patches, not rebuilds.

8+

Regulatory Updates Without Rewrites

ASIC CP 322 · FCA SCA · MiFID II Art.27 · Dodd-Frank VII · ESMA leverage caps · FATCA · KYC re-consent · PDS update — zero system rewrites.

Regulatory Compliance Architecture How 150+ components enforce MiFID II · Dodd-Frank · ASIC · FCA · FINRA · WCAG 2.1 AA at the system level
COMPLIANCE STATUS BOARD
Last Audit: PASSED Violations: 0 --:--:--
JURISDICTION STATUS
KYC / AML PIPELINE
DISCLOSURE GATE STATUS
RISK & AUDIT METRICS
RECENT AUDIT TRAIL

Five Years of Work.
Here's What Actually Shipped.

One design system running across 40+ regulated markets. Products still live, still scaling, regulatory updates shipping in days. Every number below is sourced and verifiable.

Measurable Outcomes
8+ regulatory updates shipped without system rewrites — architecture built for compliance change
MiFID II · Dodd-Frank VII · ASIC RG 268 · FCA COBS — 40+ countries
  • System Scalability — One architecture serving 40+ countries and 5 product lines. Compliance logic lives in component variants, not page layouts.
  • Design System Governance — 150+ components with documentation that lets engineering ship without design bottlenecks.
  • Built for Regulatory Change — MiFID II, Dodd-Frank, ASIC/FCA requirements built as reusable components. Updates ship in days, not months.
Research Synthesis · ACY Order Flow Redesign Q3 2023
① Observe
170+ Hotjar session recordings
② Hypothesize
3 competing variants drafted
③ Test
15 traders · moderated sessions
④ Synthesize
Affinity map · 8 clusters
⑤ Measure
Production telemetry post-launch
Finding 01
Traders abandoned confirmation step when stop-loss field was not pre-filled — perceived as incomplete order.
→ Default SL/TP from last trade
Finding 02
85% of heatmap clicks on the "Sell" CTA were hesitation taps — users re-read the price 2–3× before committing.
→ Live price lock with 3s timer
Outcome
64%
faster order placement
8.2s → 2.9s · Validated via production telemetry
Role & Cross-Functional Impact
Small team, five product lines — built systems so quality scales without bottlenecks
150+ components · C-suite collaboration · Legal-First Checklist · 30-60-90 onboarding
  • Design Direction: Set standards across 5 product lines — interaction patterns, visual systems, and research practices that let engineering build without my input on every detail.
  • Cross-Functional: Worked directly with Legal on regulatory needs, Engineering on constraints, and leadership on strategic direction. Designed investor briefings and board decks for C-suite.
  • Legal vs. UX: When Legal required 47 disclosure fields (ASIC/FCA), data showed 73% drop-off. After 3-week C-suite mediation with prototype evidence, Legal approved conditional implementation with audit trail.
  • Executive Alignment: CEO pushed "Robinhood-style minimalism" for B2B terminal. Presented side-by-side usability data (task completion 40% slower). CEO approved information-dense design after session recordings.

Design Governance
at Institutional Scale

CEO briefs me on investor materials. CFO annotates directly in Figma. Legal reviews concepts before wireframes. Three regulatory jurisdictions, five product lines, retail to institutional B2B — zero feature scraps due to compliance issues.

C-Suite Design Partnership

CEO assigned investor-facing presentations directly — no PM layer. I worked with the CFO on cash flow projections and EBITDA overlays, introduced him to Figma for direct annotation, and compressed revision cycles from multi-day emails to same-day sign-off. The COO announced the Awwwards nomination company-wide and named me by name.

Team Process & Onboarding

4-step design review (Discovery → Concept → Spec → QA) aligned to engineering sprints. 30-60-90 day onboarding covering financial products, the design system, and compliance workflows. My direct report's words: "empowerment over micromanagement."

Cross-Functional Governance

Built a Legal-First Design Checklist after a 6-week feature got scrapped for regulatory issues. Now Legal reviews concepts before wireframes, copy before prototypes, implementation before handoff. Result: zero feature scraps due to legal issues across 2+ years. Lead engineer: "one of the smoothest cross-team collaborations" — because I join standups, understand component structure, and spec to how they actually build.

Third-Party Validation

What my colleagues actually said — 8 public LinkedIn recommendations from my manager, people I managed, engineers I worked with, and leadership I collaborated with.

Yung-Yu C. · Direct Report, ACY Securities

"Exceptional resource integration... empowers team members by providing opportunities to lead new projects, favoring empowerment over micromanagement."

Sheng Wen C. · Data Engineer, ACY Securities

"Exceptional taste, technical creativity, and an almost unsettling ability to ship beautiful work fast."

Cross-Functional PM, ACY Securities

"Reduces communication gaps between designers and product managers by deeply understanding user needs."

Architecture Before
Aesthetics

I reduce translation loss between design, legal, and engineering. Legal speaks in regulation numbers. Engineers speak in components. Traders speak in risk exposure. I speak all three — so each group stops making expensive assumptions about the others.

When I'm designing for institutional clients managing real capital, or for platforms where a single UI error could trigger a regulatory violation, the priority is clear: stability over novelty, trust over conversion tricks, and solutions tailored to each user's risk tolerance rather than one template for everyone.

The best teams I've worked with treat design and compliance as the same conversation — what does the user need, what does the business require, and how do we ship something that satisfies both without cutting corners?

Right Solution for the Right Client

A wealth management dashboard and a retail trading app serve completely different people. I've designed for both — and the difference isn't just visual. It's understanding how each group actually works, what risks they care about, and what rules apply to them.

Build for What Comes Next

I start with the hardest flow — the one with regulatory requirements, edge cases, and real money on the line. If you get that right first, the product won't need to be rebuilt when the next audit or regulation change comes along.

In the Room from Day One

I join engineering standups, understand component structure, and adjust specs to match how teams build. When Legal flagged copy-trading as "financial advice" under ASIC rules, I created a Legal-First Checklist so it never happens again. When the CFO needed chart reviews, I onboarded him into Figma for direct annotation. The pattern: I learn enough of each person's world to remove friction.

Systems That Scale with the Business

Every problem I solve becomes a reusable pattern. When a platform faces regulatory updates, a well-architected system absorbs them in days — not because you predicted each change, but because you built for adaptation from the start.

The team ships better. The business grows safely. The users trust the product enough to keep using it.

Beyond the Screen

Investor materials for C-suite. Cross-functional governance that survived 8 regulatory changes. Financial products running across 40+ markets. The work that never shows up in a Figma file.

Cross-Cultural Design Leadership

Designing Across Markets: SF · Tokyo · Taipei

Led design across APAC and Western markets — navigating ASIC, FCA, FINRA frameworks and cultural expectations around trust, risk disclosure, and information density.

40+
Countries Supported
5+
Regulatory Jurisdictions
3
Time Zones Coordinated

How I Work with AI
in Financial Product Design

I give AI the regulatory context it needs — ASIC, FCA, MiFID II requirements — and check everything it produces against what I know about the business and the users. Accessibility audits via Claude + Figma, colour-blindness simulations, every flow tested against real use cases. AI makes me faster; domain experience ensures it's correct.

AI Direction Session
Live collaboration model · ACY Securities fintech case
Ed + Claude
Ed · Domain Brief
Regulatory context Design constraints Business intent
Claude · Generation
Synthesizes patterns Generates options Structures output
Ed · Judgment Filter
Validates vs. reality Domain expertise Keeps · modifies · rejects
Collaboration Trace — ACY Securities · MiFID II + ASIC · Order Execution Confirmation Design
Ed's Brief
Post-execution confirmation · CFD Trading Platform · Open position active
MiFID II Art.27 Best execution disclosure at point of trade
vs
ASIC RG 268 Leverage risk warning — visual prominence
One screen. Both mandate "visual prominence" simultaneously.
Claude's Response
  1. A compact 'Best Execution Applied' badge in the confirmation card header, showing venue and execution spread inline.
  2. A full disclosure panel auto-expanded on load below the success state — surfacing execution policy details, venue data, and RTS 28 compliance status.
  3. A tabbed layout separating 'Confirmation' (trade details, price, quantity) from 'Execution Quality' (venue, spread, policy).
  4. Leverage risk warning positioned below the confirmation card body.
  5. A secondary 'View RTS 28 Report' link for annual execution quality documentation access.
✓ Kept ⟳ Modified ✗ Replaced Click any highlighted phrase to see the reasoning
Ed's Decision Log
✓ Kept Header execution badge Art.27 via compact indicator — not a disclosure block
✗ Replaced Auto-expanded panel Presence ≠ dominance — collapsed on-demand instead
✓ Kept Tab layout One pattern satisfies both regulators simultaneously
⟳ Modified Risk warning position Below fold ≠ prominent — anchored to viewport bottom
✓ Kept RTS 28 report link Audit doc, not point-of-trade disclosure — link, don't embed
Real collaboration model — Ed provides domain context and judgment, Claude generates, Ed filters against lived fintech experience. This portfolio was built exactly this way.

This portfolio was built with Claude. AI helps me work faster — but every design decision comes from five years of shipping real products in regulated markets, working with legal, engineering, and product teams every day.

"The best financial products feel obvious in hindsight — not because they're simple, but because someone understood the business well enough to solve problems before users ever noticed them."

In finance, the gap between "looks good in Figma" and "actually works in production" is measured in regulatory risk and user trust. I close that gap across functions — the CEO briefs me on investor materials, the CFO annotates charts in Figma, Legal reviews compliance components before engineering builds them.

The Team Ships Faster with Me in It

Lead engineer: "one of the smoothest cross-team collaborations." I join standups, spec to how engineers build, and jump in on edge cases. Component misuse: ~30% → under 8% after governance docs. CFO revision cycle: multi-day email rounds → same-day Figma sign-off.

I Understand What the Business Actually Needs

ASIC issued a 14-day compliance order — we responded in days because compliance logic lives in component variants, not page layouts. CEO briefed me directly for capital-raise materials. The institutional FIX 4.4 API portal cut support tickets 67% and integration time from 3 weeks to 1.

I Know What Different Users Actually Need

40+ countries, three time zones. Users from first-time traders to institutional desks managing $10M–$500M daily order flow. Each market has different expectations around trust, risk disclosure, and information density. Shipped for all of them — retail mobile (5.0★ App Store), institutional API portals, multilingual campaigns in EN, AR (RTL), VN, and JP.

What I Build, the Whole Team Uses

150+ components across web, iOS, Android, and institutional products. The key architecture decision: compliance logic — leverage warnings, disclosure thresholds, audit trail markers — lives as component variants, not page-level overrides. When ASIC changes a leverage cap or ESMA bans inducements, one component update propagates across all 5 platforms. Eight regulatory updates, zero structural redesigns.

Let's Talk

Senior Product Design — institutional equities, risk management, and trading infrastructure. I build interfaces for regulated environments where every field, disclosure, and interaction carries compliance weight.

Download Resume PDF

San Francisco · New York · Chicago · London · Sydney · Zürich · Tokyo · Taipei — open to relocation

Currently open to Senior Product Design roles — available now