Open to Senior / Principal / Lead · US · DACH-EU · Sydney · Tokyo
Senior Product Designer · Design Lead tier · Institutional Finance
Interpreter · studio · Christie’s · regulated finance
Nearly five years shipping production design at an ASIC-regulated broker — 100K+ traders, 40+ jurisdictions, $2B+ daily volume. A 150-component design system that absorbed 8 regulatory rewrites with zero rebuilds and zero design-tied compliance findings in 2+ years. Reads the regulation before opening Figma. Ships production code, with AI in the loop and judgment kept human — the person a chief operating officer or a managing director brings a problem to before anyone knows what the solution should look like. I also own how the firm presents itself to capital markets and the board — investor briefs, listing-readiness, confidential corporate transactions — with the CEO, COO, CRO and Legal on the editing chain. Finance is where I apply the craft now, not the limit of it — the same system discipline carries into work well outside it.
Tab 01The essential read · where the file gets routed
A senior/principal product designer who treats compliance as a product surface — shipped at a regulated broker, not theorised in a deck — and an AI-fluent designer who ships production code. Route the file accordingly.
IC track at a trading platform, prime brokerage, or regulated fintech. At ACY: 8 regulatory rewrites aligned across 5 product lines and 40+ jurisdictions — owning stakeholder alignment across PM, engineering, legal and compliance without a manager translating.
6 designers led, 4 hired personally across nearly five years — through hiring, attrition, solo runs and rebuild, validated under 8 regulatory rewrites. Alongside that, five designers across four countries produce group material without reporting to me — standard-setting across a dotted line is most of what the senior job actually is. The scope has already been operated; the lead title is the part that has not caught up yet.
Token-first architecture, multi-platform export (CSS / JSON / Tailwind), regulatory absorption built in at the primitive level. Proven at 150 components across 5 platforms, with a working Storybook for engineering consumption — plus two public catalogues: institutional (251 categories around that 150-component system) and an independent 191-category consumer design system showing the same discipline anchored to platform guidelines instead of financial regulation.
The same contract for humans and agents. Public libraries: GalaxyJS, ReactΩ, and eds-mcp. Daily practice is Claude Code and Figma MCP; judgment stays human. Praxis Prime is a working TypeScript prototype (5,288 LOC), not a slide.
↳ still Tab 01 · shipped, labelled, sourced
Each case study has a named client, a regulatory anchor, and a measured outcome — working surfaces, not slides.
● Shipped · Flagship · ASIC AFSL 403863
2022 — present · APAC / EU / MENA · 100K+ traders · $2B+ daily volume
● Shipped · Solo full-stack · UHNW tier
2021 · 9 months · sole product owner, designer & developer · $5M–$80M audience
260-year auction-house brand voice translated to a digital editorial register; 8.2s → 1.4s mobile load; 50+ global editors retained with zero retraining.
● Shipped · Measured with named statistics
2022 · 8 jurisdictions · 40+ markets
Controlled within-subjects study (n=15, paired t(14)=8.92, p<0.001): time-to-insight 4.2s → 2.5s, Cohen's d = 2.47. Full methodology disclosure with seven named limits.
◇ Concept studies · production-grounded · original IP
2025 — 2026 · self-initiated · drawn from real production work, rebuilt as independent studies under fictional brands
The same token-driven system stress-tested across adjacent regimes — FINRA 2111, SEC Reg BI, FinCEN CDD, FATF Rec 10, SR 11-7, SEC 15c6-2 T+1, CSDR. Each ships a working artefact, not a mockup; Praxis Prime alone ships 5,288 LOC of React/TypeScript.
● Live · 0-to-1 · founder-built · Japan market
2025 — 2026 · designed, branded, built and shipped solo
The institutional record proves regulatory depth; these prove 0-to-1 range — a LINE-bot second-hand strategist with calibrated AI confidence, and a pet-services marketplace built from seven months of Tokyo field research.
↳ still Tab 01 · the mechanism, and what it compounds into
Same mechanism · different rulebook
The identical token-first method, pointed at a consumer regime instead of a financial one: an independent Consumer Design System — 191 categories across 17 domains, zero dark patterns by construction, every entry anchored to Apple HIG, Material 3, WCAG 2.2, App Store / Play policy, GDPR, COPPA or FTC rules, and served to AI agents over the same eds-mcp server as the institutional system. The catalogue is new in 2026, but its patterns already run in the founder’s own live consumer products — Duo-Shou and PawsRoam — and in pre-launch WizAgents, so the governance discipline is not fintech-locked.
The honest aggregate: on the order of $1M–$2M USD/year of compounded capacity returned, LTV captured and rebuild work avoided — a modelled aggregation of measured component metrics, not a single empirically-measured ROI number. The disclosure notes below name exactly what was measured and how.
Tab 02Track record & leadership · documented in artefacts, not adjectives
Every rewrite ran through one weekly sync — PM (priority), Engineering (feasibility), Compliance (interpretation), Legal (disclosure language), design absorbing all four into UI. 0 design-tied audit findings across 8 rewrites is the evidence the process worked.
150 components reached 5-product-line adoption because the handoff was designed: quarterly Figma library releases, token export as CSS/JSON/Tailwind, Storybook as source of truth, one change channel. Design ops as a deliverable, not an afterthought.
The system survived because design said no — to one-off compliance treatments, feature-specific styles, bespoke disclosure layouts. Every change propagated through tokens. That discipline only exists when design has the authority to refuse.
4 designers hired personally, each productive within a two-week ramp via the self-service enablement system (Storybook + token reference + regulatory routing playbook). Two have since moved to Australian SaaS companies and one left to found a company; the fourth joined in May 2026, completed the ramp, and is my current direct report on the CRM side — empirically validated, not retrospectively described.
Beyond product surfaces, I hold document ownership of company-level presentations — the materials an organisation uses to explain what it is to capital markets, counterparties, rooms full of clients, and its own board. That desk covers investor and fundraising briefs, listing-readiness (IPO / SPAC), confidential corporate-transaction materials, and the annual gathering. The form follows the room: a board pack is not a gala film, and neither is a product case study. I do not offer M&A, IR, or financial modelling as a service — the value is design judgement that can survive the people who actually sign.
The editing chain on those files runs through the CEO, COO, Chief Risk Officer and Chief Compliance & Legal Counsel; earlier work of the same kind was built alongside the CFO and PwC — revenue forecasts, EBITDA modelling, IPO/SPAC-readiness material. Named counterparties and live transactions stay off this page; the working relationship does not.
The design problem is not the one product work poses. Nothing here is optimised for conversion. A claim has to survive four executives whose incentives do not align — risk wants the caveat, legal wants the disclosure, operations wants the simplification, the chief executive wants the story — and it has to remain true, defensible and legible after all four have edited it. That is the same discipline as designing a regulated interface, applied to a sentence instead of a screen: the constraint is the specification, not an obstacle to it.
This is why the product decisions are anchored in unit economics, forecast and regulatory exposure — not as fluency claimed, but as the material I am accountable for. Design that reports into the risk and compliance chain is design with consequences, and it is where I do my most careful work.
↳ still Tab 02 · the 2026 operating model, disclosed not hidden
An "Ed Agent" plus nine specialist agents ingest and triage across scaffolding, documentation, and codebase recon — regulatory interpretation, naming the problem, and every sign-off stay human. Runs on-prem when the data is the company's; the open-source eds-mcp server cuts AI-token spend on UI build by ~85–90%. Full breakdown of what's delegated vs. kept human, the nine-agent roster, and the on-prem architecture is on the About page — full AI-authorship disclosure on Praxis Prime.
Tab 03Logistics & verification · the practical page
Australia note — ASIC-native, not ASIC-adjacent: nearly five years of production design from inside an ASIC-regulated AFSL holder. Building under ASIC RG 268, the Product Intervention Order leverage caps and Corporations Act disclosure obligations means near-zero regulatory ramp-up for an ASX / Macquarie / Pepperstone / CommBank / IRESS desk. The Australian retail-protection regime is lived experience, not a learning curve. Open to senior and principal roles across the Australian market.
↳ still Tab 03 · verification, check the file before forwarding it
Recruiters and AI search engines find this work without an introduction — and every quantitative claim carries either an externally citable source or a named internal instrument (GA4 · Jira · Hotjar · New Relic). Where a number can't survive scrutiny, it is labelled modelled or removed.
#1 on Google — above Figma's Nubank case study, Backbase and UXDA.
#1, above LinkedIn profiles — the exact query a recruiter types.
AI answer engines cite the ACY platform directly; in the Tokyo market the first page resolves almost entirely to this work. Live snapshots, June 2026 — a moment, not a permanent ranking claim.
Recommended 30-minute reading order for a hiring decision: post-launch first, methodology second, then accessibility, then political-skill. The four notes are the honesty register the rest of the portfolio leans on.
日本語For Japanese hiring teams
Ed Chen（エド・チェン）です。ASIC 規制下の証券会社 ACY Securities（AFSL 403863）で、10万人超のトレーダー・40 以上の法域・1日 20 億ドル超の取引基盤のトレーディング／KYC／コンプライアンス画面を設計してきました。150 コンポーネントのデザインシステムは、MiFID II・ASIC RG 268・FCA COBS・FINRA など 8 回の規制改定を作り直しなしで吸収し、UX 起因の重大なコンプライアンス指摘はゼロです。2026 年 1 月にシニアプロダクトデザイナーへ昇格しました。
プロダクト画面だけでなく、会社が資本市場・取引先・取締役会にどう見せるかの資料もドキュメントオーナーとして持っています。投資家・資金調達、上場準備（IPO / SPAC）、機密の会社取引、年次集会。編集チェーンは CEO・COO・CRO・法務コンプライアンス責任者です。M&A や IR をサービスとしては提供しません。部屋に合わせて形を変えるのが仕事で、デザイナーの美意識を押しつけることではありません。
現在の強みは AI ネイティブなデザインオペレーションです。自作のオーケストレーター「Ed Agent」と 9 体の専門エージェント（Claude Code・Codex・Antigravity・Figma MCP）で、要件の取り込みから分析・工数トリアージまでを高速化しつつ、設計判断とサインオフは人間が担保します。データ残留が要件のときはオンプレミス（DGX Spark / EXO）で完結。コードも自分で書く、AI に流暢なデザイナーです。
東京・日本市場で積極的に機会を探しています（リモート可・移住も検討、就労ビザのご相談も歓迎）。シニア／プリンシパル／デザインリード／デザインエンジニアのポジション、特に金融・トレーディング・規制対応・AI ネイティブなフィンテックのチームを希望します。業務言語は英語です。日本語は独学で毎日継続中（208日連続）ですが、現時点で業務に耐えるレベルではありません。書類・面談は英語でお願いしております。その代わり面談は JST の営業時間に合わせます。英語を業務言語とするチーム、または設計レビューを英語で回せる環境を想定しています。
想定する応募先は、証券・金融機関（野村證券・大和証券・三菱UFJ（MUFG）・SBI 証券・楽天証券・マネックス）、フィンテック（マネーフォワード・PayPay・メルカリ・楽天）、および東京の AI スタートアップです。機関投資家向け金融・規制対応 UX の実務経験を、東京の金融 DX・Web3・AI プロダクトに直接持ち込めます。ご連絡は ed@edwson.com へ（1 営業日以内に返信）。本ページ本文と各プロジェクトは英語です。日本語レベルは上記のとおりで、誇張はしていません。
In their wordsVerified, not written by me
Signed and public. Read this and ten other verified recommendations →
Close the fileOr open a conversation
If your team needs a designer who can walk into a compliance review, a product sprint, and an engineering standup in the same day — and add signal to each one — the fastest route is email.
Actively monitored · replies within one business day · interviews across US East afternoon / EU morning / JST business hours