Founding Design Engineer

About Prismera

Prismera builds AI for commercial real estate portfolio operations. Our platform ingests unstructured portfolio documents and turns them into structured intelligence that powers how institutional owners and operators manage portfolios worth billions. We handle everything from document understanding and data extraction to agentic portfolio workflows and deal execution.

We are backed by industry-leading executives, trusted by publicly traded REITs and national operators, and scaling into the largest institutional CRE firms in the world.

The Role

This is a founding design engineering role. You will own how Prismera looks, feels, and works: the interface design, the interaction patterns, the frontend implementation, and the systems that tie it all together.

The core problem is this: commercial real estate portfolio operations are enormously complex. Hundreds of workflows, thousands of documents, multiple user types ranging from a 25-year-old analyst to a 60-year-old portfolio manager who has been doing this for decades. The instinct most platforms have is to solve complexity with more surface area. More tabs, more pages, more menus. That is not what we are building. You will figure out how to collapse that complexity into something so simple it feels obvious, without losing any of the power underneath.

You will write production code. You will ship what you design. You will build relationships with customers across our client base and use those relationships to inform every decision you make about the product. If you think of yourself as someone who hands off Figma files, this is not the right fit.

What You'll Do

• Own the end-to-end design and frontend implementation of Prismera's product. You design it, you build it, you ship it.
• Define the UX patterns for agentic AI workflows: how users interact with AI that acts autonomously on their behalf, how they build trust in its outputs, how they intervene when they need to. This is a new design space with very few established patterns.
• Solve the information density problem: enterprise CRE users need access to massive amounts of data without being buried in it. You will design interfaces that surface the right information at the right time and hide everything else.
• Build a design system and component library that scales as the product grows, without accumulating technical debt along the way.
• Build and maintain direct relationships with an array of enterprise customers. You will be on calls, in Slack channels, and in their workflows regularly. What you learn from those relationships is what drives product decisions.

Who You Are

• 1-3 years of experience as a design engineer, product designer who codes, or frontend engineer with strong design instincts. What matters is the quality of what you've shipped, not the title you held.
• You can go from concept to production code. You are fluent in React and modern frontend tooling, and you write clean, maintainable code.
• You think about design in terms of user psychology, not just aesthetics. You care about button radius, but you care more about whether the person using the interface actually understands what is happening and what to do next.
• You have strong opinions on simplicity. You believe the hardest design problem is figuring out what to leave out.
• You are comfortable designing for users with wildly different levels of technical sophistication using the same product.
• Experience designing for AI-native or agentic products is a major plus. If you've thought seriously about how humans should interact with autonomous AI systems, we want to hear about it.
• You move fast, ship constantly, and refine based on real usage.
• You want to be close to customers. You see direct client relationships not as a distraction from design work, but as the most important input to it.
• Bonus: experience with enterprise SaaS, financial services, or complex data-heavy applications.

Why Now

We have enterprise customers, real revenue, and a product in a market where the incumbent software is decades old and was never designed for what AI makes possible. You would be joining at the earliest stage with the most leverage: not to maintain what exists, but to build what comes next.