Founding Engineer

Job Description

About Prismera

\n

\n

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. Over a billion square feet of commercial real estate is actively run on Prismera today.

\n

\n

We are backed by industry-leading executives, including operators who've built and run some of the largest commercial portfolios in the country, trusted by publicly traded REITs and national operators, and scaling into the largest institutional CRE firms in the world.

\n

\n

The Role

\n

\n

You'll be one of a small number of engineers working directly with the founders, owning full surface area of a production system institutional customers already depend on. You'll take a raw idea from a client meeting or investor conversation, a new workflow, a new failure mode in how leases get parsed, a new way owners want to interact with their portfolio, and turn it into shipped, production-grade product without adding technical debt or bloating the interface. There's no platform team to hand things to. If it's broken, it's yours.

\n

\n

What You'll Do

\n

\n

\n
• Build and own core product workflows across the stack: frontend systems, backend services, APIs, databases, and the interfaces customers interact with daily.
\n
• Design and ship interfaces that make complex portfolio operations, AI workflows, and enterprise data feel simple, fast, and intuitive.
\n
• Work directly with customers to understand workflows, identify friction points, and rapidly translate operational reality into production software.
\n
• Operate with high autonomy across product, engineering, and UX.
\n

\n

\n

Who You Are / Requirements

\n

\n

\n
• 1-3 years shipping production full-stack software. TypeScript/React on the frontend, Python services on the backend.
\n
• Strong relational data modeling: you can design a schema for messy, hierarchical real-world data (documents, versions, amendments) and defend your tradeoffs.
\n
• Hands-on AWS in production: containerized services (ECS/Fargate or similar), IAM, networking basics, and you've debugged something at 2am because of it.
\n
• Experience building on LLM APIs beyond a chat wrapper: structured extraction, evals, handling nondeterminism, knowing when the model is wrong.
\n
• Comfortable owning a feature end-to-end with no spec, no designer, and no platform team
\n

\n

\n

\n

Why Now

\n

\n

We have enterprise customers, real revenue, and a product entering a market where the incumbent software was never built for what AI now makes possible. You'd be joining at the earliest stage with the most leverage, not maintaining someone else's system, but defining how this gets built from here.

\n

\n

Location

\n

\n

Flatiron, Manhattan. Five days a week, in person.

\n