> Markdown version of [/jobs/ext/2225075-business-operations-manager-systems-automation](https://www.wearedevelopers.com/jobs/ext/2225075-business-operations-manager-systems-automation). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Business Operations Manager, Systems & Automation - **Company:** OCRA, L.L.P. - **Location:** United States (Remote available) - **Experience:** Experienced - **Salary:** $115,000.0 - $145,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Business Systems, Data Sharing, Operational Databases, SQL Databases, Build Tools - **Published:** August 25, 2026 - **Apply:** https://jobs.ashbyhq.com/ocra/6ea85b8b-97bf-4c61-b72a-c92c51c2df9a ## About the Role * 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., * 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. ## Description * 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., * 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. ## Related Videos - [Modern Data Architectures need Software Engineering](https://www.wearedevelopers.com/videos/1030-modern-data-architectures-need-software-engineering) - [Smart City, Smart Mobility](https://www.wearedevelopers.com/videos/954-smart-city-smart-mobility) - [Fault Tolerance and Consistency at Scale: Harnessing the Power of Distributed SQL Databases](https://www.wearedevelopers.com/videos/1146-fault-tolerance-and-consistency-at-scale-harnessing-the-power-of-distributed-sql-databases) - [APIs and Architecture for scaling omnichannel payments](https://www.wearedevelopers.com/videos/90-apis-and-architecture-for-scaling-omnichannel-payments) - [Building a framework-independent component library](https://www.wearedevelopers.com/videos/1679-building-a-framework-independent-component-library) - [API = Some REST and HTTP, right? RIGHT?!](https://www.wearedevelopers.com/videos/1675-api-some-rest-and-http-right-right) ## Related Articles - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [The CAMARA Project: How Telcos Collaborating Improves Developer Experience](https://www.wearedevelopers.com/magazine/671-the-camara-project-how-telcos-collaborating-improves-developer-experience) - [E-Commerce in the Agentic Age: When "Buy" Becomes a Function Call](https://www.wearedevelopers.com/magazine/750-e-commerce-in-the-agentic-age-when-buy-becomes-a-function-call) - [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it) - [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)