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
An advisor should not have to reconstruct a client’s story before every meeting. Mudanza is building a living client record that carries context into preparation, planning, follow-up, and firm operations. This role turns that ambition into coherent, dependable product experiences. You will own complete slices of the application, including the parts users rarely notice until they fail: permissions, background work, error recovery, and the history of what changed.
The scope of your role
This is a hands-on individual contributor role with broad product ownership. You will work closely with Scott Jones, Mudanza co-founder, and collaborate with design, AI, integrations, and implementation. Expect to help define the problem, make architecture decisions, ship the solution, and stay close to its use. Early-stage work means improving an existing product while helping establish the standards the team will grow around.
What you’ll own
- Deliver complete workflows across React interfaces, TypeScript services, APIs, and relational data. Keep client and household context consistent as people move between workspaces.
- Build meeting preparation, record updates, task handoffs, and review experiences that make source information and outstanding questions easy to find.
- Design firm, advisor, and client authorization into the service layer. Verify access again when work executes, including background jobs and AI-proposed actions.
- Make loading, empty, stale, and unavailable states understandable. A missing financial input must remain missing rather than becoming a plausible-looking number.
- Partner on data contracts and asynchronous work so retries, duplicate requests, and partial failures do not silently corrupt the client record.
- Own meaningful automated coverage, accessible interaction, release checks, monitoring, and incident follow-through. Validate the deployed behavior as well as the local implementation.
- Use customer observations to prioritize small, complete improvements. Explain technical tradeoffs in terms of reliability, time to value, and the people doing the work.
What you bring
- A track record of shipping and supporting substantial web application features, with examples of your contribution from design through production.
- Strong TypeScript and React skills, plus practical experience with API design, SQL, schema changes, and asynchronous processing.
- Experience building multi-tenant or permission-sensitive software and testing authorization boundaries beyond what the interface displays.
- Good product judgment: you can turn an ambiguous workflow into clear acceptance criteria and choose a practical first release.
- Clear written communication, comfort reviewing code, and a willingness to investigate behavior across the entire stack.
Especially useful experience
These are helpful additions, not a checklist you must complete.
- Azure services and deployment operations; experience with financial services or other regulated software.
- Accessible design systems, audit histories, complex forms, or production AI integrations.
Your first 90 days
A starting framework for the role; we’ll shape the sequence around product and customer priorities.
- Days 1–30
Understand the existing product, trace a core advisor journey, and ship a focused improvement with release evidence.
- Days 31–60
Own a complete workflow with explicit permission checks, actionable error states, and feedback from the people using it.
- Days 61–90
Establish a repeatable delivery pattern and use observed results to identify the next reliability or usability improvement.
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.
How to apply
Share a product you helped ship. Tell us what you owned, a difficult tradeoff, how you knew it worked, and what you changed after release. Public code is welcome, but a written walkthrough is equally useful.
You do not need a particular degree, employer pedigree, or a perfect match to every useful skill. Explain the relevant work you have done and the perspective you would bring. If an adjustment would help you participate in a hiring conversation, mention it in your introduction.