Senior Odoo 19 CE Developer (Claude Code Power User) — Take Over & Grow a Hospitality CRM

We have a working, well-architected Odoo 19 Community Edition project — a CRM for a Ukrainian hotel group (multiple properties). It already runs in production-grade infrastructure. We are NOT looking to rebuild it from scratch. We're looking for the one right person to take it over, keep what works, and own its long-term evolution: CRM first → HMS (hotel management) → accounting. This is a long-term seat, not a one-off task. Who we're actually looking for The hard part isn't "an Odoo developer." It's the intersection: You are genuinely senior in Odoo 19 CE — inheritance-only discipline (_inherit, _inherits, xpath), OCA-first reflexes, no core hacking, clean module boundaries. You are a real Claude Code practitioner — not "I've tried it." You use it daily in Odoo work: CLAUDE.md rulebooks, MCP servers, phase-gated prompting, subagents, file-based state across sessions. You have your own efficient workflow and real shipped cases to show it. You speak Ukrainian (fluent — this is non-negotiable; day-to-day communication is in Ukrainian). You can inherit someone else's codebase and extend it, rather than reflexively wanting to start over. If you're someone who already thinks "Pure Odoo monolith, OCA before custom, JSON-2 not XML-RPC, Standalone Owl when standard widgets won't do" — you'll feel at home here. The stack (so you can self-select) Odoo 19 Community + OCA modules (no Enterprise) PostgreSQL 16, Docker Deployment: Hetzner VPS via Coolify, GitHub Actions CI/CD, immutable SHA-tagged images Pre-commit: OCA odoo-pre-commit-hooks, ruff, pylint-odoo Doctrine: inheritance-only, one module = one concern (ruta_*), ADRs in MADR format AI-assisted development is the default way of working, not an afterthought Roadmap (long-term, in order) CRM — continue and harden the existing hospitality CRM HMS — hotel management (rooms, bookings, rates, operations) Accounting — Odoo accounting layer Plenty of runway for the right person. HOW TO APPLY (read this — generic proposals will be ignored) Please answer these in your proposal. Skipping them = automatic pass. Inherited, not greenfield: Describe ONE real Odoo project you took over (someone else's code) and extended in production. What was the worst thing you found, and how did you extend it without touching core? (Link/repo welcome but not required.) Your Claude Code workflow in Odoo: Concretely — how do you use it? CLAUDE.md, which MCP servers, how you handle context limits, how you keep it from breaking things. A 2–3 minute Loom or a tight written description is perfect. OCA: Which OCA modules have you actually used or contributed to for v18/v19? Name them. A judgment call: Give one example where you chose Studio/config over code, or OCA over custom — and one where you correctly chose custom anyway. Ukrainian check — answer this line in Ukrainian: Опишіть одним абзацом, як ви організовуєте файлову пам'ять проєкту (стан поза контекстом) при роботі з Claude Code. Start your proposal with the word PURE-ODOO so we know you read this in full. DO NOT APPLY IF You're an agency or a team reselling work — we want one accountable developer. Your first instinct is "let's rewrite it from scratch." We're keeping what works. Your Odoo experience is v16 or earlier only, or theoretical. You "plan to learn" Claude Code on this project. We need someone who already ships with it. You don't speak Ukrainian. ENGAGEMENT & TERMS Step 1: Short paid trial task (small, scoped, real) — so we both validate fit fast. Step 2: Long-term collaboration Start: immediate We're organized: documented architecture, ADRs, CI/CD, clean git history. You'll be inheriting order, not chaos. We just need the right hands to carry it forward.