About the Role  

CapIntel exists for the moments that shape someone's financial future. The conversation where an advisor explains a portfolio to a client anxious about retirement. The one where a family works out what happens to their parents' money now that their parents cannot manage it. Design is what makes those moments land, or fall flat. You are here to make them land.

One proposal tool is becoming a multi-product platform. Your scope is a product area, and it outlives any single release. You are who the ambiguous problems get routed to, including the ones the team could not settle on its own. Nobody signs off on your approach before you take it. When the evidence points against product or engineering, you are expected to say so, and to be right often enough that they keep asking.

And we build. Every designer ships something real every quarter: a prototype, a design system contribution, code. The best ideas here get built, not just drawn — you prototype until a direction is clear enough to commit to. Prototypes are how we scope work and settle arguments. AI is not a side experiment: reach for it by default and own what comes out. None of it happens alone: we review in the open, cover for each other, and the answer is usually a message away. People grow here by being handed something slightly bigger than the last one, and backed while they work it out.

What you’ll do 

• Own an area: Carry a product area across releases, and own a piece of the system other designers depend on: components, a prototype the team scopes from, or tooling that makes everyone faster
• Prototype to decide: Build working prototypes with real components and data to test ideas and align product and engineering before anything is committed
• Decide what's worth knowing: Choose the research worth running and say no to the research that will not change a decision. Own the synthesis and the call that follows it
• Own the number: Set the measure before the build, then stay with it. When it does not move, say so early and change direction rather than defending the design
• Set the bar, not just meet it: Define what quality means in your area so others can hold it without you. Error and empty states, responsive, WCAG 2.0 AA, and the patterns that keep it consistent after you move on
• Make the hard call land: Take a contested recommendation to people who outrank you and get a decision. Bring the options you killed and what you would need to see to change your mind
• Grow the people around you: Raise the standard through review, mentoring and the work itself. Your area should be a place designers get better in

What We’re Looking For 

• You have owned a product area across multiple releases, with a portfolio showing the judgment behind it: how you framed it, what you ruled out, and what you got wrong
• Depth across UX and visual design, plus one thing you are genuinely the best in the room at
• You build with AI and ship things others rely on, not just your own work
• Comfortable building: you prototype in code or with AI tools, understand how components and data shape a design, and know when a design is expensive
• You work confidently in complexity: dense data, permissions, regulated environments, information-heavy screens
• You disagree well, in public, and change your mind when the evidence turns

Bonus Experience

• Experience in fintech, wealth management or another regulated domain
• Taking something from zero to one, not only iterating on what exists
• Having built a design system, or a meaningful part of one, that outlasted you
• A background in front-end development, or experience working as a design engineer