Business Operations Manager, Systems & Automation

Business Operations Manager, Systems & Automation Location: Remote (anywhere in the U.S.) Reports to: Chief Operating Officer Type: Full-time, Salary, Exempt Salary Range: $115,000-$145,000 Collaboration Hours: 10a-6p Eastern, Monday-Friday About Ocra 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 across North America. The company has raised $8M, most recently an oversubscribed $3M round led by Trestle Partners. The Role Ocra is scaling quickly, and we are investing in the systems layer that lets the business grow faster than its headcount. You will take the recurring, high-effort work that runs across Operations, Accounting, and Revenue and build it into systems: automated where the work is mechanical, streamlined where it needs judgment, and connected so the pieces talk to each other. The emphasis is on systems, not one-off tools. Plenty of companies accumulate a graveyard of clever scripts that each solve one problem and integrate with nothing. We are building the opposite, so each thing you build makes the next one easier. That often means redesigning how the work happens rather than simply automating the steps as they exist today. You will not be starting from a blank page. There is existing tooling to build on and a clear backlog waiting, so you can ship something meaningful early rather than spending a quarter building consensus. You will get a direction and the first five percent: what we use, how we use it, and where the problems are today. From there you own it. You do your own discovery, write your own spec, and come back around ninety-five percent so we can pressure-test the last five together. The work spans the company, so the people you work with do too. You will sit with department heads to understand how their part of the business runs and scope what to build, then with the individual contributors whose daily work your systems change. Being effective in both conversations is central to the job. Responsibilities Activation and onboarding. Build the systems that take a new location from signed to live with minimal manual coordination, so activation throughput scales with the pipeline rather than with headcount. Client reporting and billing. Build the pipelines that produce and deliver client reporting and billing preparation, so a person reviews and approves rather than assembles. Revenue and forecasting visibility. Stand up the reporting that gives leadership and clients a current view of performance against plan. Cross-team data and integrations. Own the data that spans departments, including commercial and contract terms, and the integrations that keep it consistent everywhere it is used. Adoption and enablement. Own the rollout as well as the build. Train the people whose work changes and make it clear what the system does and does not do for them. A system nobody adopts has not shipped. Intake and prioritization. Run a clear path for requests coming from across the business, so priorities and status are visible to everyone. Documentation. Document what you build so others can build on it. How You Will Work Understand before you prescribe. Learn the real pain points from the people doing the work, and get their buy-in before you build. Someone who hears a problem and ships a prescription will not succeed here. Build systems, not one-offs. Everything should be designed to connect: shared data, consistent interfaces, something the next project can stand on. Start with the smallest kernel, then connect it. Build one real component completely rather than designing everything on a whiteboard first. Progress over perfection. Turning hours of repetitive work into minutes is a win even if the rest stays as it is, and it beats trying to redesign someone's entire workflow in one move. The machine does the work, the human makes the decision. Automate what has no nuance. Leave the judgment call with a person: is this right, does it have what we need. What a person should not be doing is the work in between. Design the fallback too, not just the happy path. You build it, you own it. If it breaks, the call comes to you. What This Role Is Not Not platform engineering. You build on our monitored APIs and existing deployment processes. Anything customer-facing or core-platform belongs to Engineering, and you will have that boundary in writing before you accept. Not customer support. A separate role owns tier-2 escalations. You will get internal questions on systems you own, and reducing that over time is part of the mandate. Not a business analyst seat. You may build reporting, but the job is not to make today's process faster. Expect to ask whether a process should exist in its current form at all, and to redesign it rather than automate around it. Qualifications 4+ years in operations, revenue or sales operations, business systems, or implementation, with a track record of building the tooling rather than only running the process. You have shipped something people used. Not analysis, not a recommendation, not a plan someone else executed. Working tooling that ran, had users, and that you owned including its failures. You author software rather than only configuring tools. Expect to write and maintain APIs, work in a repo daily, query a production database in SQL, and script against third-party APIs that were not built for what you are doing with them. Fluent with Claude and comparable AI tooling. Command of the customer lifecycle. From deal to activation to live operations to revenue recognition to billing, you can hold the whole path in your head and know where the numbers come from. You cannot automate a lifecycle you cannot describe. Comfortable across levels. You can scope with a department head in the morning and sit with the person doing the manual work in the afternoon, and get what you need from both. Discovery before delivery. Handed a process to automate, your first move is to watch it and talk to the person running it. Candidates who open with "here is what I would build" will not be a fit. Nice to Have Experience in parking, hospitality, travel, or another operationally complex, multi-channel business. Experience integrating systems that were not designed to talk to each other, where each feed has its own format, cadence, and definition of the same number. Experience being the first or only person doing this kind of work somewhere. Benefits Equity for everyone. Stock options are part of every Ocra offer, at every level. Fully remote. Work from anywhere in the U.S. We hold a 10a to 6p Eastern collaboration window and otherwise trust you to run your own day. Health, dental, and vision coverage, with employer contribution. Paid time off. Real autonomy over what you build. You will help decide what gets automated next, not just execute someone else's backlog. Work that compounds. Every system you ship makes the next one easier and gives time back to a team that felt the problem.