Principal Product Operations Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About The Role" (we can use About the role heading). Then responsibilities: "What You'll Do" sections. Requirements/Qualifications: "What You Bring". Skills: maybe part of that. Benefits: none mentioned except maybe compensation range? There's a Compensation Range: $215K - $260K. That's pay. So we can include Pay section with that. Benefits: none explicit. Schedule: none. So we include About the role, Responsibilities, Requirements (or Qualifications), Skills, Pay. Possibly combine Requirements and Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple if content exists. We have content for About the role (the "About The Role" paragraph). Responsibilities: "What You'll Do" bullet points. Requirements/Qualifications: "What You Bring" list. Skills: maybe we can extract skills from that list: hands-on experience with tools, comfort building dashboards, SQL plus, LLM use, experience designing processes, working knowledge of PDLC/SDLC, comfort facilitating conversations, strong analytical skills, generalist mindset, bias toward noticing inefficiency, excellent documentation/communication, ability to work autonomously. That's skills. We could put them under Skills. Pay: compensation range. Benefits: none. Schedule: none. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, Follow Us, etc. Also remove "Why Socure?" intro? That's not a section heading but it's content; we need to preserve ALL substantive information. The intro "Why Socure?" is substantive? It's about company mission. Should we include it? It's not under a heading; we could put it in a

before sections? The instruction: Output ONLY the HTML fragment. We can include a

for that intro before sections. It's not a heading. That's fine. We must not include duplicated lines. Ensure we preserve all substantive info from the posting: The "Why Socure?" paragraph, the "About The Role" paragraph, the "What You'll Do" bullet list, the "What You Bring" bullet list, the "Why This Role Matters" paragraph, the compensation range. Also maybe the "Product Operations exists to give product teams..." is part of About the role? Actually that is under About The Role heading. We'll include that as part of About the role section. We need to format lists with

