Founding Product Designer

ABOUT MUDANZA

Memory that serves the relationship.

Mudanza is an early-stage advisory platform and governed memory layer for wealth management. We are building around a simple idea: what a firm learns about its clients should carry forward, with the context and evidence that make it useful.

A client’s priorities live across conversations, notes, documents, and separate systems. Our direction brings that knowledge into one living record, connecting it to planning and the work that follows. AI should help people prepare, understand, and follow through while preserving human judgment.

Our five co-founders bring experience in advisory practices, capital markets, technology consulting, enterprise data and AI, and building businesses. We are still early: these roles will help shape both the product and the way we build it.

Why this role matters

The most useful fact about a client may be a family concern mentioned at the end of a call. Our design challenge is to bring that context into daily work without creating another overwhelming system to maintain. You will shape how advisors, associates, operations teams, and clients understand the record and act on it. The product must make room for judgment: what is known, what changed, what needs attention, and what is still waiting for a person.

The scope of your role

This is a hands-on product design role from research through implementation. You will work directly with the founders, engineers, and implementation lead, drawing on their experience in advisory practices and technology. Expect to investigate real workflows, reduce unnecessary steps, prototype alternatives, and inspect the shipped result. Visual craft matters, but success is measured by whether people can understand and complete consequential work with confidence.

What you’ll own

• Research advisor and operations workflows, including meeting preparation, follow-up, client transitions, and review. Separate observed problems from requested features.
• Design how client context travels between workspaces so people do not repeatedly identify the household, re-enter facts, or lose the thread of a task.
• Make source attribution, changed information, incomplete records, and conflicting inputs legible without overwhelming the main experience.
• Design AI interactions that clearly distinguish generated content, verified sources, proposed actions, review, and completion. Include recovery paths when the system cannot answer.
• Create prototypes and run focused usability sessions. Translate findings into prioritized changes that engineering can implement and validate.
• Establish reusable, accessible patterns for dense data, forms, navigation, permissions, empty states, and errors across desktop and smaller screens.
• Partner through delivery: clarify behavior, review rendered work, and use feedback and task outcomes to refine the experience after release.

What you bring

• A portfolio of shipped product work with complex workflows, not only marketing pages or polished concept screens.
• Strong interaction design, information architecture, typography, and visual hierarchy.
• Experience gathering evidence from users and showing how it changed a design decision.
• The ability to describe behavior, edge cases, and accessibility requirements clearly enough to support implementation.
• Comfort collaborating closely with engineers and balancing an ambitious direction with a useful, coherent first release.

Especially useful experience

These are helpful additions, not a checklist you must complete.

• Financial services, enterprise software, data-heavy applications, or products with approval and audit workflows.
• Design systems, frontend implementation, conversational interfaces, or usability evaluation of AI-generated content.

Your first 90 days

A starting framework for the role; we’ll shape the sequence around product and customer priorities.

1. Days 1–30

   Study a core workflow and produce a shared account of the user’s goal, existing friction, and evidence gaps.

2. Days 31–60

   Prototype and validate a focused redesign, then partner with engineering to deliver it.

3. Days 61–90

   Measure what improved and turn successful patterns into reusable guidance for the next product release.

How we approach the work

Start with the person and the problem. Make a small, complete improvement. Keep sources and assumptions visible. Test the important failure cases, and follow the work through to its actual use. We value clear writing, thoughtful disagreement, and the ability to change direction when the evidence changes.

In an early team, ownership includes the edges: documenting a decision, helping a teammate, investigating an issue, and being honest about what is ready and what is still being built.