Technical Product Manager

About Odin

Odin Labs, Inc. (“Odin”) is the workforce visibility and compliance platform powering the next generation of infrastructure. As demand accelerates for AI data centers, clean energy projects, and large-scale construction, Odin provides the operational backbone for real-time workforce tracking, credential verification, site access, and compliance management. We experienced more than 7x revenue growth from 2024 to 2025, and 2026 has already surpassed 2025 growth.

Odin’s growth is driven by rapid expansion and adoption of our software platform across complex, high-compliance construction environments. As we continue to see strong market momentum and a growth in complex construction programs, Odin is preparing for its next stage of scale.

We are hiring a Technical Product Manager to own the delivery lifecycle for product engineering t means identifying the problems worth solving, shaping the projects that solve them, staying close to the engineering team as they build, sharing QA with them, and getting what they have built in front of customers.

Most engineering work at Odin happens inside autonomous teams of 2-3 engineers that take a scoped project end to end. You sit alongside the engineering leads anchoring these teams as a peer, not above them. You own the why and the what. They own the how. You partner with customers during discovery and with customer success on targeted outreach to increase adoption of released features.

The engineering background is a qualification, not the job function. You will not be writing production code day to day, but you will have the technical fluency to scope projects realistically. That fluency also lets you use AI to prototype the desired UX directly in code, communicating the end state with more fidelity and less effort than disposable design artifacts.

Engineering leadership sets the product direction. You take it from there, from finding the problems worth solving to maximizing customer adoption of what ships.

• Find the problems worth solving, whether you surface them yourself or get handed one to research. Sit with customers, work through product data, and pull insights from internal teams.
• Shape the most important problems into projects engineers can build from, each with clear purpose, outcome, and boundaries.
• Pitch what we should build next, defending the problem, the user, and the bet behind each project.
• Lead project kickoffs and stay close to the team throughout execution. Answer questions as they come up and review the work as it takes shape.
• Defend the deadline by cutting scope. As the team finds where the work is hard, you decide which nice-to-haves come out and what has to stay for the project to solve the problem. You trim scope, not quality, to end on time with a clean slate.
• Share QA with the engineers building the work. They own story-level quality. You hold the bar for whether the project, as a whole, is ready for customers.
• Decide when customers see what the team has built. The engineers own when code reaches production, you own when customers see the feature. Use feature flags and incremental rollouts to keep the two decisions independent and the landing smooth.
• Drive adoption of what shipped by authoring help docs, posting feature announcements, ramping internal teams, and partnering with customer success on targeted outreach to specific accounts.
• Do the design work that does not need a designer, like lofi mockups, wireframes, or screens mocked in code, to communicate intent and unblock conversations.
• Build first-hand knowledge of how Odin's customers actually work. Visit jobsites, sit with workers and security teams, watch the product in use in a guard booth or trailer. Carry that understanding into…