Member of Technical Staff, Product

The role

As a Member of Technical Staff focused on Product, you’ll own entire product domains end to end. You'll work directly with our advisors, operators, and clients to understand what they need, then prototype, ship, and iterate fast. If you ship it, you own it

What you’ll build (and own)

- Advisor and operator surfaces. The tools your colleagues use to serve clients, built so one advisor can deliver high-touch service to far more clients than they could before. This is how the firm scales without the experience degrading.

- Consumer portals. Where clients interact with their advisor, see their full financial picture, and engage on their own terms. This is also our organic growth engine: the surface that turns a good experience into clients who come to us on their own.

- The AI that powers all of it. From the tools and skills agents use, to how those agents are embedded in the product itself. This is the layer that makes the other three feel intelligent rather than just digital.

Example problems you’d work on

These aren’t hypothetical; we’re actively working on versions of all of these.

- A research agent advisors actually trust. An advisor prepping for a client meeting needs to know how a pending divorce affects an estate plan, cross-referenced with tax law and the client's portfolio. The agent has to search proprietary data, integrations, and the web, then synthesize something the advisor can act on without second-guessing. "Close enough" isn't acceptable here. The hard part is building a system that knows what it doesn't know, and surfaces that uncertainty in a way that builds trust, under real constraints: compliance, auditability, and datasets where a stale answer is as harmful as a wrong one.

- Generative UI that doesn't break the advisor's flow. Our agents view and update the advisor's frontend in real time: dynamic scenarios, interactive plan adjustments, visualizations that shift as the conversation does. The challenge is ensuring agents can reliably render and manipulate our pages without feeling unpredictable. An advisor mid-call can't be troubleshooting their UI.

- An agentic planning engine that earns trust over time. A client about to retire wants to know if they can help their kids with a down payment. The agent has to hold a continuously updated model of each client's situation, surface the right adjustments at the right moment, and explain its reasoning in terms the advisor can relay in plain English—getting more accurate the longer it knows someone.

- A migration engine that makes every acquisition possible. Every firm runs on something different: a CRM last updated in 2011, a proprietary custodian export, a decade of notes in a shared folder. The engine has to ingest all of it and produce data clean enough to power the models we build on top. Get it wrong and the personalization doesn't work. Data quality is the moat; migrations are how we grow.

The kind of person who thrives here

You’re excited by ownership, ambiguity, and building things that matter.

- You're unusually good at understanding users and willing to act on it. You'd rather sit next to an advisor during a client call, watch where they hesitate, and come back with a point of view than wait for a PM to hand you a spec. You know the difference between what users ask for and what they actually need.

- You're ambitious in a way specific to this work. You're building for people who manage real retirement savings and estate plans. "Good enough" means something different here. You'll rebuild something that works because you know it won't hold through the next acquisition—and that standard motivates you more than shipping faster than last sprint.

- You move fast, and you know speed and reliability aren't in tension here. Advisors depend on what you build every day. Breaking prod isn't something you wait until Monday to fix.

- You’re someone people actually want to be in the room with. This is a 12-person team, one office, five days a week, working on problems that don’t have clean answers. The people who thrive here want to argue about product direction at lunch and then build something together in the afternoon. Kind, direct, and low-ego, you can give candid feedback without being an asshole, and you’re genuinely energized by this environment (not just tolerant of it).