Middle Odoo Python Developer

Odoo Python DeveloperLocation: 90% WFH + 10% on site in SkawinaType: Full-time, 3m + permRange: 13-17k PLN gross___Role summaryWe are looking for a mid-level Odoo Python Developer who works primarily in Odoo Enterprise and can independently design, implement and maintain modules including API connectivity between Odoo and external systems. Independently is the operative word: you will be given a problem, an API specification and access, and be expected to come back with a production-ready solution — not to be walked through it. An example project will be: building a two-way integration with one of the Supply Chain Services providers to enable carrier stock visibility (pallet and shipment status, warehouse availability, orders creation and validation) directly in Odoo. You will not be starting from nothing: we already run multiple carrier and internal integrations, so there is a pattern to follow and improve on. Key responsibilitiesWork mainly in Odoo.sh: branches, builds and deployments; analysing logs; debugging with the Shell and monitoring toolsDesign, develop and maintain custom Odoo modules — models, business logic, views, security, reports — for logistics, inventory and manufacturing workflowsIndependently deliver the API integration end-to-end: consume their API securely (auth, tokens/keys), map carrier data onto Odoo models (shipments, pallets, locations, statuses), and implement synchronisation — scheduled jobs, retries, idempotency, error handling and logging that someone can debugged easily by any member of the team. Extend the same approach to other carriers and external systems, including the storefront that talks to Odoo over APIsReview Pull Requests before it reaches production. Multiple sources of changes to the custom modules - you are a quality gate, and this is a real part of the job rather than an afterthoughtPerformance work backed by evidence. A recent example from codebase: a computed field added significant slowdown in processing orders and deadlocks. It was diagnosed by reading access logs and Postgres deadlock traces, not by guessing. You should be comfortable with data EXPLAIN, with why a GIN trigram index cannot serve an =, and with reasoning about ORM recompute cascadesHandle multi-company properly — with dozens of companies, company_dependent fields, record rules and pricelist resolution are where the sharp edges liveCollaborate with logistics, warehouse and sales teams to turn requirements into designs that survive contact with productionRequirements — must haveStrong Python and Odoo backend skills: ORM (create, write, search, unlink), computed and stored fields, constraints, onchanges, access rules2+ years of commercial Odoo or comparable ERP backend development, including at leastone integration you personally owned from reading the API documentation through to productionProven API integration experience: REST/JSON, authentication (API keys, tokens, OAuth), pagination, timeouts, retries, error handling, logging and monitoringSolid PostgreSQL: how queries behave under load, indexes, join patterns, batching, transaction scopeGit-based workflows — branches, pull requests, code review — preferably on Odoo.sh or similar Git-driven hostingComfort with MacOS Terminal / Linux Shell - running commands, reading logs, checking processes, analysing resource usage and troubleshooting performanceComfortable with using and challenging AI in your daily workEnglish for written technical discussion with partners; Polish and English day-to-dayNice to haveAWS prior knowledge - knowing principal AWS services such as S3, EKS, Cloudfront…Experience with logistics and carrier integrations: track & trace, shipment status, stock visibilityExperience integrating an external storefront with an ERP over APIJob-queue patterns (OCA queue_job, Celery, SQS) — we run home-grown queue models plus ir.cron, and experience with any of these transfers directlySOAP integrations with accounting systemsTest automation: unit tests for Odoo modules, integration tests for APIsWhat we offerOwnership of strategic integration projects such as Carrier/API stock visibilityDaily work on real production systems in manufacturing, retail and logistics — not a sandboxGenuine influence over integration architecture, and a say in what partners are allowed to shipAutonomy: this role exists because we want to increase speed of delivering best services internally within our companyWhat success looks like after six monthsThe API/Carrier integration is live and you are not the only person who can support it, because you documented it. And at least one partner pull request was materially better because you reviewed it.