> Markdown version of [/jobs/ext/3810713-software-engineer](https://www.wearedevelopers.com/jobs/ext/3810713-software-engineer). 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). --- # Software Engineer - **Company:** Ohme - **Location:** UK - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Automation of Tests, Business Systems, Continuous Integration, Data Integrity, Relational Databases, Python (Programming Language), Microsoft Dynamics, Netsuite, SAP (Applications), Software Engineering, SQL Databases, Web Application Frameworks, AWS Cdk, Data Logging, ReactJS, Backend, Agentic-AI, Fastapi, Odoo, Front End Software Development, Api Design - **Published:** October 18, 2026 - **Apply:** https://startup.jobs/software-engineer-ohme-ev-com-10490666 ## About the Role * Around 3 to 5 years of professional software engineering experience, with strong Python. You have built and run backend services in production and you care about API design, testing and the operational side of keeping things healthy. * Familiar with AWS, containerised deployment and automated CI/CD across multiple environments. Infrastructure as Code, ideally AWS CDK. * Comfortable with AI-assisted and agentic coding tools, and appropriately sceptical of what they produce. You review generated code as rigorously as your own. * Commercial experience with Odoo is an advantage, but not a requirement. If you have worked on another ERP or a large business system - NetSuite, Dynamics, SAP or similar - or you simply have the appetite to learn one properly, we want to hear from you. * Comfortable on the frontend with a modern component framework. We use React for new work and Odoo has its own; we care that you can own a feature end to end rather than which framework you learned it in. * Strong relational data modelling and confident SQL. You think about entities, identity and referential integrity before you think about endpoints. * Curious about how the business actually works. Enthusiasm for understanding a business process properly matters more than prior domain experience. * At ease working directly with the people who use what you build - finance, operations and customer care - and able to turn a process someone describes to you into something precise enough to build against. * Comfortable in an established codebase you didn't write and self-directed when documentation is thin. Nice to have * Experience with Fast API or similar modern Python frameworks. * Exposure to multi-market complexity: currency, tax, language, or e-invoicing regimes. * Knowledge of the electric vehicle industry. What success looks like * First 3 months: you are shipping changes to the ERP confidently and independently, and you understand the business processes behind them well enough to question what you are asked to build. * First 6 months: you are contributing to the new capability services alongside your ERP work, and internal teams are using what you build every day. * First 12 months: you are taking a specification and delivering a capability against it independently, helping move functionality across from the ERP, and improving how we specify and build., Please note that we are unable to offer visa sponsorship for this role. You must have full eligibility to work in the UK. ## Description We're hiring a Software Engineer to join our Business Systems team, working on the systems that run Ohme's business across multiple markets. You will start where the business runs today: maintaining and extending our Odoo ERP and shipping new functionality for teams across the company. Alongside that, we are building a set of focused, independently deployable services that each own a single business capability behind a clearly defined contract. Expect roughly a 70/30 split between the two to begin with, shifting steadily towards the new build as it matures. This suits someone who wants to understand a business properly before rebuilding it, rather than someone looking for greenfield from day one. Two things shape how we work. First, we build from written specifications: behaviour, data shapes and acceptance criteria are agreed up front, and the build is evidenced against them. Second, we make use of agentic coding tools, so a meaningful part of the job is directing, constraining and reviewing generated code rather than typing every line yourself. Both mean we value engineers who read carefully, think in contracts and are hard to satisfy about correctness., * Build and maintain in the ERP: develop, extend and support the Odoo modules our teams rely on day to day and ship changes through our release pipeline with confidence. * Solve real operational problems: work with finance, operations and customer care to understand what they need, then build it from small process fixes to substantial new functionality. * Build capability services: design and ship independently deployable Python services that progressively take over business functions from the ERP, working to an agreed specification. * Interrogate the spec: find the gaps, ambiguities and edge cases before you build, not after. We expect specifications to be challenged. * Bridge old and new: build and maintain the integrations that let new services and the ERP work alongside each other while the transition runs. * Define and honour contracts: versioned APIs and event schemas, with sensible idempotency, retry and replay behaviour. * Build the operational UI: create the interfaces our internal teams use to run these capabilities, with a focus on clarity and speed for people doing the same task fifty times a day. * Test what you ship: automated tests that trace back to agreed behaviour, so we can prove a change does what it was meant to do and nothing else. * Instrument everything: tracing, structured logging, alerting and the reconciliation checks that show the new path agrees with the old one. * Document what you build: clear, current documentation of interfaces and the decisions behind them.