You pay attention to how people actually work. You sketch to think, prototype to learn, and ship so you can watch what happens next. You pick the right tool for the moment—horses for courses: a paper sketch for a messy idea, a Figma flow for team debate, a clickable prototype for usability tests.
You read WIRED and the odd design book, notice patterns in the products people really use, and you’re just as happy naming a button as shaping an end‑to‑end flow.
Bonus points if you love machines (you’ve toured a factory, tinkered with hardware) or you’ve placed a trade and felt the heartbeat between click and confirm.
You’ll take features from discovery → prototype → spec & handoff → QA in UAT → post‑launch iteration.
Mission: Design calm, useful interfaces—then close the loop after they go live.
What you’ll do
- Partner with PM/eng to clarify problems; turn ideas into flows, wireframes, and prototypes in Figma.
- Evolve a design system (tokens, components, states) with accessibility built‑in; keep naming and docs tidy.
- Design core app surfaces (My Suitcase, Markets Dashboard, Research Repository) and marketing pages/landing experiments.
- Run lightweight usability tests (scripts, recruits, notes) and share crisp findings.
- Write clear UX copy; pair with eng on specs, edge cases, empty/error/skeleton states.
- After release, review analytics and feedback, propose improvements, and ship follow‑ups with the team.
- Contribute to visual standards (icons, motion, data‑viz patterns) and brand consistency.
How we work (principles)
- Prototype to learn; productionize to last. Start low‑fi; add fidelity when it pays off.
- Words first. Plain language, fewer choices, obvious next steps.
- Accessibility is default. Keyboard paths, labels, contrast; test with real assistive tech.
- Performance matters. Design for fast first interaction; avoid UI that looks busy but feels slow.
- One system, many surfaces. Components serve app and web; document decisions.
- Close the loop. Ship small, observe real use (metrics + research), iterate.
- Jargon‑light, clarity‑heavy. Names people can guess; states they can recover from.
What you bring
- 2–5 years designing digital products end‑to‑end (startup experience welcome).
- Strong Figma skills (auto‑layout, variables, components, prototyping) and tidy files.
- Comfort with design systems, accessibility basics, and collaborating with engineers—without writing code.
- Taste for practical solutions, clear async communication, and good time habits in a remote setup.
Nice to have
- Exposure to Wealth Tech (portfolios, orders, statements) or Manufacturing/Should‑Costing workflows.
- Familiarity with data‑viz conventions, SEO/landing-page basics, and light experiment design (A/B with PM/eng).
Extra credit — portfolio prompts
-
A prototype that changed the plan (and what you learned).
-
A before/after where you removed steps or made the next action obvious.
-
A post‑launch iteration where you moved a metric (task success, time on task, or conversion) and how you knew.
-
Tell us 3 tiny stories: a usability test that surprised you, a flow you simplified, and a post‑launch improvement you shipped. Include links (portfolio, Figma files, notes or case studies).