Product Manager, Admissions and Finance Systems

About the role

International House at UC Berkeley is a non-profit residential and program community committed to fostering intercultural respect, mutual understanding and leadership skills, so that residents and alumni promote a more equitable and peaceful world. I‑House is home to graduate and undergraduate students, visiting scholars and interns from across the United States and around the world. The building operates year‑round as a residence, a dining hall, a conference and events venue and a program center, which means the systems that run it touch admissions, finance, housing operations, dining, facilities, security and human resources at the same time.

The Product Manager, Admissions and Finance Systems owns the systems that move a resident from application through to payment. You will support the Admissions and Financial Aid Department with the annual application build, billing and payment automation, and the reporting that tells the organization whether any of it is working. This is a product role rather than a help desk role. You will decide how a process should work, build or configure it, test it, document it, and then own the consequences when the cycle runs. The application build in particular is a fixed calendar commitment: it has to be complete and tested before offers go out, and there is no manual fallback. You will work most closely with Admissions and Financial Aid, Accounting, Housing Operations and the technical team, and with StarRez and our payment providers.

Responsibilities

• Build, configure and test the annual application in StarRez for each cycle, to a deadline set by the offer calendar, and hand it to the Director of Admissions and Financial Aid for sign-off.
• Own day‑to‑day StarRez administration and troubleshooting, including terms, rates, room and rate assignment, booking statuses and the business rules behind them.
• Maintain the integrity of booking and contract records.
• Reporting problems are solved in the reporting, not by deleting records.
• Support move‑in and move‑out cycles, including the access, card and data steps that have to happen in the right order.
• Own the accounting automations that apply late fees and charges, run payment schedules, and generate the resident statement of account.
• Own the payment integrations and the routing behind them, including Stripe and TouchNet, and the webhook and signing key configuration each provider requires.
• Make sure the resident‑facing account summary in the portal reflects what the ledger actually