Read the message
Start with what the resident actually said. Do not flatten a broken lock, a rent question, and a noisy hallway into the same score.
02
The road here
I came to software through physics. The useful part was making somebody else's work easier.
I studied applied physics at Cornell and spent time in an electron microscopy lab. Part of a magnetic-noise experiment meant doing the same slow analysis again and again. I wrote a small program to do it faster, and a researcher got hours back. That was the first time software felt useful to me.
I wrote a tool because the experiment was slow.
The code was not ambitious. It removed a tedious part of someone else's day. I still start there.
The new tool had to beat the spreadsheet.
At BlackRock, I built analytics software for financial advisors and the people planning their retirements. I won the internal Aladdin Hackathon three times. A prototype could still win the room and lose the next morning to a spreadsheet that people knew how to use.
We asked whether the school changed what someone could earn.
At Climb Credit, I ran product, engineering, and data while we built loans for career-focused education. We brought completion rates, graduate earnings, and employment outcomes into the product instead of pretending a credit score told the whole story.
At ResiDesk, the customer is right there in the conversation.
A resident's message can become an answer, a repair, a renewal conversation, or a decision about how a building is run. I want our product to follow that work far enough to know whether anything got better.
Homes covered in a four-month study of what residents said about Wi-Fi and how it related to renewals. Read the study
Climb's annual loan volume grew from roughly $1 million to $300 million while I led product, engineering, and data. The early Climb story
Annual recurring revenue reached by the advisor analytics product I helped build from its first version at BlackRock.