UI/UX Developer

Role: UI/UX Developer Reports to: Frontend / Product Engineering Focus: Product UI development, design-system work, and selected UX design About Midas Midas is an AI-assisted investment platform. The product covers portfolios, watchlists, market exploration, insights, alerts, onboarding, settings, and an agent chat. It is a modern TypeScript frontend with a shared component library and a Figma-driven visual language. The design system is still converging — inconsistent controls, spacing, and loading states remain — so this role both ships new UI and tightens the existing one. The role We need someone who can implement production UI and do enough UX design to unblock themselves. This is not a handoff-only implementer, and not a designer who never lands PRs. You will take Figma (or a loose brief) to a merged, pixel-tight, accessible screen — and when Figma is incomplete, you will propose the flow, states, and layout yourself. Work spans web and mobile. You should be comfortable designing and building responsive web UI and mobile-app experiences (native or mobile web), including touch targets, compact layouts, and platform-appropriate patterns. What you will work on Product surfaces: dashboard, portfolio, watchlists, markets, insights, chat, alerts, onboarding, and settingsShared UI primitives (buttons, cards, tables, metrics, empty/error/loading states) — new ones only when reuse is not possibleFigma → live gap work: spacing, typography, interaction states, empty/error/loading, mobile vs desktopLight UX: information architecture, interaction design, and state design when product/design is thinDesign-system convergence: semantic tokens, consistent radius and type, no one-off colors or one-off controls Responsibilities UI engineering (majority) Build and polish UI in Next.js (App Router) + React + TypeScript + TailwindDefault to Server Components; extract client components only for real interactivityReuse the shared component library and existing patterns before adding new onesNew shared primitives go in the design system with a Storybook storyUse semantic design tokens — no raw utility colors or hardcoded hexCover empty, loading, error, and gated/plan variants — not only the happy pathWrite unit tests and Storybook stories for new UI; follow existing end-to-end patterns when a flow is user-facingVerify in the browser and on mobile viewports before calling a ticket done UX design (part of the job) Translate Figma into implementable specs; flag conflicts with the design system instead of copying raw values blindlyDesign missing flows, edge states, and responsive / mobile behavior when Figma is a single frameProduce lightweight artifacts: annotated frames, flow notes, component inventory — enough for reviewPolish: alignment, spacing, contrast, focus, hover/press, and motion that matches the productAccessibility: keyboard, focus rings, contrast, labels on interactive controls, reduced-motion where we animate How you work with the team Small, reviewable PRs; conventional commits with ticket keysMatch existing architecture — you are not rewriting data layersLeave the design system cleaner than you found it; do not introduce a parallel look Must-have Strong production experience with React + TypeScript + Tailwind in a real product (not only marketing sites)Shipped UI on both web and mobile (responsive web plus mobile app or mobile-web product work)Comfortable in Next.js App Router (Server vs Client components, layouts, forms)Can implement from Figma with high visual fidelity and know when to follow the product design system instead of raw Figma valuesPortfolio that shows both shipped UI code and UX judgment (flows, states, responsive, empty/error)Component-library discipline: variants, tokens, composition, StorybookSolid CSS layout (flex/grid, responsive, overflow, stacking) — you debug spacing yourselfAccessible UI as a default, not a later passCan work independently in a git monorepo: branch, PR, address review, iterate from screenshots/gaps Strong plus Design-system migration or visual-debt cleanup in a large existing appFintech / markets / portfolio / data-dense dashboardsNative mobile (React Native, SwiftUI, or equivalent) or a strong mobile-web craftLight motion (CSS transitions, tasteful animation) without hurting performanceVitest + Storybook + PlaywrightFigma (Auto Layout, components, variants, Dev Mode)Dark + light theming via CSS variablesTurborepo / pnpm monoreposi18n-aware UI Not this role Backend / API / auth-platform work as the main jobPure visual design with no production PRsGreenfield “redesign the whole app” without shipping incrementallyBuilding a second component library next to the existing design system Stack you will live in Apps Next.js, React, TypeScript, App RouterStyle Tailwind, semantic CSS variables, light / dark themesUI Shared component library + Storybook; Figma as visual source of truthData Server Components, Server Actions for mutations, BFF routes for client readsQuality Vitest, Storybook, Playwright, ESLint design-system rulesDesign Figma; implement to the product system, not one-off values