技术总监
Director of Technology
Ocra正在构建停车行业的商业开发者平台，是连接卖家、预订渠道以及资金流转系统的中间层。在此之上，我们推出了SaaS产品：Ocra Direct，这是由渠道运营商拥有和运营的白标产品；Ocra Terminal，让收入团队从一个界面定价其全部组合；Ocra Settlement，用于结算每个渠道应支付的金额。每个产品都可以独立运行，但它们共同形成闭环。
Ocra与众不同之处在于机器学习。该平台位于需求、定价决策和实际收入交汇的地方。这是现有企业不具备的视角。这个位置使我们的模型能够学习市场中真正驱动收入的因素，而不是模仿去年的报价表。其他人只销售仪表盘，而我们销售的是每天都在变好的系统。
我们正在寻找一位领导者，他能在小型、分布式团队中工作，自主性、好奇心和适应能力比僵化的流程更重要（但我们也在不断优化流程）。
## 你将负责的工作
- **负责产品、工程和测试的交付**：总共约十人。你对发布的内容、频率以及生产环境中的稳定性负责。
- **贴近工作本身**。在这个规模下，你会参与设计评审、阅读PR，并且偶尔会写代码。你不仅仅是管理层：你是真正了解系统如何运作的人。
- **管理工程体系，而非工程师的任务**：解除依赖关系，尽早消除歧义，保持“决定”到“上线”的路径简短而枯燥。
- **将可靠性作为平台的属性，而非英雄行为**：保证可用性、错误预算，以及一个小团队可以真正维持的值班轮班制度。
- **在定价业务背后扩展平台**：高吞吐量的数据摄入、事件流水线和API，为十几个预订渠道的数百个地点提供服务，未来两者都会继续增长。
- **将API表面作为产品来管理**：合作伙伴集成、访问控制、第三方渠道和我们自己的应用都使用它。版本控制、合同、弃用策略和文档都由你负责。
- **将集成转化为可重复的模式**：每个新渠道和每个访问控制供应商都应该比上一个更便宜。目前还做不到这一点。
- **在不增加仪式感的前提下提升工程严谨性**：CI/CD、环境、测试策略和可观测性，这些应该加快小团队的速度，而不是阻碍它。任何成本高于收益的流程都是你要优化的对象。
查看英文原文
Ocra is building the commercial developer platform for parking. The connective layer between sellers, booking channels, and the systems that move money between them. On top of it we ship SaaS: Ocra Direct, a white-label channel operators own; Ocra Terminal, where revenue teams price their entire portfolio from one surface; and Ocra Settlement, which reconciles what every channel owes. Each stands alone. Together they close the loop.
What separates Ocra is the machine learning. The platform sits where demand, pricing decisions, and realized revenue all pass through. A vantage point no incumbent has. That position lets our models learn what actually drives revenue in a market rather than mimic last year's rate sheet. Everyone else sells dashboards. We sell a system that gets better every day it runs.
_We’re looking for a leader who is energized by working in a small, distributed team where autonomy, curiosity, and adaptability matter more than rigid processes (but we do work on our processes)._
## What you will be doing
- **Own delivery across product, engineering, and QA**: roughly ten people total. You're accountable for what ships, how often, and whether it holds up in production.
- **Stay close to the work**. At this size you're in design reviews, reading PRs, and occasionally in the code. You're not just a layer of management: you're the person who knows how the system actually works.
- **Run the engineering system, not the engineers' tasks:** Unblock dependencies, kill ambiguity early, and keep the path from "decided" to "in production" short and boring.
- **Make reliability a property of the platform, not a heroic act**: Uptime, error budgets, and an on-call rotation a small team can actually sustain.
- **Scale the platform behind the pricing business**: high-volume ingestion, event pipelines, and APIs serving hundreds of locations across a dozen booking channels, with more of both coming.
- **Own the API surface as a product:** Partner integrations, access-control systems, third-party channels, and our own applications all consume it. Versioning, contracts, deprecation, and docs are yours.
- **Turn integrations into a repeatable pattern:** Every new channel and every access-control vendor should be cheaper than the last. Today they aren't.
- **Bring engineering rigor without ceremony**: CI/CD, environments, testing strategy, and observability that speed a small team up rather than gate it. Process that costs more than it returns is your problem to remove.
- **Partner with the AI team on the surfaces they depend on**: data capture, event ingestion, model serving. You're not building models; you're making sure the platform they run on is dependable and instrumented.
- **Sequence the roadmap honestly**: surface tradeoffs early and say no clearly when something can't be done well in the time available.
- **Hire deliberately:** Going from where we are to ~10 means every hire is visible in the team's output. Set the bar, run the loop, and grow the people already here.
## Core skills & experience
- **8+ years building production software, with 3+ leading teams**: Team sizes in the 5–15 range are exactly right; we're not looking for large-org management experience.
- **Still technical and glad to be:** You've led while remaining hands-on, and you'd be uncomfortable managing a system you couldn't debug.
- **Depth in distributed systems and API platforms**: services, queues and event streams, integration patterns, and data models that survive contact with the real world.
- **A real SRE track record**: SLOs, incident command, capacity planning, cost-aware infrastructure. You've woken up and fixed the class of problem rather than the instance.
- **Experience scaling a system:** Traffic, data, or integrations, and the scars to say what you'd do differently.
- **Third-party integration experience**: especially where partners are inconsistent, poorly documented, or occasionally wrong. Parking, travel, hospitality, payments, logistics, or marketplace backgrounds all translate.
- **Ownership of QA strategy:** what gets automated, what stays manual, and how quality gets measured rather than asserted.
- **Clear written communication:** Design docs, incident writeups, and roadmap updates people outside engineering actually read.
## Bonus points (wouldn’t it be sweet if …)
- IoT, hardware, or sensor integrations
- revenue systems, marketplaces, or financial reconciliation
- having taken a partner-facing API program from early stage to mature
- having been the first or second engineering leader somewhere
## Who you are
- Clear & Direct Communicator
- Communicates with clarity, precision, and honesty.
- Assumes good intent and avoids unnecessary fluff.
- Adaptable Generalist
- Curious and eager to learn unfamiliar parts of the system.
- Collaborative & Feedback-Friendly
- Pragmatic & Impact-Oriented
- Focuses on delivering value, not chasing perfection.
- Makes thoughtful tradeoffs between speed and quality.
- Flexible & Proactive
- Raises issues early and steps outside their lane when needed.
## Non-negotiables
- We value humility, curiosity, and outcomes over ego or rigid process.