Product Owner

Glasgow, hybrid - £32,000–£37,000 depending on experience - Full time - Reports to Senior Product Manager

Pelion provides IoT connectivity to businesses that run connected devices at scale: fleet trackers, EV chargers, payment terminals, telecare alarms, smart meters. Those devices sit in the field, where a connectivity failure is an operational failure, so reliability is the whole job. We run 1.8M+ connections across 600+ networks in 150+ countries, at 99.995% uptime.

We're a small company with a broad product: a customer portal, tariffs and cost control, eSIM provisioning, security and monitoring, and the APIs that tie it together. That breadth is what makes product work here interesting, and it's why we need someone who can turn agreed direction into shipped software, every time.

This is a role for someone early in their product career who has already shipped with a product team and wants more ownership than they have now.You will join a product team of two: you and our Senior Product Manager, who owns direction, discovery and prioritisation. You own delivery, end to end. Approved requirements arrive as short PR-FAQs and PRDs; your job is to turn them into work the engineering team can build without guesswork, and to see that work through to release.You will work day to day with the engineering squad, with Data, Operations, Support and Customer Success around you. The team is small, the process is yours to run, and the work you specify ships. The detail matters: a well-specified ticket saves the team a week, and an ambiguous one costs them one.

• Engineering is never blocked waiting for a specification, an answer or a decision
• Tickets meet the definition of ready before build starts, and features ship without rework caused by unclear scope
• The delivery process is followed without chasing: nothing reaches build unspecified or skips a QA state
• Plans reflects reality, so anyone in the business can see what is being built, why, and where it stands

• Translate approved PR-FAQs and PRDs into epics, user stories and acceptance criteria that engineering can build from without guesswork
• Break features into increments that are sized, sequenced and independently releasable where possible
• Write acceptance criteria that are testable, so QA knows what to check and "done" is not a matter of opinion
• Spot the gaps in a requirement early, and get answers before build starts rather than during it

Run the backlog and the delivery process

• Run backlog refinement and keep tickets meeting the definition of ready: specified, signed off, sized and understood before work starts
• Keep work moving through the delivery process end to end, from specification through review and QA to release, with nothing skipping a step
• Keep Jira accurate as the record of delivery: statuses, links between epics and stories, and decisions captured on the ticket
• Track work through to release: acceptance against the criteria you wrote, release readiness, and handover to Support and Operations

Be engineering’s first call

• Be the first point of contact for engineers' questions on scope and acceptance criteria, and answer them quickly
• Know which questions are yours to answer and which are decisions to escalate, and escalate them promptly rather than letting work stall
• Communicate progress, risks and dependencies clearly and early
• Feed what you learn in delivery back into how requirements are written, so specifications keep improving
• You have a year or more in a product role, such as associate product manager, junior product owner or product analyst, and you have taken at least one feature from written requirement to release with an engineering team
• You know what a good ticket looks like because you have written bad ones and lived with the consequences
• You write clearly. Your tickets, notes and messages reduce ambiguity rather than add to it
• You are organised and you notice detail. You are comfortable being the person who keeps tickets, statuses and process honest
• You ask questions until you understand, and you know the difference between a question you can answer yourself and a decision someone else needs to make
• You have used Jira and Confluence, or similar tooling, in a team that ships software
• Experience in connectivity, telecoms or IoT, or curiosity about how mobile networks and SIMs work
• Familiarity with technical products: APIs, platforms, integrations
• Exposure to QA and testing practice
• Exposure to product discovery: user research, problem framing, prioritisation
• A recognised agile or Product Owner qualification

If your experience does not match this exactly but you recognise yourself in the description, apply anyway and tell us why.

• £32,000–£37,000 depending on experience
• Hybrid working from our Glasgow office
• Real ownership of delivery across the whole product, and a clear route into discovery and direction
• Flexible, hybrid (2 Days in our Glasgow Office)
• 25 days holiday
• 7% employer pension contribution
• Access to comprehensive health and dental plans
• Health assessment
• Life Assurance
• Group Income Protection