<aside> <img src="/icons/city_gray.svg" alt="/icons/city_gray.svg" width="40px" /> Odin Labs, Inc.

</aside>

<aside> <img src="/icons/row_gray.svg" alt="/icons/row_gray.svg" width="40px" /> Table of Contents

</aside>

<aside> <img src="/icons/flash_gray.svg" alt="/icons/flash_gray.svg" width="40px" /> Apply Now!

</aside>

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.

About the Role

We are hiring a Technical Product Manager to own the delivery lifecycle for product engineering at Odin. That 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.

What You Will Do

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 everything you touch.

What We’re Looking For

• 7+ years owning the delivery lifecycle for a product engineering team. Discovery, shaping, QA, release. You have been the person on the hook for whether work shipped well and whether it solved the problem.
• A track record of finding problems worth solving. You pitch your projects with conviction, but hold them loosely enough to abandon when new evidence falsifies your hypothesis.
• An engineering background that you still use. You have written production code in a prior role, you can read what engineers are working on now, and you can hold a real conversation about technical tradeoffs.
• Strong product instincts. You can read what a customer is actually trying to do, separate that from what they think they want, and decide what is worth building now versus later.
• You think like a customer when you test. You can tell when a project is ready for customers versus when it just feels close, and you have the QA instincts to know the difference.
• You have run enough projects against fixed deadlines to know what trade-offs land well in practice. You can read where a project is drifting and make adjustments early rather than letting it slip.
• You have coordinated rollouts across product, engineering, and customer-facing teams to get the right users to see it at the right time.
• You partner well across functions. Engineering as a peer, customer success on adoption, sales on customer expansion, and customers themselves during discovery.
• Strong written and verbal communication. Your pitches, docs, release notes, customer calls, and engineering meetings leave people informed and aligned.
• You have depth in multiple areas, not just one, plus the appetite to keep learning what each project demands.
• AI is part of how you work, used to accelerate your thinking rather than replace it. You review and refine every output, and what you put your name on is sharp and accurate regardless of which tool helped get it there.

Nice to Have

• Direct experience with construction tech, access control, workforce management, or other software that runs on a jobsite.
• Time at an early-stage startup where you helped shape the product process, not just inherit one.
• Figma fluency. You can produce the wireframe or mockup a conversation needs.
• Mobile or hardware-adjacent QA experience, where you have built a test program that covers a long tail of devices, environments, and physical conditions you cannot fully replicate in a lab.

Our Stack

You are not expected to have experience with all of these, but you should be comfortable reading and reasoning about them, and willing to keep growing into the rest.

• Kubernetes hosted on Google Cloud
• Postgres on Cloud SQL
• Node and GraphQL on the backend
• React on the web
• React Native and Expo on mobile
• TypeScript end to end
• Field hardware including badge readers, kiosks, turnstiles, and cameras
• Datadog for observability
• Mintlify for docs
• Figma and Claude Design
• GitHub, Shortcut, Slack, Notion, Google Workspace

Our Benefits

• Competitive salary package
• Comprehensive health insurance coverage for you and your family
• Flexible working hours and remote work options
• Generous vacation and paid time off policy