• . For prose use

  . For headings use

  . We must not create sections with filler. So we will have:

  About the role

  ... (the About The Role paragraph plus maybe the "Product Operations exists..." paragraph). Actually the About The Role heading is followed by a paragraph describing the role. We'll combine. Then

  Responsibilities

  • ... each bullet from What You'll Do.
  Then

  Requirements

  maybe combine with Qualifications? Could do Requirements and Qualifications separate but content similar. Safer to have one Requirements section that includes the "What You Bring" bullet list. Or we could split: Requirements (years experience, familiarity with tools) and Qualifications (skills). But we have limited time. We'll put Requirements as the bullet list. Then

  Skills

  maybe we can list skills extracted. But that may duplicate content. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section, and not have separate Skills. But they asked to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It's not mandatory to use all; we can include only those with real content. So we could have About the role, Responsibilities, Requirements (which includes qualifications and skills), Pay. That's enough. But we need to preserve all substantive info; if we combine, we still preserve. So we can have Requirements section containing the bullet list from What You Bring. That includes experience, hands-on experience, comfort building dashboards, SQL plus, LLM use, experience designing processes, working knowledge of PDLC/SDLC, comfort facilitating conversations, strong analytical skills, generalist mindset, bias toward noticing inefficiency, excellent documentation/communication, ability to work autonomously. That covers skills. Thus we will have:

  About the role

  Why Socure? Socure is building the identity trust infrastructure for the digital economy — verifying 100% of good identities in real time and stopping fraud before it starts. The mission is big, the problems are complex, and the impact is felt by businesses, governments, and millions of people every day. We hire people who want that level of responsibility. People who move fast, think critically, act like owners, and care deeply about solving customer problems with precision. If you want predictability or narrow scope, this won’t be your place. If you want to help build the future of identity with a team that holds a high bar for itself — keep reading.

  Product Operations exists to give product teams the systems, data, and processes they need to plan, prioritize, and deliver well — the same way Sales Ops supports Sales or DevOps supports Engineering. This role sits at the center of that discipline, owning four things: the tools and systems product teams plan and work in, the reporting and analytics that give everyone visibility into what's happening, the process that makes planning and delivery repeatable instead of reinvented pod by pod, and the ongoing work of keeping strategy and execution connected as priorities shift. We run Product Operations as a hybrid centralized/embedded model: some Product Ops work sits centrally and serves every product team consistently, while other Product Ops work sits embedded inside individual product lines, close to their day-to-day priorities. This role sits in the centralized hub — you're the shared systems, process, and reporting engine that every embedded product manager and product ops partner relies on, rather than being dedicated to any single product line. We're a small team, so this role is intentionally broad. At larger companies, "owns the tools," "owns the reporting," and "owns the process" are sometimes split into two or three separate roles. Here, one person does all of it, with the flexibility to shift emphasis as priorities and team size change over time.

  Then Responsibilities:

  Responsibilities

  • Own the product systems & tools stack: Administer and configure the core product management / roadmapping platform (e.g., Aha!, Productboard, or equivalent) — workspaces, fields, workflows, scorecards, and permissions.
  • Own the connection between the product management platform and the engineering work-tracking system (e.g., Jira) — field mapping, status sync, and keeping data consistent between the two.
  • Manage the broader product tech stack: evaluate new tools, prevent tool sprawl, and maintain integrations across roadmap, delivery, feedback, and CRM systems.
  • Build and maintain the intake and prioritization workflows product teams use to submit, score, and rank requests.
  • Document system configuration and standard operating procedures so system knowledge isn't concentrated in one person (including yourself).
  • Support reporting & analytics for the Product Org: Build and maintain the dashboards and reports that give leadership and embedded product teams a reliable view of roadmap status, delivery progress, and portfolio health.
  • Define and track core product operations metrics (e.g., cycle time, roadmap adherence, planning hygiene, tool adoption).
  • Centralize and facilitate Product Performance metrics definition, telemetry builds, and availability to central data and BI teams, and coordinate dashboard and reporting builds with the central Business Intelligence team to enable deeper insights and faster decision making for the Product Team.
  • Partner with Finance, Sales/RevOps, and Engineering to bring commercial and delivery data (e.g., CRM/ARR data) into product prioritization and reporting.
  • Support recurring reporting cadences — business reviews, quarterly/annual planning, board updates — with clean, trusted data.
  • Monitor data quality and drive hygiene standards across the systems that feed reporting.
  • Drive process, efficiency & team enablement: Design and document repeatable processes for planning, prioritization, intake, and roadmap reviews — so teams have a consistent way of working instead of reinventing it pod by pod.
  • Identify friction points and manual, duplicative work in the product development lifecycle, and fix them — through better process, automation, or tooling.
  • Build templates, playbooks, and checklists (e.g., for feature intake, roadmap reviews, launch readiness) that save product managers time and reduce administrative burden.
  • Act as the go-to resource for product managers and embedded product ops partners on how to use shared tools and processes effectively — training, office hours, documentation.
  • Facilitate cross-functional handoffs between Product, Engineering, Design, and GTM so work moves smoothly instead of stalling on a handoff.
  • Continuously look for opportunities to standardize process across pods while leaving room for the flexibility each team actually needs.
  • Keep strategy and execution aligned: Partner with product leadership to translate high-level strategy and company priorities into a concrete, trackable roadmap and planning cadence.
  • Run the rhythm of planning — quarterly/annual planning cycles, roadmap reviews, and business reviews — that keeps execution connected to strategy as priorities shift.
  • Monitor progress against strategic priorities and flag early when day-to-day execution is drifting from what leadership actually intended.
  • Support trade-off and prioritization conversations when competing asks conflict with stated strategic priorities, so decisions get made deliberately rather than by default.
  • Make sure work happening inside individual pods visibly ladders up to company-level strategic themes, not just local priorities.
  • Close the loop after major planning moments — make sure decisions made in a review actually get reflected in the systems everyone works from day to day.
  Then Requirements:

  Requirements

  • 10+ years in Product Operations, Business/Sales Operations, or a Product Analyst/Management role, ideally supporting or working inside of a product or engineering organization.
  • Hands-on experience working in or familiarity with a product roadmapping/PPM tool (e.g., Aha!, Productboard, Jira Product Discovery) and a work-tracking tool (e.g., Jira, Linear, Azure DevOps).
  • Comfort building dashboards and reports (in the PPM tool itself, Tableau, Looker, or Google Sheets/Excel); SQL is a plus.
  • Use of LLM-based tools (e.g. Claude, ChatGPT, Perplexity, etc.) to augment and optimize job and role-related workflows, dashboards, research, etc.
  • Experience designing and documenting repeatable processes — intake, prioritization, planning cadences — rather than just running an existing one.
  • Working knowledge of PDLC and SDLC processes — roadmaps, backlogs, sprints, and prioritization frameworks (e.g., RICE, WSJF), different types of launch and product profiles (0-1 products, mature products, etc) and the PDLC process to support them.
  • Comfort facilitating conversations where strategic priorities and day-to-day execution are in tension, and helping stakeholders land on a decision.
  • Strong analytical skills — able to turn messy or scattered data into something people can act on.
  • A generalist mindset and genuine comfort moving between technical configuration, process design, and data/reporting work in the same week.
  • A bias toward noticing