Technical Product Owner

Linxup•Chesterfield, MO

2h•Hybrid

About The Position

This is the product role for someone who likes the layer where software meets hardware. You’ll own the parts of Linxup that customers rarely see but depend on completely: our public API and the partner integrations built on it, the pipeline that ingests telemetry from a quarter-million devices in the field, and the OTA firmware and device management tooling we use to configure, update, and troubleshoot that hardware at scale. You’ll also own initiatives in our core web and mobile products, so you stay close to the end customer and the day-to-day experience — this is not a pure infrastructure role, and the mix is part of what makes it interesting. Your engineering team is technical, and so are many of your customers: partner developers reading your API docs, integration engineers at ERP and dispatch vendors, and internal teams who need visibility into a fleet of devices. Your job is to understand what they actually need, decide what gets built and in what order, and write requirements precise enough that engineers don’t have to guess. You don’t need to write production code. You do need to be the kind of product owner who reads the API response, runs the query, and looks at the device logs before forming an opinion.

Requirements

2–5 years as a technical product owner or product manager, business analyst, or software engineer — ideally on API, platform, integration, or connected-device products
A track record shipping technical products where the customer was a developer, a partner system, or a device —not only a screen
Experience working with software engineering teams in an agile process, and alongside hardware teams
Proven experience managing a product through all stages of its lifecycle
Hands-on comfort with REST APIs and webhooks: you can read a spec, exercise an endpoint in Postman or curl, and tell good payload design from bad
Working knowledge of SQL and enough data fluency to answer your own questions
Solid grasp of the SDLC, cloud infrastructure, and how data moves through a system end to end
Enough comfort with logs and observability tooling to narrow down whether a problem is the device, the network, the ingestion pipeline, or the application
You go to the primary source — the payload, the log, the query, the customer call — before you form a view
You understand that good software delivers on ease of use and makes complicated things feel simple
You translate complex technical concepts for non-technical audiences without losing what matters, and you write with precision
You can hold several parallel workstreams without losing the thread on any of them
You’re comfortable with ambiguity and with hardware realities you don’t fully control
You have a keen sense of UX and genuine empathy for customers

Nice To Haves

IoT or connected-hardware experience: telemetry ingestion, OTA update campaigns, MQTT or similar protocols
Familiarity with cellular connectivity in the field
Experience owning a public or partner-facing API, including deprecation decisions with real customers
Familiarity with event streaming or message queues (Kafka, MQTT, SQS, or similar)

Responsibilities

Own the roadmap for our public API and the partner ecosystem built on it — requirements definition, endpoint and payload design, authentication, rate limits, versioning, and deprecation
Work directly with partner developers and integration engineers to scope, launch, and unblock integrations
Treat developer experience as a product surface: clear documentation, predictable payloads, useful error messages, sandbox access, and sensible defaults
Own product requirements for ingesting data from GPS trackers, dash cams, and asset and equipment trackers deployed in the field
Partner with engineering on how device data is normalized, enriched, stored, and exposed — both to customers and to downstream features and reports
Work through the real-world messiness of field hardware: intermittent cellular coverage, buffered and out-of- order messages, power and duty-cycle tradeoffs, and data that is missing or ambiguous
Define the reporting, alerting, and rules behaviors that customers rely on that data to drive
Help build the operational visibility the business needs into device state, connectivity, and firmware versions across an installed base of 250,000+ devices
Own initiatives in our core web and mobile products alongside the platform work — the features customers touch every day
Write clear user stories and acceptance criteria, own and prioritize the backlog, and run refinement and sprint ceremonies with your engineering team
Partner with QA to define test cases and validate solutions against real device and API behavior
Make the call on scope and sequencing — and explain the tradeoff credibly to both an engineer and an executive
Serve as the internal subject-matter expert on our API, device data, and firmware capabilities
Talk to customers and partners regularly — including technical ones — and turn what you hear into prioritized, well-defined work
Stay current on competitive software and hardware to keep our solutions market-ready