Cornell '29, Urban and Regional Studies (College of Architecture, Art and Planning). Three internships on the operating side of real estate in Los Angeles: a Newmark retail brokerage team, an affordable-housing owner's asset-management team, and a 13-property multifamily operator.

The work I keep coming back to is the process underneath the asset: documents, checks, and the handoffs where things quietly go wrong. In summer 2026 I ran an annual affordable-housing recertification by hand, saw where it broke, and then built a small tool to make the checking reproducible instead of dependent on my attention.

• groundwork-review-engine — a deterministic document-review engine for LIHTC compliance files, built after doing that review manually. Re-checks income against source documents, cites every finding to its page, and refuses in code to state a regulatory conclusion. 33 tests, fictional data only, no users.
• palmier-demo — a property-walkthrough web prototype: a listing's photographs as a clickable room-by-room tour. Public demo; zero customers.
• mcp-records-demo — a small template Model Context Protocol server: typed tools, schema validation, writes off by default. A pattern demo, not a product.

Not a software engineer: the code here was written with heavy AI assistance under my direction. I chose the problems, wrote the rules, read the tests, and found the defects. What I do have is a habit of not trusting a number or a machine's output until I have traced it to its source, and a record of doing that on real regulated work.

Looking for a Summer 2027 internship in New York where cities, real estate operations and building the checks overlap. shr62@cornell.edu · linkedin.com/in/shanereiss