InvestCloud is a private-equity backed platform business supporting over $6 trillion of assets globally, with deep, long-standing relationships across the asset and wealth management ecosystem.Private markets are rapidly becoming a core part of wealth portfolios – but the industry infrastructure has not kept pace. Most wealth managers still rely on manual processes, fragmented data, and operational workarounds to deliver private market exposure.
InvestCloud’s Private Markets Network (PMN) is designed to change that. PMN is a network-level execution and processing platform that enables private market investments to be delivered at managed-account scale, with the same operational discipline and integration model that wealth managers expect in public markets.
This role sits at the intersection of strategy, product, and technology – bridging the gap between where PMN is going and what the team can actually build. Its core currency is turning ambiguous problems into something concrete that others can react to, fast.
Purpose of the Role
PMN moves fast and operates across complex, interconnected domains. Strategy, product, and technology each have their own language – and too often, things get lost in translation between them.This role exists to close that gap.
The Product & Prototyping Lead takes fuzzy strategic questions and operational pain points and turns them into working prototypes that teams can learn from, react to, and build on. They are equally comfortable in a whiteboard session with leadership and a hands-on build session with engineers – and they know how to move quickly between the two.
What You’ll Actually Be Doing
This role cuts across boundaries and moves fast. On any given week, you might be:
1. Sitting with PMN Ops or Product to get to the bottom of a real problem – and leaving with a clear plan for what to build next.
2. Building a working prototype to test an idea before anyone has written a spec.
3. Running a demo with senior stakeholders and extracting the signal from their reaction.
4. Turning a messy strategic question into a concrete experiment with a clear pass/fail.
5. Helping engineering understand not just what to build, but why – and what success looks like.
6. Telling the team clearly and early when something isn’t working – and redirecting to what will.
7. Keeping strategy, product, and engineering aligned without creating process overhead.
Key Responsibilities
Bridging Strategy, Product & Technology
8. Act as the connective tissue between PMN’s strategic direction, product priorities, and engineering execution.
9. Translate high-level strategic goals into product problems worth solving, and product problems into things engineers can build.
10. Help PMN leadership make better decisions by giving them something tangible to react to rather than abstract options.
11. Maintain a clear, honest view of what’s feasible – and push back constructively when strategy outpaces reality.
Discovery & Problem Definition
12. Run structured discovery with PMN Ops, Product, and Engineering to surface the highest-value opportunities.
13. Turn vague pain points and strategic ambitions into well-defined problem statements with clear success criteria.
14. Maintain a prioritised opportunity backlog with transparent impact/effort reasoning.
15. Make confident calls on what not to pursue – and articulate why clearly.
Rapid Prototyping
16. Build functional prototypes quickly – good enough to learn from, not necessarily to ship.
17. Use modern tooling – including the latest AI to compress the time from idea to something testable.
18. Design each prototype around a specific question: what do we need to learn, and what’s the fastest way to learn it?
19. Know when a prototype has done its job and move on.
Demo, Alignment & Iteration
20. Run compelling, well-structured demos to internal stakeholders and leadership.
21. Use demos as an alignment tool – to surface disagreements, sharpen requirements, and build conviction.
22. Extract clear signal from stakeholder feedback; translate it into sharper problem definitions or go/no-go decisions.
23. Iterate quickly; treat each cycle as an opportunity to learn, not just to refine.
Handoff to Engineering
24. Define what “validated and ready to build” looks like: outcomes, acceptance criteria, data requirements, integration points.
25. Stay close through early build to ensure the intent of the prototype is preserved.
Essential Skills & Experience
26. Strong product instincts: able to frame ambiguous problems into clear outcomes, make confident prioritisation decisions, and define what good looks like.
27. Hands-on prototyping ability: comfortable building working demos and proof-of-concept tools independently – not just writing specs for others.
28. Technical fluency: enough engineering depth to work credibly alongside developers, understand trade-offs, and prototype against real systems and data – without needing to own production code.
29. Comfort with modern tooling: familiar with the current landscape of AI, no-code, and low-code tools; picks up new ones quickly.
30. Discovery and user research: skilled at extracting genuine insight from stakeholder conversations; able to distinguish between what people say and what they actually need.
31. Demo and communication skills: able to run structured, compelling demos and translate technical concepts clearly for senior, non-technical audiences.
32. Comfortable with ambiguity: able to operate without a defined playbook, bring structure to loosely-defined problems, and make progress under uncertainty.
33. Typically 4–8 years’ experience in a product, technical product, or product-engineering role.
Desirable Skills & Experience
34. Experience in financial services, B2B SaaS, or other regulated or data-sensitive environments.
35. Exposure to private markets, wealth platforms, or operations tooling.
36. Prior experience acting as a bridge between product and engineering in fast-moving environments.
37. Familiarity with data pipelines, APIs, or operational systems – enough to prototype against real data sources.
38. Experience running structured discovery or design sprint processes.
Personal Attributes
39. Shows rather than tells – defaults to a working prototype over a slide deck.
40. Moves fluidly between strategic thinking and hands-on building; neither feels like a step down.
41. Energised by iteration; not precious about ideas that aren’t working.
42. High conviction, low ego – changes their mind when the evidence points that way.
43. Keeps moving when things are ambiguous; brings clarity rather than waiting for it.
44. Earns trust quickly across different audiences – from ops teams to the executive level.