Technical Product Owner

Ocra•Chicago, IL

1d•Remote

About The Position

Ocra is an AI-powered Revenue Management System (RMS) and Global Distribution System (GDS) built for hotel parking assets. Hotels use Ocra to sell underutilized parking inventory through “parking OTAs” to non-guest customers looking to park near airports and event venues. Ocra's team of parking revenue management experts drives revenue growth without adding labor or disrupting operations, helping hotels increase net operating income (NOI) while never compromising parking for hotel guests and staff. Ocra partners with 50+ operators and 25+ hotel groups at 600+ locations. The company has raised $10M, most recently an oversubscribed $5M round co-led by Trestle Partners and MCR Hotels. As the Technical Product Owner, you are responsible for day-to-day delivery execution. This role is squarely focused on turning business needs into clear, actionable engineering work and ensuring that work ships predictably and at quality. You are the primary owner of tickets, requirements, sprint flow, and delivery coordination—not long-range roadmap ownership. You act as the connective tissue between stakeholders and engineering, ensuring the team always knows what to build, why it matters, and when it is done.

Requirements

Experience in agile delivery management and/or technical product ownership
Proven ability to run sprints and drive execution in fast-paced environments
Strong competency writing clear, buildable, testable user stories
Experience managing backlogs and prioritizing against business impact
Comfortable making scope and tradeoff decisions under time constraints
Strong cross-functional communication and stakeholder management skills
Detail-oriented with a focus on throughput, clarity, and shipped outcomes
Hands-on, execution-driven mindset with engineering-first thinking

Responsibilities

Lead core agile ceremonies: standups, sprint planning, reviews, and retrospectives
Own sprint execution: manage scope, dependencies, risks, and blockers
Maintain visibility into delivery health, throughput, and progress
Remove operational, technical, and cross-functional obstacles
Ensure stories are sprint-ready and QA standards are met
Communicate clear, consistent status updates to stakeholders
Translate business needs into clear, outcome-driven requirements
Write well-scoped user stories with explicit acceptance criteria
Groom and prioritize the backlog based on value, urgency, and constraints
Ensure backlog readiness before sprint planning
Balance feature delivery, technical debt, and operational needs
Make real-time scope and priority decisions as constraints evolve
Review completed work and accept/reject based on defined standards
Maintain visibility into PDLC readiness, dependencies, and upcoming work