Technical Product Manager

The Sage Group; United States; On-site; USD 110,000 - 160,000; Full time

Job summary

The Sage Group’s client in the AI Cybersecurity space seeks a mid-level Technical Product Manager to scale product ownership. You’ll define what we build and why with enough technical depth to earn engineering trust and translate customer problems into sharp requirements from day one.

This is a product-thinking role first with the depth to engage architecture discussions, evaluate tradeoffs, and drive security-focused outcomes.

Qualifications

• 3–6 years of product management experience with technical/infrastructure or security focus.
• Security background with identity, access management, cloud security, or compliance (SOC 2).
• Technical depth to engage engineers on design and architecture decisions.
• Strong product instincts and autonomy with minimal oversight.

Responsibilities

• Own product definition end to end: identify problems, write specs, and tradeoff scope and technical approach with engineering.
• Evaluate build-vs-buy, architecture options and technical debt tradeoffs with engineers.
• Translate security concepts to requirements and align with customer/market needs.
• Research competitors and market trends to inform investment areas.
• Collaborate with design to shape product experience for technical and security-heavy features.
• Develop sales enablement materials, demos, and talking points for the product.
• Conduct customer discovery and validate problems to shape prioritization.
• Contribute product perspective to analyst conversations and messaging.

Skills

Product management

Security concepts

Technical depth

Autonomy

Job description

The Sage Group’s client in the AI Cybersecurity space looking for a mid-level Technical Product Manager to help scale product ownership as we grow. You'll take on real product surface area — defining what we build and why — with the technical depth to earn engineering's trust and the security fluency to translate customer and market problems into sharp requirements from day one.

This is a product-thinking role first. You'll need enough technical depth to form independent opinions on architecture and tradeoffs and make calls grounded in customer and market context - not coordinate other people's decisions.

What you'll do

• Own product definition for a set of areas end to end: identify the problem worth solving, write the spec, and make the tradeoff calls on scope, sequencing, and technical approach in partnership with engineering.
• Bring real technical judgment to the table — evaluate build-vs-buy, architecture options, and technical debt tradeoffs alongside engineers, and hold your own in that conversation.
• Come in fluent in security concepts and terminology (identity, access, threat models, compliance drivers) so you can translate customer and market problems into requirements without a ramp-up period.
• Research competitors, market trends, and emerging technologies to inform where we invest next.
• Partner closely with design to shape the product experience for technical/security-heavy features.
• Own sales enablement — build and maintain the materials, demos, battlecards, and technical talk tracks the sales team needs to sell the product effectively.
• Talk to customers directly — run discovery, validate problems, and use that insight to shape what we prioritize, not just what we execute.
• Contribute product perspective to analyst conversations, sales/marketing messaging, and content, expanding the surface area the product voice covers.
• Define what success looks like for your areas and track whether we're actually moving the needle.

What you need to bring

• 3–6 years of product management experience, with meaningful time on technical/infrastructure or security products — you should be evaluating tradeoffs, not just gathering requirements.
• A security background you can hit the ground running. Hands‑on experience with concepts like identity, access management, cloud security, or compliance (SOC 2, etc.).
• The technical depth to engage engineers as a peer on design and architecture discussions.
• Strong product instincts — comfort defining problems from ambiguity, not just executing a pre‑defined plan.
• Experience operating with high autonomy, taking real ownership without needing heavy oversight.
• Bonus: prior startup experience, dev‑facing/API product experience, or experience supporting GTM/analyst‑facing work.